Date: Mon, 4 Aug 1997 15:12:08 -0700 (MST) From: Terry Lambert <terry@lambert.org> To: davidn@labs.usn.blaze.net.au (David Nugent) Cc: terry@lambert.org, current@FreeBSD.ORG Subject: Re: Some thoughts and ideas, and quirks Message-ID: <199708042212.PAA05027@phaeton.artisoft.com> In-Reply-To: <E0wvVHi-0007a1-00@labs.usn.blaze.net.au> from "David Nugent" at Aug 5, 97 08:07:26 am
next in thread | previous in thread | raw e-mail | index | archive | help
> 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. I think this has more to do with VM optimizations in the recent past, where the processing order dependencies haven't been propagated. Look at the last change date in ext2fs (one that isn't an attempt at a fix, and then look at the deltas to the UFS/FFS code from that date to present. This should tell you roughly the neighborhood, if in fact it's a VM related problem. There are really no other common subsystem dependencies that could have not been updated at the same time, I believe. You may want to look over the -current list archives; in particular, I believe John Dyson was doing-something/going-to-be-doing-something in this are as well (my memory may not be correct on this point, however). Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199708042212.PAA05027>