From: Vitaly Fertman <vitaly@namesys.com>
To: Jan De Luyck <lkml@kcore.org>, linux-kernel@vger.kernel.org
Subject: Re: forwarded message from Jan De Luyck
Date: Wed, 10 Dec 2003 16:04:15 +0300 [thread overview]
Message-ID: <200312101604.15299.vitaly@namesys.com> (raw)
In-Reply-To: <16343.2023.525418.637117@laputa.namesys.com>
Hello,
> Hello,
>
> Today I discovered this in my syslogs, after something strange
> happening to XFree86 (hung at startup, then dumped me back to the console)
>
> is_leaf: free space seems wrong: level=1, nr_items=41, free_space=65224
> rdkey vs-5150: search_by_key: invalid format found in block 283191. Fsck?
> vs-13070: reiserfs_read_locked_inode: i/o failure occurred trying to find
> stat data of [11 12795 0x0 SD] is_leaf: free space seems wrong: level=1,
> nr_items=41, free_space=65224 rdkey vs-5150: search_by_key: invalid format
> found in block 283191. Fsck? vs-13070: reiserfs_read_locked_inode: i/o
> failure occurred trying to find stat data of [11 12798 0x0 SD]
this all about fs corruptions. fsck is needed.
> I've never seen these before, and I've been digging through my syslogs but
> am unable to find any other references of this.
> Does this mean the disk is dying? Or just the filesystem is corrupt?
> Unfortunately, I'm not able to rebuild the tree at this time because I
> haven't got a 'rescue' disk with me and the errors are on my root
> partition...
>
> Any other pointers?
reiserfsck from the 3.6.12-pre1 package is able to recover mounted ro
partitions.
--
Thanks,
Vitaly Fertman
next parent reply other threads:[~2003-12-10 12:03 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <16343.2023.525418.637117@laputa.namesys.com>
2003-12-10 13:04 ` Vitaly Fertman [this message]
2003-12-10 13:59 ` forwarded message from Jan De Luyck Jan De Luyck
2003-12-10 19:54 ` Hans Reiser
2003-12-10 21:02 ` Vitaly Fertman
2003-12-10 21:24 ` Hans Reiser
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200312101604.15299.vitaly@namesys.com \
--to=vitaly@namesys.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lkml@kcore.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.