All of lore.kernel.org
 help / color / mirror / Atom feed
From: eazgwmir@umail.furryterror.org (Zygo Blaxell)
To: reiserfs-list@namesys.com
Subject: Re: About direntries pointing to nowhere on reiserfs problem in 2.4
Date: 24 Feb 2003 22:45:18 -0500	[thread overview]
Message-ID: <b3eose$crj$1@satsuki.furryterror.org> (raw)
In-Reply-To: 200302242159.15769.vitaly@namesys.com

In article <200302242159.15769.vitaly@namesys.com>,
Vitaly Fertman  <vitaly@namesys.com> wrote:
>> Reiserfsck takes 53 hours to scan everything on some of my machines,
>> which is a long time considering that I already know where all the
>> missing direntries are since they are recorded in various error log files.
>
>which version of reiserfsprogs do you use? and is this in the rebuild-tree mode?
>if it is, 3.6.5-pre1 had a speedup for pass0. 

This is 3.6.5-pre1 in --fix-fixable mode.  600 GB of data, average file size
12K.  It currently takes about 8-10 days to dump all of the data to tape.

>P.S. btw, I am going to release a new version of fsck which has some on-boot 
>time checks. Is it possible to try it on your big partitions to fugure out 
>if it takes less then a few seconds?

I could probably fit in a few short tests.

-- 
Zygo Blaxell (Laptop) <zblaxell@feedme.hungrycats.org>
GPG = D13D 6651 F446 9787 600B AD1E CCF3 6F93 2823 44AD

  reply	other threads:[~2003-02-25  3:45 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-02-20 14:53 About direntries pointing to nowhere on reiserfs problem in 2.4 Oleg Drokin
2003-02-21  7:11 ` Manuel Krause
2003-02-21  7:14   ` Oleg Drokin
     [not found] ` <20030220154924.7171cbd7.akpm@digeo.com>
2003-02-21 19:03   ` 2.4 iget5_locked port attempt to 2.4 Oleg Drokin
2003-02-21 20:04     ` Jan Harkes
2003-02-22  9:29       ` Oleg Drokin
2003-02-24 10:21       ` 2.4 iget5_locked port attempt to 2.4 (supposedly fixed NFS version this time) Oleg Drokin
2003-02-24 16:50         ` Trond Myklebust
2003-02-24 17:02           ` Trond Myklebust
2003-02-24 17:03           ` Oleg Drokin
2003-02-24 17:17             ` Trond Myklebust
2003-02-24 17:26               ` Oleg Drokin
2003-02-24 17:33                 ` Trond Myklebust
2003-02-24 17:38                   ` Oleg Drokin
2003-03-03 14:09       ` 2.4 iget5_locked port attempt to 2.4 Oleg Drokin
2003-03-03 16:25         ` Alan Cox
2003-03-03 15:35           ` Nikita Danilov
2003-03-03 15:38           ` Oleg Drokin
2003-03-03 15:57             ` Anton Altaparmakov
2003-03-03 16:04               ` Oleg Drokin
2003-03-03 16:27                 ` Anton Altaparmakov
2003-03-03 16:45                   ` Oleg Drokin
2003-03-03 16:50             ` Jan Harkes
2003-03-03 16:57               ` Oleg Drokin
2003-03-03 17:23               ` Jan Harkes
2003-02-24 17:49 ` About direntries pointing to nowhere on reiserfs problem in 2.4 Zygo Blaxell
2003-02-24 18:59   ` Vitaly Fertman
2003-02-25  3:45     ` Zygo Blaxell [this message]
2003-02-25 12:39       ` Vitaly Fertman
2003-02-25 18:11         ` Zygo Blaxell
2003-02-25 19:35           ` Vitaly Fertman
2003-02-25  7:04   ` Oleg Drokin
2003-02-25 12:01     ` Hans Reiser
2003-02-25 12:31       ` Oleg Drokin
2003-02-28  4:15 ` Zygo Blaxell
2003-02-28  7:46   ` Oleg Drokin

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='b3eose$crj$1@satsuki.furryterror.org' \
    --to=eazgwmir@umail.furryterror.org \
    --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.