All of lore.kernel.org
 help / color / mirror / Atom feed
From: Hans Reiser <reiser@namesys.com>
To: Thomas Graham <lkthomas@sml.dyndns.org>
Cc: Vitaly Fertman <vitaly@namesys.com>, reiserfs-list@namesys.com
Subject: Re: http://www.namesys.com/snapshots/2004.08.03-internal.testing/
Date: Wed, 04 Aug 2004 01:44:42 -0700	[thread overview]
Message-ID: <4110A1FA.2030803@namesys.com> (raw)
In-Reply-To: <55083.202.71.232.79.1091590413.squirrel@sml.dyndns.org>

Thomas Graham wrote:

>how long does it take to build-fs for 200GB data HD ? and how many data am
>I going to lost ?
>
>I am just freak out, you guys are promised that disk format wouldn't be
>change anymore, but it still changing actually, pretty upset for that
>statement.
>
>  
>
>>Hello All,
>>
>>This snapshot contains updated reiser4progs-0.5.7 and the grub patch.
>>
>>It includes several bug fixes against the previous snapshot, and has a
>>disk
>>format change -- the layout of blocks that contain backuped fs metadata
>>are changed.
>>
>>No kernel patch is needed for the disk format change, however fsck may
>>report about some corruptions on an existent fs if a block was allocated
>>for some data and has become a backup one. Fsck.reiser4 --build-fs is
>>able to fix it of course, although the data in these blocks are lost then.
>>
>>--
>>Thanks,
>>Vitaly Fertman
>>
>>
>>    
>>
>
>
>  
>
Vitaly, your email is a marvel of unclarity that vaguely threatens of 
losing data in ways that cannot be understood by the reader.  Please 
revise and resend, and don't make disk format changes in the future 
without discussing them with the rest of the team first.  Perhaps you 
should start that discussion of this disk format change now....

Hans

  reply	other threads:[~2004-08-04  8:44 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               ` http://www.namesys.com/snapshots/2004.08.03-internal.testing/ mjt
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       ` Hans Reiser [this message]
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=4110A1FA.2030803@namesys.com \
    --to=reiser@namesys.com \
    --cc=lkthomas@sml.dyndns.org \
    --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.