https://jira.whamcloud.com This file is an XML representation of an issue en-us 9.4.14 940014 05-12-2023 https://jira.whamcloud.com/browse/LU-12078 Lustre <p>I've added test commit top of 2.10.7_rc1 tag for test. at the end, tar filename is a bit longer. (lustre-2.10.7_RC1.tar.gz vs lustre-2.10.7_RC1_1_g8c8ff5f.tar.gz) and there are some file path are longer than limitation below.</p> <div class="preformatted panel" style="border-width: 1px;"><div class="preformattedContent panelContent"> <pre># sh ./autogen.sh; ./configure --enable-dist; make dist - snip - test -n "" \ || find "lustre-2.10.7_RC1_1_g8c8ff5f" -type d ! -perm -755 \ -exec chmod u+rwx,go+rx {} \; -o \ ! -type d ! -perm -444 -links 1 -exec chmod a+r {} \; -o \ ! -type d ! -perm -400 -exec chmod a+r {} \; -o \ ! -type d ! -perm -444 -exec /bin/sh /scratch/lustre-release/config/install-sh -c -m a+r {} {} \; \ || chmod -R a+r "lustre-2.10.7_RC1_1_g8c8ff5f" tardir=lustre-2.10.7_RC1_1_g8c8ff5f &amp;&amp; tar --format=ustar -chf - "$tardir" | GZIP=--best gzip -c &gt;lustre-2.10.7_RC1_1_g8c8ff5f.tar.gz tar: lustre-2.10.7_RC1_1_g8c8ff5f/contrib/lbuild/lustre-2.10.7_RC1/zfs/scripts/zpios-test/4th-1024rc-4rs-1cs-4off.sh: link name is too long; not dumped tar: lustre-2.10.7_RC1_1_g8c8ff5f/contrib/lbuild/lustre-2.10.7_RC1/zfs/scripts/zpios-test/1x256th-65536rc-4rs-1cs-4off.sh: link name is too long; not dumped tar: lustre-2.10.7_RC1_1_g8c8ff5f/contrib/lbuild/lustre-2.10.7_RC1/zfs/scripts/zpios-test/16th-8192rc-4rs-1cs-4off.sh: link name is too long; not dumped tar: lustre-2.10.7_RC1_1_g8c8ff5f/contrib/lbuild/lustre-2.10.7_RC1/zfs/scripts/zpios-test/1th-16rc-4rs-1cs-4off.sh: link name is too long; not dumped tar: lustre-2.10.7_RC1_1_g8c8ff5f/contrib/lbuild/lustre-2.10.7_RC1/zfs/cmd/zed/zed.d/resilver_finish-notify.sh: link name is too long; not dumped tar: Exiting with failure status due to previous errors make[1]: Leaving directory `/scratch/lustre-release' if test -d "lustre-2.10.7_RC1_1_g8c8ff5f"; then find "lustre-2.10.7_RC1_1_g8c8ff5f" -type d ! -perm -200 -exec chmod u+w {} ';' &amp;&amp; rm -rf "lustre-2.10.7_RC1_1_g8c8ff5f" || { sleep 5 &amp;&amp; rm -rf "lustre-2.10.7_RC1_1_g8c8ff5f"; }; else :; fi </pre> </div></div> <p>this tarball gets broken whtn it extracts.</p> LU-12078

File path for zfs scripts are too long

Bug Minor Open Unresolved WC Triage Shuichi Ihara Fri, 15 Mar 2019 20:30:55 +0000 Tue, 8 Dec 2020 16:41:16 +0000 Lustre 2.10.6 0 3 <p>One thing that stands out is using "--format=ustar". I suspect this is causing ancient filename length limits to be used...</p> <p>I see an old commit that is supposed to fix this:</p> <div class="preformatted panel" style="border-width: 1px;"><div class="preformattedContent panelContent"> <pre>commit 7ef98b9c2549185b1ee2e758eb2cf0da261d75b5 Author: Brian J. Murrell &lt;brian@whamcloud.com&gt; AuthorDate: Mon Jan 24 15:53:53 2011 -0500 Commit: Brian J. Murrell &lt;brian@whamcloud.com&gt; CommitDate: Mon Feb 28 12:51:27 2011 -0500 b=21581 too long file / path names for old tar Instruct automake to use tar's ustar format to prevent errors when pathnames are longer than 99 chars. </pre> </div></div> <p>but it may not be enough. Could you try replacing "<tt>tar-ustar</tt>" in <tt>configure.ac</tt> with "<tt>tar-pax</tt>" to see if this fixes your problem? This is not being hit in anyone else's build environment, so you will need to verify this fixes the problem on your system. The "<tt>--format=pax</tt>" support has been available in GNU tar since version 1.14, which is really old already (I think we were patching tar 1.22 for Lustre many years ago), and is not a portability concern since Lustre will only run on Linux and use GNU tar.</p> <p>Also note that there <em>probably</em> shouldn't be a whole ZFS tree under <tt>lbuild/lustre-2.10.7_RC1</tt> in the build directory, but I don't use lbuild very much and can't comment authoritatively.</p> Related LU-14198 Development Rank 1|i00dfr: Rank (Obsolete) 9223372036854775807 Severity