All of lore.kernel.org
 help / color / mirror / Atom feed
From: Edward Shishkin <edward@namesys.com>
To: David Masover <ninja@slaphack.com>
Cc: Hans Reiser <reiser@namesys.com>,
	"E.Gryaznova" <grev@namesys.com>,
	reiserfs-list@namesys.com
Subject: Re: reiser4progs do not handle the reiser4 format changes
Date: Sun, 24 Jul 2005 03:44:39 +0400	[thread overview]
Message-ID: <42E2D667.6060104@namesys.com> (raw)
In-Reply-To: <42E196FB.6080409@namesys.com>

Edward Shishkin wrote:

> David Masover wrote:
>
>>
>>
>> Ok, please explain what this actually means for users.
>>
>> How will an FS made by the current reiser4progs be different than 
>> that made by the new (patched) ones that will be coming out?  Is the 
>> new way better?  If so, how can one take an existing FS and 
>> convert/update/tweak it to the new way?
>>
>
> This is a common scenario:
>
> Each disk reiser4 is supposed to be supported by all kernel/reiser4.


I was wrong here: the only last version of kernel/reiser4 is able
to support _all_ disk file systems. Old kernels will refuse to mount
file systems of new versions with the warning about wrong plugin set
of root inode.

Edward.

>
> Both kernel and reiser4progs have a plugin table which should be 
> upgraded in sync.
> For each point A of upgrading the plugin table all reiser4progs of 
> versions < A
> become invalid for disk reiser4 being once mounted in the 
> kernel/reiser4 of version >= A.
>
> Is it okay?
> Perhaps introducing a special sub-versions of reiser4/reiser4progs for 
> upgrading
> the plugin table will improve the situation..
>
>
> Edward.
>
>>
>>
>
>
>


  reply	other threads:[~2005-07-23 23:44 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-07-20 14:06 reiser4progs do not handle the reiser4 format changes E.Gryaznova
2005-07-20 18:54 ` David Masover
2005-07-21  1:00   ` Edward Shishkin
2005-07-21  7:56     ` Hans Reiser
2005-07-21 10:35       ` Edward Shishkin
2005-07-21 17:35         ` David Masover
2005-07-23  1:01           ` Edward Shishkin
2005-07-23 23:44             ` Edward Shishkin [this message]
2005-07-26 20:02               ` Vitaly Fertman
2005-07-21  8:10     ` Gregory Maxwell
2005-07-21  8:24       ` Hans Reiser
2005-07-21  4:05 ` Hans Reiser

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=42E2D667.6060104@namesys.com \
    --to=edward@namesys.com \
    --cc=grev@namesys.com \
    --cc=ninja@slaphack.com \
    --cc=reiser@namesys.com \
    --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.