Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 20 Jan 2009 04:49:03 -0800
From:      David Wolfskill <david@catwhisker.org>
To:        chandra reddy <creddym@gmail.com>
Cc:        freebsd-hackers@freebsd.org, freebsd-questions@freebsd.org
Subject:   Re: tar fails on FreeBSD 7 and passes on FreeBSD 6 for the same input
Message-ID:  <20090120124903.GH17567@albert.catwhisker.org>
In-Reply-To: <3f95d3db0901192354s502644cdh3ecf44a4ecf3fe6f@mail.gmail.com>
References:  <3f95d3db0901192354s502644cdh3ecf44a4ecf3fe6f@mail.gmail.com>

Next in thread | Previous in thread | Raw E-Mail | Index | Archive | Help

--dQAkT9kf8uI42z2+
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Tue, Jan 20, 2009 at 01:24:41PM +0530, chandra reddy wrote:
> Hi,
>=20
> I am getting the following error when i run tar on a directory.
>=20
> [chandra@home]$ tar  zcf config-xsl.tar  config-xsl/9.6
>=20
> tar: Cannot open directory
> config-xsl/9.6/configuration/protocols/mpls/label-switched-path/oam/bfd-l=
iveness-detection/detection-time:
> No such file or directory
> tar: Cannot open directory
> ...
> 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.

I believe you will find that the system call is "fstatfs".
=20
> Can any one help me what is the real problem here and how to fix it?

A subsequent message of your verified that the hierarchy being read was
on an NFS-mounted file system.  Perchance, was that NFS mount managwed
by amd(8)?

If so, while I do not have a "fix" for you, I am relieved to see someone
else finally report these symptoms.  Please see
<http://docs.FreeBSD.org/cgi/mid.cgi?20081203001538.GC96383>; for an
archived copy of my initial message in a thread reporting this.

There is additional detail (including kernel trace information &
how-to-repeat instructions) in subsequent messages in the thread.  Also
mentioned is a circumvention -- basically, crippling amd(8) so it no
longer attempts to unmount() a file system.

However, I was unable to re-create the symptoms at home -- only at work.
A colleague at work was able to re-create the symptoms, and was
intending to experiment a bit more, but he's been busy with other things
recently.

Please contact me (off-list, if you prefer), and we can discuss
additional details.

Peace,
david
--=20
David H. Wolfskill				david@catwhisker.org
Depriving a girl or boy of an opportunity for education is evil.

See http://www.catwhisker.org/~david/publickey.gpg for my public key.

--dQAkT9kf8uI42z2+
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.9 (FreeBSD)

iEYEARECAAYFAkl1yD4ACgkQmprOCmdXAD1UxgCghs3BhjNOLyskf9J9ZB75CZ8+
AAIAnjq/eBOITNAvB0X6e39ks7HWLTFz
=JX2n
-----END PGP SIGNATURE-----

--dQAkT9kf8uI42z2+--



Want to link to this message? Use this URL: <http://docs.FreeBSD.org/cgi/mid.cgi?20090120124903.GH17567>