Re: ext2_free_inode errors (with 2.0.32)

Paul Wouters (paul@xtdnet.nl)
Sat, 17 Jan 1998 11:27:40 +0100 (MET)


On Fri, 16 Jan 1998, James Mastros wrote:

> > b--Sr-xrw- 1 28020 13881 80, 77 Jan 13 1970 5-2.gif
>
> "man chattr"... "chattr -i 5-2.gif"... If the inode got scribbled over, then

# chattr -i 5-2.gif
chattr 0.5b, 14-Feb-95 for EXT2 FS 0.5a, 95/03/19
chattr: No such device while reading flags on 5-2.gif

> > > Any useful suggestions to avoid such problems in the future?
> > No clue. Keep recent backups :)
> And run badblocks, if you havn't already. (Or e2fsck -cv)

I won't do that from home though :)

For what it's worth, my machine was :
e2fsck 1.07, 14-Mar-97 for EXT2 FS 0.5b, 95/08/09
Using EXT2FS Library version 1.07

The machine i had to go to last night (after this thread started) had
the same problem. Going to single user and e2fsck'ing didn't give
any weird files that I've found so far. That machine apparently got
into problems roughly at the time it was receiving a 16+ MB mailfile
It was:
e2fsck 1.06, 7-Oct-96 for EXT2 FS 0.5b, 95/08/09
Using EXT2FS Library version 1.06

Ah well, no real harm has been done :)

Paul