Messages in this thread |  | | From | Andreas Dilger <> | Subject | Re: ext2 filesystem corruptions back from dead? 2.4.0-test11 | Date | Wed, 22 Nov 2000 23:40:36 -0700 (MST) |
| |
Mohammad A. Haque writes: > I just got these while doing many compiles on my box .... > > Nov 23 00:40:06 viper kernel: EXT2-fs warning (device ide0(3,3)): > ext2_unlink: Deleting nonexistent file (622295), 0 > Nov 23 00:40:06 viper kernel: = 1 > Nov 23 00:40:06 viper kernel: EXT2-fs error (device ide0(3,3)): > ext2_free_blocks: Freeing blocks not in datazone - block = 540028982, > count = 1 > Nov 23 00:40:06 viper kernel: EXT2-fs error (device ide0(3,3)): > ext2_free_blocks: Freeing blocks not in datazone - block = 540024880, > count = 1 > Nov 23 00:40:06 viper kernel: EXT2-fs error (device ide0(3,3)): > ext2_free_blocks: Freeing blocks not in datazone - block = 170926128, > count = 1
I'm not sure where the nonexistent file comes from. According to the printf statement, you're trying to unlink a file with no links, so it would be interesting to see if 622295 is a valid inode number (it should be, or there would have been more error messages). Doing
dumpe2fs -h /dev/hda3
may help to find out where this bogus inode came from.
These block numbers decode to ASCII data:
540028982 = 0x20303036 = " 336" 540024880 = 0x20302030 = " 3 3" 170926128 = 0x0a302030 = "\n3 3"
There were problems like this quite a while ago (block numbers that are really ASCII data)... I can't recall what the problem turned out to be at that time.
I would suggest a full fsck to start with (you have probably already done so). If you haven't done a full fsck on this filesystem in a long time, there is a chance the corruption was from the old kernel bug.
Cheers, Andreas -- Andreas Dilger \ "If a man ate a pound of pasta and a pound of antipasto, \ would they cancel out, leaving him still hungry?" http://www-mddsp.enel.ucalgary.ca/People/adilger/ -- Dogbert - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org Please read the FAQ at http://www.tux.org/lkml/
|  |