Date: Wed, 2 Jun 2010 17:55:08 +0200 From: Leon =?iso-8859-15?Q?Me=DFner?= <l.messner@physik.tu-berlin.de> To: freebsd-questions@freebsd.org Subject: Re: freeBSD nullfs together nfs and "silly rename" Message-ID: <20100602155507.GR1023@emmi.physik-pool.tu-berlin.de> In-Reply-To: <20100602115033.GQ1023@emmi.physik-pool.tu-berlin.de> References: <20100602115033.GQ1023@emmi.physik-pool.tu-berlin.de>
next in thread | previous in thread | raw e-mail | index | archive | help
--DzFMwNuU1QL7hgxO Content-Type: text/plain; charset=iso-8859-15 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable nevermind.. resend and forgot to change the addressee. If anyone has an idea i would of course still be grateful. Regards, leon On Wed, Jun 02, 2010 at 01:50:33PM +0200, Leon Me=DFner wrote: > Hi, > I hope this is not the wrong list to ask. Didn't get any answers on > -questions. >=20 > When you try to do the following inside a nullfs mounted directory, > where the nullfs origin is itself mounted via nfs you get an error: >=20 > # foo=20 > # tail -f foo&=20 > # rm -f foo=20 > tail: foo: Stale NFS file handle > # fg >=20 > This is really a problem when running services inside jails and using > NFS as storage. As of [2] it looks like this problem is known for a > while. On a normal NFS mount this does not happen as "silly renaming" > [1] works there (producing nasty little .nfsXXXX files). >=20 > TIA, > Leon >=20 > [1] http://nfs.sourceforge.net/#faq_d2 > [2] http://ftp.freebsd.org/pub/FreeBSD/development/FreeBSD-CVS/src/sys/nf= sclient/nfsnode.h,v rev:1.32.2.1 --DzFMwNuU1QL7hgxO Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (FreeBSD) iEYEARECAAYFAkwGftsACgkQJCh4HSRvNnwxRgCfQeFcERdOzqWIYvSsDEfhYVXy OksAn2Vu2Ss31qtnovwVyNMABPgbHTJs =UIfR -----END PGP SIGNATURE----- --DzFMwNuU1QL7hgxO--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20100602155507.GR1023>