> EXT3-fs error (device ide0(3,3)): ext3_get_inode_loc: bad inode number: 4005720840
> EXT3-fs error (device ide0(3,3)) in ext3_reserve_inode_write: IO failure
Did those messages scrolling up and up seem to push the sinking
feeling in your stomach lower and lower ;)?
> /dev/hda3 is root (1.5 GB total, ~450 MB used). Thodr messages are in the
> log too, 63 of them, all referring to the same inode. (For future
> reference, how do I find out what's at inode X?)
I don't know, but a good start would be to e2image it ASAP, fish
around and see if you can hook any help from someone on the
ext2-devel@lists.sourceforge.net or ext3-users@redhat.com ml's, or
possibly comp.os.linux.misc.
>
> Going to tty7 must have ticked it off, because it "oops"ed then.
>
> OK, maybe it's a fluke, and fsck will fix it. No dice, after restart (still
> in console mode) it crashed again. Fine. I booted from the System Rescue
> CD (handy tool, that), tarred up everything on /dev/hda3, mkfs'd a new
> filesystem, restored the files, fixed the bootloader and restarted. So far
> so good...
Any messages during your tar?
You got something bogus written to a directory block.
~ Daniel
-----------------------------------------------------------------------
This list is provided as an unmoderated internet service by Networked
Knowledge Systems (NKS). Views and opinions expressed in messages
posted are those of the author and do not necessarily reflect the
official policy or position of NKS or any of its employees.
This archive was generated by hypermail 2.1.3 : Fri Aug 01 2014 - 19:14:11 EDT