From: mjt@nysv.org
To: Vitaly Fertman <vitaly@namesys.com>
Cc: Hans Reiser <reiser@namesys.com>, reiserfs-list@namesys.com
Subject: Re: http://www.namesys.com/snapshots/2004.08.03-internal.testing/
Date: Wed, 4 Aug 2004 13:52:08 +0300 [thread overview]
Message-ID: <20040804105208.GO1284@nysv.org> (raw)
In-Reply-To: <200408041434.41816.vitaly@namesys.com>
On Wed, Aug 04, 2004 at 02:34:41PM +0400, Vitaly Fertman wrote:
>the previous bakup layout had backup block locations depending on the fs
>size, in other words every resize operation may need to relocate some nodes
>in the tree to other blocks if the current ones are needed for the backup --
>even on expanding. there are no such problems with the current backup layout.
OK, this is a good enough motivation.
But does it have to be done here with fsck with data loss, is there no
other way around?
--
mjt
next prev parent reply other threads:[~2004-08-04 10:52 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-14 20:22 http://www.namesys.com/snapshots/2004.06.14-internal.testing/ Vitaly Fertman
2004-06-14 21:05 ` http://www.namesys.com/snapshots/2004.06.14-internal.testing/ mjt
2004-06-14 21:27 ` http://www.namesys.com/snapshots/2004.06.14-internal.testing/ Vitaly Fertman
2004-06-16 11:58 ` http://www.namesys.com/snapshots/2004.06.14-internal.testing/ Vitaly Fertman
2004-06-16 15:44 ` http://www.namesys.com/snapshots/2004.06.14-internal.testing/ Sander Sweers
2004-06-16 16:08 ` http://www.namesys.com/snapshots/2004.06.14-internal.testing/ Vitaly Fertman
2004-07-13 10:27 ` http://www.namesys.com/snapshots/2004.07.13-internal.testing/ Vitaly Fertman
2004-07-13 10:54 ` [PATCH] http://www.namesys.com/snapshots/2004.07.13-internal.testing/ Philippe Gramoullé
2004-07-13 12:06 ` Vitaly Fertman
2004-08-03 13:50 ` http://www.namesys.com/snapshots/2004.08.03-internal.testing/ Vitaly Fertman
2004-08-03 13:58 ` http://www.namesys.com/snapshots/2004.08.03-internal.testing/ mjt
2004-08-03 14:19 ` http://www.namesys.com/snapshots/2004.08.03-internal.testing/ Vitaly Fertman
2004-08-04 8:51 ` http://www.namesys.com/snapshots/2004.08.03-internal.testing/ Hans Reiser
2004-08-04 9:55 ` http://www.namesys.com/snapshots/2004.08.03-internal.testing/ mjt
2004-08-04 10:34 ` http://www.namesys.com/snapshots/2004.08.03-internal.testing/ Vitaly Fertman
2004-08-04 10:52 ` mjt [this message]
2004-08-04 12:49 ` http://www.namesys.com/snapshots/2004.08.03-internal.testing/ Vitaly Fertman
2004-08-04 12:56 ` http://www.namesys.com/snapshots/2004.08.03-internal.testing/ mjt
2004-08-04 12:41 ` http://www.namesys.com/snapshots/2004.08.03-internal.testing/ Philippe Gramoullé
2004-08-04 12:50 ` http://www.namesys.com/snapshots/2004.08.03-internal.testing/ mjt
2004-08-04 13:49 ` http://www.namesys.com/snapshots/2004.08.03-internal.testing/ Chris Mason
2004-08-04 14:16 ` http://www.namesys.com/snapshots/2004.08.03-internal.testing/ Thomas Graham
2004-08-04 14:22 ` http://www.namesys.com/snapshots/2004.08.03-internal.testing/ mjt
2004-08-04 17:47 ` http://www.namesys.com/snapshots/2004.08.03-internal.testing/ Hans Reiser
2004-08-04 18:21 ` http://www.namesys.com/snapshots/2004.08.03-internal.testing/ mjt
2004-08-04 18:51 ` http://www.namesys.com/snapshots/2004.08.03-internal.testing/ Vitaly Fertman
2004-08-04 21:44 ` http://www.namesys.com/snapshots/2004.08.03-internal.testing/ Hans Reiser
2004-08-09 19:49 ` http://www.namesys.com/snapshots/2004.08.09-internal.testing/ Vitaly Fertman
2004-08-04 3:33 ` http://www.namesys.com/snapshots/2004.08.03-internal.testing/ Thomas Graham
2004-08-04 8:44 ` http://www.namesys.com/snapshots/2004.08.03-internal.testing/ Hans Reiser
2004-08-04 10:16 ` http://www.namesys.com/snapshots/2004.08.03-internal.testing/ Vitaly Fertman
2004-08-04 10:28 ` http://www.namesys.com/snapshots/2004.08.03-internal.testing/ mjt
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=20040804105208.GO1284@nysv.org \
--to=mjt@nysv.org \
--cc=reiser@namesys.com \
--cc=reiserfs-list@namesys.com \
--cc=vitaly@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.