Re: [Bug-tar] Possible bug in 1.26 version ?

[shift]

Ok, I've remade test and can post information. Newly generated tar and strace files resides at the same ftp account. Problem was reproduced. See here:

address@hidden:~/build/openwrt/trunk/build_dir/target-mips_r2_uClibc-0.9.33.2/OpenWrt-SDK-ar71xx-for-Linux-x86_64-gcc-4.6-linaro_uClibc-0.9.33.2/staging_dir/target-mips_r2_uClibc-0.9.33.2/root-ar71xx/sbin$ ls -alh
ls: klogd: No such file or directory
ls: sysctl: No such file or directory
ls: lsmod: No such file or directory
ls: udhcpc: No such file or directory
ls: watchdog: No such file or directory
ls: ifconfig: No such file or directory
ls: poweroff: No such file or directory
ls: pivot_root: No such file or directory
ls: start-stop-daemon: No such file or directory
ls: logread: No such file or directory
ls: reboot: No such file or directory
ls: insmod: No such file or directory
ls: ifdown: No such file or directory
ls: init: No such file or directory
ls: hwclock: No such file or directory
ls: rmmod: No such file or directory
ls: syslogd: No such file or directory
ls: halt: No such file or directory
total 2.5M
drwxr-xr-x  3 darius darius 4.0K Aug 18 21:38 .
drwxr-xr-x 17 darius darius 4.0K Aug 18 21:38 ..
-rwxr-xr-x  1 darius darius  200 Aug 11 16:29 devstatus
-rwxr-xr-x  1 darius darius  629 Aug 11 16:30 firstboot
lrwxrwxrwx  1 darius darius   14 Aug 18 17:28 halt -> ../bin/busybox
-rwxr-xr-x  1 darius darius  37K Aug 18 21:37 hotplug2
-rwxr-xr-x  1 darius darius  317 Aug 11 16:30 hotplug-call
lrwxrwxrwx  1 darius darius   14 Aug 18 17:28 hwclock -> ../bin/busybox
lrwxrwxrwx  1 darius darius   14 Aug 18 17:28 ifconfig -> ../bin/busybox
lrwxrwxrwx  1 darius darius    4 Aug 11 16:29 ifdown -> ifup
-rwxr-xr-x  1 darius darius  249 Aug 11 16:29 ifstatus
-rwxr-xr-x  1 darius darius 1.2K Aug 11 16:29 ifup
lrwxrwxrwx  1 darius darius   14 Aug 18 17:28 init -> ../bin/busybox
lrwxrwxrwx  1 darius darius   14 Aug 18 17:28 insmod -> ../bin/busybox
lrwxrwxrwx  1 darius darius   14 Aug 18 17:28 klogd -> ../bin/busybox
-rwxr-xr-x  1 darius darius  500 Aug 11 16:30 led.sh
lrwxrwxrwx  1 darius darius   14 Aug 18 17:28 logread -> ../bin/busybox
lrwxrwxrwx  1 darius darius   14 Aug 18 17:28 lsmod -> ../bin/busybox
-rwxr-xr-x  1 darius darius  517 Aug 11 16:30 mount_root
-rwxr-xr-x  1 darius darius  26K Aug 18 21:38 mtd
-rwxr-xr-x  1 darius darius 1.8M Aug 18 21:35 netifd
lrwxrwxrwx  1 darius darius   14 Aug 18 17:28 pivot_root -> ../bin/busybox
lrwxrwxrwx  1 darius darius   14 Aug 18 17:28 poweroff -> ../bin/busybox
lrwxrwxrwx  1 darius darius   14 Aug 18 17:28 reboot -> ../bin/busybox
lrwxrwxrwx  1 darius darius   14 Aug 18 17:28 rmmod -> ../bin/busybox
----------  1 darius darius    0 Aug 19 10:59 route
lrwxrwxrwx  1 darius darius   14 Aug 18 17:28 start-stop-daemon -> ../bin/busybox
drwxr-xr-x  6 darius darius 4.0K Aug 18 10:50 .svn
-rwxr-xr-x  1 darius darius  20K Aug 18 21:38 swconfig
----------  1 darius darius    0 Aug 19 10:59 switch_root
lrwxrwxrwx  1 darius darius   14 Aug 18 17:28 sysctl -> ../bin/busybox
lrwxrwxrwx  1 darius darius   14 Aug 18 17:28 syslogd -> ../bin/busybox
-rwxr-xr-x  1 darius darius 4.6K Aug 12 23:29 sysupgrade
-rwxr-xr-x  1 darius darius 423K Aug 18 17:19 ubusd
-rwxr-xr-x  1 darius darius  87K Aug 18 21:35 uci
-rwxr-xr-x  1 darius darius 8.9K Aug 18 21:37 udevtrigger
lrwxrwxrwx  1 darius darius   14 Aug 18 17:28 udhcpc -> ../bin/busybox
----------  1 darius darius    0 Aug 19 10:59 vconfig
lrwxrwxrwx  1 darius darius   14 Aug 18 17:28 watchdog -> ../bin/busybox
-rwxr-xr-x  1 darius darius 2.3K Aug 11 16:28 wget2nand
-rwxr-xr-x  1 darius darius 3.9K Aug 11 16:30 wifi

Honestly I don't know what errors 'No such file or directory' means, but real problem is with files 'route', 'switch_root' and 'vconfig'. As you can see they are 0 sizes and with no permissions. Files in FTP now are exactly the same which generated an output as you can see above.


On 08/18/2012 11:36 PM, Paul Eggert wrote:

I've looked at the strace output and it looks fine.
The 'tar' in question had no apparent problems
in creating the destination.  And I had no problems
extracting from the tarball you sent me, using tar 1.26
on Fedora 15.

What are the exact failure symptoms that you are observing?