Date: Fri, 24 Mar 2006 12:10:30 -0500 From: Kris Kennaway <kris@obsecurity.org> To: Viren Patel <virenp@mail.utexas.edu> Cc: questions@freebsd.org, Kris Kennaway <kris@obsecurity.org> Subject: Re: FreeBSD 6.1 - mount_nullfs broken? Message-ID: <20060324171030.GB24853@xor.obsecurity.org> In-Reply-To: <1052.66.25.138.31.1143209131.squirrel@mail.cm.utexas.edu> 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>
next in thread | previous in thread | raw e-mail | index | archive | help
--R3G7APHDIzY6R/pk Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable 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 >=20 > After looking at the dmesg output more closely one > discrepancy I found was the second last line: >=20 > ad6: 238475MB <WDC WD2500JS-55MHB0 02.01C03> at > ata3-master SATA300 >=20 > 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 --R3G7APHDIzY6R/pk Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2.2 (FreeBSD) iD8DBQFEJCgGWry0BWjoQKURArPXAJ98wM90FNAgU/4umGl+YxuyILPsSQCgyJoO 7Kyn07bHFc3iRUP/4eio7wQ= =ey5R -----END PGP SIGNATURE----- --R3G7APHDIzY6R/pk--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20060324171030.GB24853>