From: Oleg Drokin <green@namesys.com>
To: Patrik Wallstrom <pawal@blipp.com>
Cc: reiserfs-list@namesys.com
Subject: Re: reiserfsck --rebuild-tree is very slow
Date: Mon, 5 Aug 2002 09:04:47 +0400 [thread overview]
Message-ID: <20020805090447.A5678@namesys.com> (raw)
In-Reply-To: <20020804212148.GC6570@vic20.blipp.com>
Hello!
On Sun, Aug 04, 2002 at 11:21:48PM +0200, Patrik Wallstrom wrote:
> The result of reiserfsck --check and the result with --fix-fixable:
> bread: Cannot read a block # 10052279.
Hm, what's in kernel logs, is it filled with I/O errors?
> ####### Pass 0 #######
> Loading on-disk bitmap .. ok, 6110187 blocks marked used
> Skipping 8399 blocks (super block, journal, bitmaps) 6101788 blocks
> will be read
> 0% left 5911812, 2 /sec
> From what I can see, this session can last for many years...
> Any advise?
Look into the kernel logs, if it is filled by many I/O error messages,
then it will indeed may atek a lot of time. Also it is possible that the
drive itself is reading data very slowly (ie it encounters multiple errors
that it tries to correct and this takes huge amount of time, I saw such
behaviour with IBM DTLA drives).
If you can access data on the drive just fine without fsck
(I mean if dd if=/dev/device of=/dev/zero bs=4096k works as fast as expected),
then this may need more investigations.
Bye,
Oleg
next prev parent reply other threads:[~2002-08-05 5:04 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-04 21:21 reiserfsck --rebuild-tree is very slow Patrik Wallstrom
2002-08-05 5:04 ` Oleg Drokin [this message]
2002-08-05 7:37 ` Patrik Wallstrom
2002-08-05 7:42 ` Oleg Drokin
-- strict thread matches above, loose matches on Subject: below --
2002-08-08 21:08 berthiaume_wayne
2002-08-08 21:34 ` Hans Reiser
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=20020805090447.A5678@namesys.com \
--to=green@namesys.com \
--cc=pawal@blipp.com \
--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.