Date: Tue, 05 Aug 1997 08:07:26 +1000 From: David Nugent <davidn@labs.usn.blaze.net.au> To: Terry Lambert <terry@lambert.org> Cc: current@freebsd.org Subject: Re: Some thoughts and ideas, and quirks Message-ID: <E0wvVHi-0007a1-00@labs.usn.blaze.net.au> In-Reply-To: Your message of "Mon, 04 Aug 1997 13:19:03 MST." <199708042019.NAA04714@phaeton.artisoft.com>
next in thread | previous in thread | raw e-mail | index | archive | help
> > Well bugs, typos or whatever, they still prevent them from being made into > > lkms. However I still don't see an ext2fs lkm or mount_ext2fs program > > (unless it's hiding from me), and mount -t ext2fs did need the kernel > > directive so afaic that's not really a typo. > > The list is there whether the FS is compiled in or not (see mount.h), > so having the enumerated value on the other side of the mount call > isn't really an issue; there's a number of other places where it's > screwed up, though. > > There's also a mount_ext2fs in /usr/src/sbin/mount_ext2fs. 8-). Just incidently, it seems that support for ext2fs in -current is broken right now, having had occasion to use it over the last few days. I haven't had time yet to diagnose it in detail, but mention it now in case someone has some ideas already and save some time. (Bruce? Are you listening?) Sympoms are "block already freed" errors when writing to the ext2fs filesystem, and eventually (sometimes very quickly) a complete system freeze - no panic messages at all, no ddb in spite of it being in the running kernel. Mounting it read-only seems safe and stable enough, so I'm doing that for now. FS code, particularly on -current, is way out of my league. :-) Regards, David
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?E0wvVHi-0007a1-00>