Messages in this thread |  | | | From | (Nick Holloway) | | Subject | Re: ext2 and unlink(2) | | Date | 30 Sep 1997 21:04:58 +0100 |
| |
tytso@MIT.EDU (Theodore Y. Ts'o) writes: > But for > some reason, there are cases where the Linux kernel is getting confused > enough to scribble random data on an inode table.
Spooky. I read your message at home in the morning. Just over an hour later, when I happened to be in the machine room, the main Linux machine at work ate a filesystem.
attempt to access beyond end of device 16:01: rw=0, want=942814853, limit=768064 Kernel panic: EXT2-fs panic (device 16:01): ext2_write_inode: unable to read i-node block - inode=331778, block=942814852 attempt to access beyond end of device 16:01: rw=0, want=892678965, limit=768064 Kernel panic: EXT2-fs panic (device 16:01): ext2_read_inode: unable to read i-node block - inode=265721, block=892678964 attempt to access beyond end of device 16:01: rw=0, want=221853494, limit=768064 Kernel panic: EXT2-fs panic (device 16:01): read_block_bitmap: Cannot read block bitmap - block_group = 71, block_bitmap = 221853493
Does this look like the same sort of problem?
Fsck was not happy (duplicated blocks, etc) but did say it had fixed it. As the partition involved was an nntp cache, and corrupt data is worse than no data, I remade it, and no badblocks were reported.
This is Linux 2.0.30, running on a Dell XPS/90, and the disk involved was an IDE (Seagate ST52520A, 2446MB). The disk the most recent addition (several months ago) to a machine that has been in service for a couple of years.
The machine is running apache, bind, squid, nntpcache, innd. I know that nntpcache is a heavy user of mmaped files shared between processes.
-- `O O' | Nick.Holloway@alfie.demon.co.uk http://www.alfie.demon.co.uk/ // ^ \\ | Nick.Holloway@parallax.co.uk http://www.parallax.co.uk/~alfie/
|  |