From: Francesco Biscani <frbiscani@jumpy.it>
To: reiserfs-list@namesys.com
Cc: Domenico Andreoli <cavok@tiscali.it>
Subject: Re: reiser4 disk formats (was http://www.namesys.com/snapshots/2004.08.09-internal.testing/)
Date: Mon, 16 Aug 2004 01:13:38 +0200 [thread overview]
Message-ID: <200408160113.38791.frbiscani@jumpy.it> (raw)
In-Reply-To: <20040815225501.GA8679@raptus.homelinux.net>
Hi,
On Monday 16 August 2004 00:55, Domenico Andreoli wrote:
> so the most safe catch-all command sequence should be simply
>
> 1. fsck.reiser4 device
> - do also whatever fsck says is required to bring the fs
> consistent. most probably it will say to use --build-sb and
> then --fix.
> 2. debugfs.reiser4 -C device
> 3. fsck.reiser4 device
> - do again whatever fsck says, most probably --fix is required.
>
> this should bring the fs from whatever disk format it is in to the
> latest one and this *should* happen without data loss. am i right?
I may be wrong here, but as far as I remember reiser4progs 1.x give errors if
used on old disk formats. If you try to --fix these errors _before_ changing
format you may lose data. So the best sequence would be:
1. fsck.reiser4 --fix device
(with reiser4progs < 1.x)
2. upgrade to reiser4progs 1.x
3. debugfs.reiser4 -C device
4. fsck.reiser4 --fix device
This way you fix all real errors (possibly) present _before_ converting the
layout, and you avoid the (false) errors reported by reiser4progs 1.x on old
disk layouts. Can someone confirm?
Regards,
Francesco
next prev parent reply other threads:[~2004-08-15 23:13 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-13 17:18 reiser4 disk formats (was http://www.namesys.com/snapshots/2004.08.09-internal.testing/) Domenico Andreoli
2004-08-13 17:25 ` Domenico Andreoli
2004-08-15 11:24 ` Vitaly Fertman
2004-08-15 22:55 ` Domenico Andreoli
2004-08-15 23:13 ` Francesco Biscani [this message]
2004-08-15 23:27 ` Domenico Andreoli
2004-08-15 23:38 ` Francesco Biscani
2004-08-15 23:50 ` Domenico Andreoli
2004-08-16 9:20 ` Vitaly Fertman
2004-08-16 9:18 ` Vitaly Fertman
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=200408160113.38791.frbiscani@jumpy.it \
--to=frbiscani@jumpy.it \
--cc=cavok@tiscali.it \
--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.