Date: Mon, 10 Apr 2000 19:06:57 +0800 From: Adrian Chadd <adrian@freebsd.org> To: John Estess <jestess@wcnet.net> Cc: freebsd-fs@freebsd.org Subject: Re: UNIONFS Message-ID: <20000410190656.B18146@ewok.creative.net.au> In-Reply-To: <38EF6FAD.44DF0965@wcnet.net>; from John Estess on Sat, Apr 08, 2000 at 12:43:09PM -0500 References: <38EF5E0D.1B06FDD5@wcnet.net> <38EF6FAD.44DF0965@wcnet.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sat, Apr 08, 2000, John Estess wrote: > hate to answer my own post, but... > > > like the inability to umount(no kidding - am I > > doing something wrong?). Also, a whiteout file was affected. Yes, I'll > > recheck that - that didn't make sense. > > Works correctly on both counts. (double) Whoops. Heh. I've been looking at this bug, and I'm not impressed. It looks like a VM/unionfs problem, however there are plenty of other unionfs weirdnesses (including one where if you pwd while running a script which happens to exist in the upper directory and not the lower one, it returns the upper dir pathname, breaking lots of configure type stuff. I don't know whether this is a bad thing or not, to be honest :-) which I'm going to be looking at over the next few weeks and submit some patches. Adrian To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-fs" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20000410190656.B18146>