Date: 24 Mar 2006 13:47:33 -0500 From: Lowell Gilbert <freebsd-questions-local@be-well.ilk.org> To: Viren Patel <virenp@mail.utexas.edu>, questions@freebsd.org Subject: Re: FreeBSD 6.1 - mount_nullfs broken? Message-ID: <44lkuzel2y.fsf@be-well.ilk.org> In-Reply-To: <20060324184044.GA26325@xor.obsecurity.org> References: <58674.146.6.135.6.1143153068.squirrel@mail.cm.utexas.edu> <20060323230935.GA90169@xor.obsecurity.org> <1052.66.25.138.31.1143209131.squirrel@mail.cm.utexas.edu> <20060324171030.GB24853@xor.obsecurity.org> <60973.146.6.135.6.1143225570.squirrel@mail.cm.utexas.edu> <20060324184044.GA26325@xor.obsecurity.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Kris Kennaway <kris@obsecurity.org> writes: > On Fri, Mar 24, 2006 at 12:39:30PM -0600, Viren Patel wrote: > > > On Fri, Mar 24, 2006 at 08:05:31AM -0600, Viren Patel > > > wrote: > > > > > >> # umount /export/jails/testjail/dev > > >> # mount_nullfs -o ro /export/jails/basejail > > >> /export/jails/testjail/basejail > > >> mount_nullfs: Operation not supported by device > > >> > > >> After looking at the dmesg output more closely one > > >> discrepancy I found was the second last line: > > >> > > >> ad6: 238475MB <WDC WD2500JS-55MHB0 02.01C03> at > > >> ata3-master SATA300 > > >> > > >> It was definitely SATA150 under FreeBSD 6.0, even after > > >> updates. So maybe a problem in the SATA300 driver? > > > > > > Unlikely. It looks like you don't have kernel nullfs > > > support enabled. > > > > > > Kris > > > > > > > I am using the generic kernel. Looking through /etc there > > is nothing regarding enabling nullfs. I also looked at > > GENERIC kernel conf file without luck. How do I enable > > nullfs? > > Compile it into your kernel or load the module. Read the handbook for > more help. Or you could come at it the other way; figure out how you did it when you were running 6.0. The procedure has not changed.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?44lkuzel2y.fsf>