From: rohrer@fncrd6.fnal.gov (Keith Rohrer) Subject: Re: ext2fs CRASH help! Date: 28 May 1993 14:31:48 GMT
In article <C7pE83.GMA@eis.calstate.edu>, cwilder@eis.calstate.edu (Charlotte Wilder) writes:
|> Guess what... ext2fs v0.3 just bombed on me... What caused it was a system
[deleted...]
|> ... Also another thing I noticed about e2fsck is that sometimes an error
|> will exist in a file and e2fsck won't catch it until I delete the file, then
|> running e2fsck will discover filesystem errors that were associated with
|> the file.... arrghhh...
Last week, I had the problem that when I filled my /usr partition (ext2) with
anything (after awhile I was just catting /dev/zero > test.blob) I got out-
of-space errors with 2700 or so blocks, and scads of inodes, still free.
I ended up re-mke2fs'ing the partition to fix it. e2fsck showed no problems
whatsoever. Anyone else had this sort of bomb? (the partition may have been
made with 0.2 mke2fs, but I was using the 0.3 e2fs patches and programs;
kernel is 0.99.9)
TIA for any help,
Keith
-- Disclaimer: None of Grinnell College, URA, Fermilab, and any other affiliated persons or orginizations have licensed my ideas or opinions, and thus are not entitled to any which may appear above.