Date: Fri, 25 Jun 1999 11:46:08 +0200 From: Ladavac Marino <mladavac@metropolitan.at> To: "'Kevin Quinlan (UK)'" <KevinQ@ctxuk.citrix.com>, freebsd-questions@freebsd.org Subject: RE: Kernel crashes using FreeBSD 3.1 (and 3.2) Message-ID: <55586E7391ACD211B9730000C11002761796A1@r-lmh-wi-100.corpnet.at>
next in thread | raw e-mail | index | archive | help
> -----Original Message----- > From: Kevin Quinlan (UK) [SMTP:KevinQ@ctxuk.citrix.com] > Sent: Thursday, June 24, 1999 6:37 PM > To: freebsd-questions@freebsd.org > Subject: RE: Kernel crashes using FreeBSD 3.1 (and 3.2) > > /home -> /targetdisk/home (null) > > When I changed this to a Union mount, the system (only tested on 3.2) > no > longer crashes, > but now I get hundreds of: > > vnode_pager: *** WARNING *** stale FS getpages > > messages. > > I would like to mount this disk on /home rather than using a symlink, > are > there any workarounds for this? Is it a known problem? > [ML] There seem to be some problems with null and union mounts. Symlink is probably the best way, but NFS loopback mount did work for me, even though it was slowish and was causing unneccessary load. I've been using symlinks ever since, except that some dumb 3rd party install programs check whether /foo/bar is a directory and fail if it is a symlink to /blah; in such cases I use NFS loopback, and replace it with symlink afterwards (installation speed is hardly critical :) /Marino To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?55586E7391ACD211B9730000C11002761796A1>