From: Mike Fedyk <mfedyk@matchmail.com>
To: Carl-Daniel Hailfinger <c-d.hailfinger.kernel.2003@gmx.net>
Cc: Kristian Koehntopp <kris@koehntopp.de>,
ReiserFS List <reiserfs-list@namesys.com>
Subject: Re: Strange directories after reisferfsck
Date: Tue, 4 Nov 2003 18:16:44 -0800 [thread overview]
Message-ID: <20031105021644.GB32687@matchmail.com> (raw)
In-Reply-To: <3FA85B48.1050202@gmx.net>
On Wed, Nov 05, 2003 at 03:07:04AM +0100, Carl-Daniel Hailfinger wrote:
> Kristian Koehntopp wrote:
> > If so, wouldn't it be useful not only to have a magic byte
> > marker in each data structure, but also a filesystem generation
> > number, that is unique for each filesystem generated, for
> > example the time_t the filesystem was created. Thus metadata
> > structures from vmdk or loop files would have the same magic
> > bytes as metadata from the main filesystem, but would be
> > recognizeable as belonging to a different tree due to the
> > different generation number.
>
> Yes, but:
> - nobody wants to sponsor that feature
> - reiserfs 3.6 is in feature freeze
> - the on-disk format would be not backwards compatible
>
>
> >>reiser4 will be able to keep reiser4 images in files without such
> >>problems.
> >
> >
> > How does it do that?
>
> By using the ideas you specified. Sorry to disappoint you: your ideas are
> not new, but they are good. Good enough to be incorporated in reiser4.
Does that mean there is no generation number, or random hash in the 3.6
format, or anything else that changes on each fs image that could be keyed
upon?
next prev parent reply other threads:[~2003-11-05 2:16 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-04 6:59 Strange directories after reisferfsck Kristian Koehntopp
2003-11-04 13:54 ` Vitaly Fertman
2003-11-05 1:08 ` Kristian Koehntopp
2003-11-05 2:07 ` Carl-Daniel Hailfinger
2003-11-05 2:15 ` Hans Reiser
2003-11-05 2:16 ` Mike Fedyk [this message]
2003-11-05 2:32 ` Hans Reiser
2003-11-05 16:35 ` Kristian Koehntopp
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=20031105021644.GB32687@matchmail.com \
--to=mfedyk@matchmail.com \
--cc=c-d.hailfinger.kernel.2003@gmx.net \
--cc=kris@koehntopp.de \
--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.