All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alex Zarochentsev <zam@namesys.com>
To: Henning Westerholt <henning-04@die.informatik.uni-siegen.de>
Cc: reiserfs-list@namesys.com
Subject: Re: i/o error (lost+found) with reiser4
Date: Mon, 23 Feb 2004 18:20:03 +0300	[thread overview]
Message-ID: <20040223152003.GA1712@backtop.namesys.com> (raw)
In-Reply-To: <200402222338.23623.henning-04@die.informatik.uni-siegen.de>

On Sun, Feb 22, 2004 at 11:38:23PM +0100, Henning Westerholt wrote:
> Hello all,
> 
> after the regular stat data error, i try to fix the fs as usual. Today the 
> fsck program complains the first time about a fatal corruption. I attached 
> the output from the first fsck run.
> 
> I run fsck with option "build-fs" as recommended, and it seems to fix the 
> error. But now a "ls" in the root of the reiser4 partiton complains about a 
> input/ output error on the directory "lost+found". 
> Output from the system log:
> 
> +++++++++
> reiser4[ls(14750)]: check_open_format40 
> (fs/reiser4/plugin/disk_format/disk_format40.c:551)[vpf-1360]:
> WARNING: The object with the oid 3441763 greater then the max used oid 3441762 
> found.
> reiser4[ls(14831)]: check_open_format40 
> [...the same with stat, bash...]
> +++++++++
> 
> Error messages from ls, stat..:
> 
> +++++++++
> # ls /var/tmp/
> ls: /var/tmp/lost+found: Input/output error  
> ccache  distfiles  emerge-webrsync  kdecache-party  portage  portage-pkg  sync 
> 
> # stat /var/tmp/lost+found
> stat: cannot stat `/var/tmp/lost+found': Input/output error
> 
> # cd /var/tmp/lost+found
> -bash: cd: /var/tmp/lost+found: Input/output error
> 
> #fsck.reiser4 /dev/hdd8 
> ...
> No corruption found.
> +++++++++
> 
> Should i rebuild the partition? Is this a know problem?

This is not known but I have an idea why it happened.  I will discuss it with
our fsck maintainer and then we tell you how to fix the corruption. 

Thanks for the report. 

> Best regards,
> 
> Henning

-- 
Alex.

  reply	other threads:[~2004-02-23 15:20 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-02-22 22:38 i/o error (lost+found) with reiser4 Henning Westerholt
2004-02-23 15:20 ` Alex Zarochentsev [this message]
2004-02-23 17:00   ` Alex Zarochentsev
2004-02-23 17:23     ` Alex Zarochentsev
2004-02-23 16:59       ` Henning Westerholt

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=20040223152003.GA1712@backtop.namesys.com \
    --to=zam@namesys.com \
    --cc=henning-04@die.informatik.uni-siegen.de \
    --cc=reiserfs-list@namesys.com \
    /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.