Date: Sat, 27 Feb 1999 13:05:26 +0100 From: Eivind Eklund <eivind@FreeBSD.ORG> To: Luigi Rizzo <luigi@labinfo.iet.unipi.it> Cc: Tony Finch <dot@dotat.at>, current@FreeBSD.ORG Subject: Re: mount -o union broken recently? Message-ID: <19990227130525.L19632@bitbox.follo.net> In-Reply-To: <199902262016.VAA26475@labinfo.iet.unipi.it>; from Luigi Rizzo on Fri, Feb 26, 1999 at 09:16:44PM %2B0100 References: <E10GNQx-0002lU-00@fanf.noc.demon.net> <199902262016.VAA26475@labinfo.iet.unipi.it>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, Feb 26, 1999 at 09:16:44PM +0100, Luigi Rizzo wrote: > (about union mounts on 3.1 not returning all files with an 'ls' in 3.1 > while it did in 3.0) > > > Is it sorrect that this magic is implemented in sys/kern/vfs_lookup.c? > > The odd thing is that AFAICS no-one has made significant changes to > > this code. > > i just experienced the above today while trying diskless, and while ls > only seems to return the entries for the topmost directory, files are > accessible if you know the name. no idea if this is of any help. > > on a related subject; i noticed that using mount_null on a directory > with device entries (e.g. still in the diskless case, say /foo/dev is > an mfs partition with device entries, and i do a mount_null /foo/dev > /dev ) causes very bad effects such as crashing the system when i > start X. ideas about this as well ? Yes. NULLFS mounts do not work, due to a combination of aliasing problems and locking problems. There is a preliminary patch at http://www.freebsd.org/~eivind/FixNULL.patch that I believe fix the aliasing problems, and some of the locking problems, but not all. Using nullfs with this works somewhat, but sometimes get locks screwed up (which result in access to one file just hanging). Eivind. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?19990227130525.L19632>