All of lore.kernel.org
 help / color / mirror / Atom feed
From: <doiggl@velocitynet.com.au>
To: Christian Kujau <lists@nerdbynature.de>
Cc: reiserfs-devel@vger.kernel.org
Subject: Re: Fwd: fsck.reiser4 questions
Date: Fri, 24 Jun 2016 17:51:52 +1000	[thread overview]
Message-ID: <82ddbedfaee2bef953eef731b971445a@mail.velocitynet.com.au> (raw)
In-Reply-To: <alpine.DEB.2.20.12.1606231501530.28615@trent.utfs.org>

On Thu, 23 Jun 2016 15:21:40 -0700 (PDT), Christian Kujau
<lists@nerdbynature.de> wrote:
> On Fri, 24 Jun 2016, doiggl@velocitynet.com.au wrote:
>> Is fsck broken in version reiser4progs-1.1.0  ?
>> What reiser4 checks and tests can I run on the the r4 meta data to see
if
>> it is  ok ? 
>> Packed with 
>> - I packed r4 meta-data with command
>> # debugfs.reiser4 -P /dev/sdb  | gzip -9 > r4meta-sdb.gz
> 
> See debugfs.reiser4(8): once you've packed metadata, you can unpack it
and 
> write to a different device and use fsck.reiser4 on it. But...what are
you 
> trying to do?

> Christian.

Hello,
reiser4progs] fsck.reiser4 commands fail to repair file system [1] is the
reason I ask for this.

[1]

 --build-sb
 --build-fs 
 --fix

e.g
# fsck.reiser4 --build-sb --build-sb /dev/sdb
# fsck.reiser4 --build-fs --build-fs /dev/sdb
# fsck.reiser4 --fix  /dev/sdb

# fsck.reiser4 --fix --help
Usage: fsck.reiser4 [ options ] FILE
Fsck options:
  --check                       checks the consistency (default)
  --fix                         fixes minor corruptions
  --build-sb                    rebuilds the super block
  --build-fs                    rebuilds the filesystem
.
.
.


      reply	other threads:[~2016-06-24  7:51 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-23 14:24 Fwd: fsck.reiser4 questions doiggl
2016-06-23 22:21 ` Christian Kujau
2016-06-24  7:51   ` doiggl [this message]

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=82ddbedfaee2bef953eef731b971445a@mail.velocitynet.com.au \
    --to=doiggl@velocitynet.com.au \
    --cc=lists@nerdbynature.de \
    --cc=reiserfs-devel@vger.kernel.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.