All of lore.kernel.org
 help / color / mirror / Atom feed
From: Hans Reiser <reiser@namesys.com>
To: Vitaly Fertman <vitaly@namesys.com>
Cc: Oleg Drokin <green@namesys.com>, myciel <myciel@dotcom.pl>,
	reiserfs-list@namesys.com
Subject: Re: fsck in background?
Date: Mon, 31 Mar 2003 22:54:06 +0400	[thread overview]
Message-ID: <3E888ECE.2090301@namesys.com> (raw)
In-Reply-To: <200303312154.35760.vitaly@namesys.com>

Vitaly Fertman wrote:

>On Monday 31 March 2003 21:14, Hans Reiser wrote:
>  
>
>>Oleg Drokin wrote:
>>    
>>
>>>Hello!
>>>
>>>On Mon, Mar 31, 2003 at 12:30:37PM +0200, myciel wrote:
>>>      
>>>
>>>>Yes, I know this sounds strange, but if one have 1T filesystem full of
>>>>small files,
>>>>reiserfsck estimates duration to be of order of months,
>>>>        
>>>>
>>>We have a patch that significantly speeds things up.
>>>In the similar case 28+ years estimated for pass 0 turned into 208 hours
>>>total
>>>      
>>>
>>As I said before, 208 hours is unacceptable and Vitaly needs to do more
>>work on it. If Vitaly doesn't know how to fix it, then I need to review
>>his algorithms in detail.
>>    
>>
>
>As I wrote you the objectid handling is not the problem anymore, and I 
>described also that the performance problem for now is nlink calculation 
>on semantic rebuild pass which needs many writes on disk what is not easy
>to optimize in the case with shared objectids.
>
by shared objectids you mean when more than one file is discovered by 
fsck to have the same oid?  what is the problem?

> Although it could be solved 
>with another pass which would solve all such shared objectid problems just 
>before semantic rebuild pass. 
>
>  
>


-- 
Hans



  reply	other threads:[~2003-03-31 18:54 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-03-31 10:30 fsck in background? myciel
2003-03-31 10:46 ` Oleg Drokin
2003-03-31 17:14   ` Hans Reiser
2003-03-31 17:27     ` Oleg Drokin
2003-03-31 17:54     ` Vitaly Fertman
2003-03-31 18:54       ` Hans Reiser [this message]
2003-04-05  5:37     ` Andreas Dilger
2003-04-07 17:06       ` Hans Reiser
2003-04-08  9:40   ` myciel
2003-04-08 14:28     ` Oleg Drokin
2003-03-31 10:47 ` Robin H. Johnson

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=3E888ECE.2090301@namesys.com \
    --to=reiser@namesys.com \
    --cc=green@namesys.com \
    --cc=myciel@dotcom.pl \
    --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.