Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 20 Jan 2009 14:29:04 -0600
From:      Chris Ruiz <chris@young-alumni.com>
To:        freebsd-hackers@freebsd.org
Subject:   Re: tar fails on FreeBSD 7 and passes on FreeBSD 6 for the same input
Message-ID:  <EFF21B1D-21DB-4D5D-9A28-F948DD2B0346@young-alumni.com>
In-Reply-To: <3f95d3db0901192354s502644cdh3ecf44a4ecf3fe6f@mail.gmail.com>
References:  <3f95d3db0901192354s502644cdh3ecf44a4ecf3fe6f@mail.gmail.com>

next in thread | previous in thread | raw e-mail | index | archive | help

On Jan 20, 2009, at 1:54 AM, chandra reddy wrote:

> Hi,
>
> I am getting the following error when i run tar on a directory.
>
> [chandra@home]$ tar  zcf config-xsl.tar  config-xsl/9.6
>
> tar: Cannot open directory
> config-xsl/9.6/configuration/protocols/mpls/label-switched-path/oam/ 
> bfd-liveness-detection/detection-time:
> No such file or directory
> tar: Cannot open directory
> config-xsl/9.6/configuration/protocols/mpls/label-switched-path/oam/ 
> bfd-liveness-detection/failure-action:
> No such file or directory
> [chandra@home]$ ldd  tar
> tar:
>        libc.so.6 => /usr/local/lib/compat/libc.so.6 (0x28097000)

I am a little confused by the above.  It shows your tar binary being  
linked to a library from freebsd 6 NOT 7.  Did you update your "world"  
when  you updated your kernel to 7?

This is the appropriate output on a recent CURRENT:
# ldd /usr/bin/tar
/usr/bin/tar:
         libarchive.so.4 => /usr/lib/libarchive.so.4 (0x800649000)
         libbz2.so.3 => /usr/lib/libbz2.so.3 (0x800774000)
         libz.so.4 => /lib/libz.so.4 (0x800884000)
         libc.so.7 => /lib/libc.so.7 (0x800998000)

IIRC, 7 should have very similar output and should be linked to  
libc.so.7.

> chandra@home]$ uname -a
> FreeBSD chandra 7.1-RC1 FreeBSD 7.1-RC1 #0: Sun Dec  7 05:57:33 UTC  
> 2008
> root@logan.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC  i386
> I have debugged libc and found that  system call "fstafs" is failing  
> and
> returning -1.
>
> Can any one help me what is the real problem here and how to fix it?
>
>
>
> Thanks
> Chandra_

My best guess is that you have an incompletely upgraded system.

Chris Ruiz




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?EFF21B1D-21DB-4D5D-9A28-F948DD2B0346>