All of lore.kernel.org
 help / color / mirror / Atom feed
From: Hans Reiser <reiser@namesys.com>
To: Vitaly Fertman <vitaly@namesys.com>
Cc: "Markus TЖrnqvist" <mjt@nysv.org>, reiserfs-list@namesys.com
Subject: Re: http://www.namesys.com/snapshots/2004.08.03-internal.testing/
Date: Wed, 04 Aug 2004 01:51:22 -0700	[thread overview]
Message-ID: <4110A38A.7040807@namesys.com> (raw)
In-Reply-To: <200408031819.51600.vitaly@namesys.com>

Vitaly Fertman wrote:

>On Tuesday 03 August 2004 17:58, Markus Törnqvist wrote:
>  
>
>>On Tue, Aug 03, 2004 at 05:50:00PM +0400, Vitaly Fertman wrote:
>>    
>>
>>>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.
>>>      
>>>
These blocks refers to blocks that were used by files and are now backup 
super blocks?  These blocks could be critical database files, etc.?

If yes, then please pull this off our website until you come up with a 
scheme that I am sure will not create more user problems than it solves, 
on average.

>>What kind of probabilities and amounts of data are we talking about?
>>    
>>
>
>The first gig has 22 backup blocks and they are distributed expotentially.
>The first backup copy was probably almost always used for other needs.
>
>  
>


  reply	other threads:[~2004-08-04  8:51 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         ` Hans Reiser [this message]
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       ` 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=4110A38A.7040807@namesys.com \
    --to=reiser@namesys.com \
    --cc=mjt@nysv.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.