On Tue, 15 Feb 2005, smitty wrote:
> On Tuesday 15 February 2005 18:35, Eben King wrote:
> > 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...
> I use Reiser 3.6 based on an evaluation I made of four journaling filesystems.
> I have never had a problem with Reiser 3.6 or 3.5 for that matter. Looking
> forward to a stable Reiser4.
This time,I initially had formatted it as reiserfs, but the kernel failed to
mount it because reiserfs is a module (I don't use an initrd), not compiled
in as ext3 is. I aim to rectify that next time I have the kernel source
open.
Some people decry reiserfsck's ability. Have you had to recover data from a
damaged reiserfs filesystem?
--
-eben ebQenW1@EtaRmpTabYayU.rIr.OcoPm home.tampabay.rr.com/hactar
A: Because it looks dumb and is hard to read.
Q: Why is top-posting wrong? -- from lots42@xxx.com
http://www.fscked.co.uk/writing/top-posting-cuss.html
This archive was generated by hypermail 2.1.3 : Fri Aug 01 2014 - 20:31:09 EDT