All of lore.kernel.org
 help / color / mirror / Atom feed
From: Hans Reiser <reiser@namesys.com>
To: Chris Mason <mason@suse.com>
Cc: "Jure Pečar" <pegasus@nerv.eu.org>,
	reiserfs-list@namesys.com, "Vitaly Fertman" <vitaly@namesys.com>
Subject: Re: online fsck
Date: Thu, 22 Apr 2004 11:14:20 -0700	[thread overview]
Message-ID: <40880B7C.9070009@namesys.com> (raw)
In-Reply-To: <1082657211.12989.111.camel@watt.suse.com>

Chris Mason wrote:

>On Thu, 2004-04-22 at 13:51, Hans Reiser wrote:
>  
>
>>Chris Mason wrote:
>>
>>    
>>
>>>On Thu, 2004-04-22 at 09:00, Jure Peèar wrote:
>>> 
>>>
>>>      
>>>
>>>>Hi all,
>>>>
>>>>Is it theoretically posible?
>>>>
>>>>Like, does it need a drastic redesing of reiserfs or just sufficient $$
>>>>directed to the team to be implemented?
>>>>
>>>>
>>>>Because i think that reiserfsck --check in 12h + --rebuild-tree in 18h is
>>>>still waaay too much downtime for a 500gb mail server...
>>>>   
>>>>
>>>>        
>>>>
>>>Online check is easy, just use lvm or evms to make a snapshot and then
>>>check the snapshot. 
>>>
>>>      
>>>
>>Requires that users use lvm before discovering the need for fsck, but, 
>>yes.  What would be ideal would be some support for finding the 
>>inconsistency on the snapshot, and then fixing it on the real fs using 
>>the information learned from the snapshot fsck.
>>    
>>
>
>Which should be possible, espeically for corruptions at the leaf
>levels.  Things like incorrect i_size, pointers to files that don't
>exist, etc.  Corruptions that require a full blow rebuild-tree will be
>much harder.
>
>I was wrong to say that an online rebuild-tree would be impossible, but
>it certainly does seem tricky.  Basically you could freeze the old tree,
>using it for readonly lookups.  Rebuild to new tree in the background,
>and verify things you find in the old tree in the new tree (to catch a
>file that has been deleted while the FS was mounted but is present in
>the old tree).
>
>-chris
>
>
>
>
>  
>
rebuild-tree would likely  be a major engineering effort which would 
require funding from someone who cared enough to pay for it....., 
finding inconsistencies on a snapshot and applying them to a live system 
would be less difficult but still substantive work.

  reply	other threads:[~2004-04-22 18:14 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20040422150042.5b49c6c3.pegasus@nerv.eu.org>
2004-04-22 13:34 ` online fsck Chris Mason
2004-04-22 14:24   ` Jure Pečar
2004-04-22 15:24     ` Chris Dukes
2004-04-22 15:45       ` Nikita Danilov
2004-04-22 15:58         ` Marcelo Pacheco
2004-04-22 17:11         ` Chris Dukes
2004-04-22 17:51   ` Hans Reiser
2004-04-22 18:06     ` Chris Mason
2004-04-22 18:14       ` Hans Reiser [this message]
2004-04-22 18:15     ` Chris Dukes
2004-04-25 14:10       ` daniel.poelzleithner
2004-04-22 23:20 ` Matthias Andree
2005-05-23 18:24 btinsley
2005-05-24 10:43 ` E.Gryaznova
2005-05-24 23:26   ` marco
2005-05-25  3:02     ` btinsley
2005-05-27  6:15       ` marco
2005-05-27  9:17       ` Philippe Gramoullé
2005-05-27  9:32         ` Yiannis Mavroukakis
2005-05-27 14:12           ` mjt
2005-05-27 22:50           ` David Masover
2005-05-27 23:04             ` btinsley
2005-05-28  7:58     ` Vladimir Saveliev

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=40880B7C.9070009@namesys.com \
    --to=reiser@namesys.com \
    --cc=mason@suse.com \
    --cc=pegasus@nerv.eu.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.