Messages in this thread |  | | | Subject | Re: extremely odd FS decay in 2.0.32 | | From | Pierfrancesco Caci <> | | Date | 14 Apr 1998 19:03:01 +0200 |
| |
"Brian H. Trammell" <brian@altara.org> writes:
> > I'm seeing some very, very odd behavior in an e2fs under RedHat's 2.0.32 > kernel (stock 2.0.32 +teardrop +f00f, I believe). For a while, I've > watched inodes just disappear from underneath me, giving me errors such as > > EXT2-fs warning (device 03:02): ext2_free_inode: bit already cleared for > inode 41131 > > Listing the file (ls -li) gives the following: > > 41131 ?--------- 0 root root 0 Dec 31 1969 downtown-freedom-640.jpg > > The data in the file is, of course, gone. Attempts to edit with vi return > "downtown-freedom-640 is not a file". > > I have heard theories relating this to flaky hardware (the same sort of > memory insanity that makes the happy sig11 possible), and am running > kernel compiles nonstop to see if I can get a sig11 to show up (nothing > after three compiles, will keep trying.) >
this is the same thing that happens to me (version as in the signature) the file(s) involved are always the same: /usr/sbin/pppd (which is a soft link to /usr/sbin/pppd-2.3.3), /usr/sbin/statnet, named-xfer, chat
I've learned to keep a copy in another directory, so far...
Pf
--
------------------------------------------------------------------------------- Pierfrancesco Caci | Internet: mailto:ik5pvx@infogroup.it ik5pvx | http://www.geocities.com/SoHo/Lofts/8999 Firenze - Italia | Office for the Complication of Otherwise Simple Affairs Linux penny 2.1.95 #8 Fri Apr 10 22:01:11 CEST 1998 i586 unknown - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.rutgers.edu
|  |