All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Vladimir V. Saveliev" <vs@namesys.com>
To: jfeise@feise.com
Cc: reiserfs-list@namesys.com
Subject: Re: Better fsck.reiser4 needed
Date: Wed, 6 Sep 2006 13:04:30 +0400	[thread overview]
Message-ID: <200609061304.30625.vs@namesys.com> (raw)
In-Reply-To: <44FE8041.5060403@feise.com>

Hello

On Wednesday 06 September 2006 12:01, Joe Feise wrote:
> Hi,
>
> It seems that fsck.reiser4 -a doesn't do anything. It doesn't even detect
> corruption.

I think it is made that way with intention. If fsck.reiser4 -a did corruption 
detection bootup process would take long time and users would not have the 
main advantage of journalled filesystems - quick recovering after unclean 
shutdown.

> I had a /var corruption (reiser4 on /var) over the weekend, and since I was
> out of town, the machine was hanging trying to go into multi-user mode 

I guess here you got reiser4 bug where it hanged trying to access corrupted 
partition instead of returning -EIO. Was there anything interesting in logs 
and have you managed to catch them?

> for 
> a day before I could fix the corruption manually. An fsck that actually
> would do some automatic repairs (e.g., like ext3 which I use as the root
> partition) would be really helpful.
> For now, I have resorted to --fix -y at bootup time for all my reiser4
> partitions, but that's just a quick hack, and rather unsatisfactory.
>
> Cheers,
> -Joe

  reply	other threads:[~2006-09-06  9:04 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-09-06  8:01 Better fsck.reiser4 needed Joe Feise
2006-09-06  9:04 ` Vladimir V. Saveliev [this message]
2006-09-06 14:36   ` Joe Feise
2006-09-06 18:24   ` Andreas Dilger

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=200609061304.30625.vs@namesys.com \
    --to=vs@namesys.com \
    --cc=jfeise@feise.com \
    --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.