Date: Tue, 27 Apr 2004 04:43:34 -0700 From: Kris Kennaway <kris@obsecurity.org> To: andy_park@nospammail.net Cc: kris@obsecurity.org Subject: Re: Auto-mounting ext2 slices Message-ID: <20040427114333.GA36953@xor.obsecurity.org> In-Reply-To: <1083064442.29080.185185414@webmail.messagingengine.com> References: <1083064442.29080.185185414@webmail.messagingengine.com>
next in thread | previous in thread | raw e-mail | index | archive | help
--WIyZ46R2i8wDzkSu Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Tue, Apr 27, 2004 at 04:14:02AM -0700, andy_park@nospammail.net wrote: > -- Original message -- > No, there's also a fsck_ext2fs. This is necessary for fsck to have > any hope of being able to clean the filesystem automatically (it > doesn't know about weirdly named binaries like e2fsck :-), although > you may need to copy it into /sbin since /usr isn't mounted by the > time fsck runs. >=20 > Kris > -- End of original message -- >=20 > Right, so I copied fsck_ext2fs (which I had already, in /usr/local/sbin) > to /sbin, and hard-reset the system, but the boot still halts at the > point it tries to mount the ext2 slice. I get a warning that says the > slice is not clean, followed by a 'no permissions' error. The other > oddity is that simply trying 'fsck /dev/ad1s5' doesn't work (it complains > about the magic number being incorrect), although the man page for > fsck_ext2fs suggests that fsck should be able to invoke fsck_ext2fs. Does > this mean the slice has a corrupt superblock? > > I also have a follow-up question. Is there a way to mark a slice 'dirty' > without crashing or hard-resetting the OS? It would considerably ease my > testing. You can just use fsck -f. Kris --WIyZ46R2i8wDzkSu Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (FreeBSD) iD8DBQFAjkdlWry0BWjoQKURAonMAJ4963BaAy96jnzPEvxH24b16YkMOgCg49jM 8QzIgz4U56Kd5+LF2FafqgY= =TOTk -----END PGP SIGNATURE----- --WIyZ46R2i8wDzkSu--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20040427114333.GA36953>