| To: | linux-xfs@xxxxxxxxxxx |
|---|---|
| Subject: | Re: null character filesystem corruption with 2.4.6 |
| From: | Colin Walters <walters@xxxxxxxxxxxxxxxxxx> |
| Date: | Sat, 14 Jul 2001 16:05:46 -0400 |
| In-reply-to: | <3B50834F.3DA6115D@xxxxxxx> (Eric Sandeen's message of "Sat, 14 Jul 2001 12:37:19 -0500") |
| Mail-followup-to: | linux-xfs@xxxxxxxxxxx |
| Organization: | The Ohio State University Dept. of Computer and Info. Science |
| References: | <87y9psdpcc.church.of.emacs@xxxxxxxxxxxxxxxxxx> <3B50834F.3DA6115D@xxxxxxx> |
| Sender: | owner-linux-xfs@xxxxxxxxxxx |
| User-agent: | Gnus/5.090004 (Oort Gnus v0.04) Emacs/21.0.103 (powerpc-debian-linux-gnu) |
Eric Sandeen <sandeen@xxxxxxx> writes: > How many times has this system crashed? The only time I have seen > null characters is when I had a system crash, and some files which > were being actively written to came up with nulls after recovery. > This is because the metadata (size) had been written out to disk, > but the data itself had not. I see. It's only crashed once. It is probably (actually, certainly) my fault that the corruption was so severe; I just exited from the kernel debugger and continued reading my email, which was about the dumbest thing I could do. Oh, well. I've learned my lesson :) So far findnull hasn't found any new nulled files, so I think I'll continue using XFS. I will let you know if it does find new ones, though. Thanks! |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: null character filesystem corruption with 2.4.6, Seth Mos |
|---|---|
| Next by Date: | Re: null character filesystem corruption with 2.4.6, Juha Saarinen |
| Previous by Thread: | Re: null character filesystem corruption with 2.4.6, Eric Sandeen |
| Next by Thread: | Web Page Banner, David Lloyd |
| Indexes: | [Date] [Thread] [Top] [All Lists] |