From: Vitaly Fertman <vitaly@namesys.com>
To: Domenico Andreoli <cavok@tiscali.it>, reiserfs-list@namesys.com
Subject: Re: reiser4 disk formats (was http://www.namesys.com/snapshots/2004.08.09-internal.testing/)
Date: Mon, 16 Aug 2004 13:20:00 +0400 [thread overview]
Message-ID: <200408161320.00782.vitaly@namesys.com> (raw)
In-Reply-To: <20040815232751.GA3627@raptus.homelinux.net>
On Monday 16 August 2004 03:27, Domenico Andreoli wrote:
> On Mon, Aug 16, 2004 at 01:13:38AM +0200, Francesco Biscani wrote:
> > 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?
>
> i'm talking about a message to be put in the reiser4progs 1.0.0 package.
> when the user reads the message she will not have any older version
> around. so this sequence dosen't suit my needs :(
>
> if you are right about fixing things before debugfs.reiser4 may loose
> data, then the right sequence is the one from Vitaly.
>
> what is confusing me is Vitaly saying:
>
> "The converter (debugfs.reiser4 -C) is supposed to be run on consistent
> fs of course, so probably it is worth to check/fix it with the current
> reiser4progs before any update."
>
> probably with "... any update." he meant also the update of the
> reiser4progs package to 1.0.0, doesn't him?
right, the current progs before update.
--
Thanks,
Vitaly Fertman
next prev parent reply other threads:[~2004-08-16 9:20 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
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 [this message]
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=200408161320.00782.vitaly@namesys.com \
--to=vitaly@namesys.com \
--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.