On Tue, 15 Feb 2005, Eben King wrote:
> I just got 63 of these, all for the same inode:
>
> 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
>
> They killed X, and eventually caused an "oops". hda3 is my root fs (1.5 GB,
> 452 MB used), which is indeed ext3. What should I do? I rebooted (had to
> because of the oops), and it works for now. Maybe it hasn't tried to read
> that inode yet. How do I find out what's there? Is "4005720840" decimal or
> hex? Probably decimal, as the odds that it's hex and _none_ of the digits
> are >9 are 0.6%.
Well, it happened again, so 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...
-- -eben ebQenW1@EtaRmpTabYayU.rIr.OcoPm home.tampabay.rr.com/hactar A. A Top Poster \ http://www.fscked.co.uk/ B. Who's there? \ writing/ A. Knock-knock -- from bobward@xxx.com \ top-posting-cuss.html
This archive was generated by hypermail 2.1.3 : Fri Aug 01 2014 - 20:31:06 EDT