From: eazgwmir@umail.furryterror.org (Zygo Blaxell)
To: reiserfs-list@namesys.com
Subject: Re: reiserfsck --rebuild-tree on a big filesystem
Date: Thu, 19 Dec 2002 16:51:23 +0000 (UTC) [thread overview]
Message-ID: <atsteb$44s$1@genki.hungrycats.org> (raw)
In-Reply-To: 20021125174846.A31778@namesys.com
This thread is rather old, but I have basically the same problem...
In article <20021125174846.A31778@namesys.com>,
Oleg Drokin <green@namesys.com> wrote:
>On Mon, Nov 25, 2002 at 03:36:34PM +0100, Mira Temp?r wrote:
>> my setup:
>> linux 2.4.18 SMP, HW RAID5, nearly full 240GB reiserfs of mostly small files,
>> reiserprogs 3.6.4.
>> With advice to run --rebuild-tree.
Mine:
Linux 2.4.18 UP (SMP kernel), SW RAID0 and linear, nearly full 160GB
reiserfs of mostly small files, reiserfsprogs 1:3.6.3-1 (Debian). I had
two machines go through a power failure while doing lots of concurrent
hard links and deletes. The linear system survived apparently intact,
while the RAID0 system had the usual "stat Permission denied"
problem.
This has happened a number of times before on a variety of systems
(it seems to be reiserfs's most common failure mode). The events are
very similar each time. AFAICT you just have to set up a reiserfs on
some kind of RAID system and let it run through a few power failures to
reproduce the problem.
>> But after 16 hours of running it, it is still on 0% and whole process
>> would take about 1 month to complete (started at 2000 blocks/sec,
>> but now running at 26b/s).
My reiserfsck --rebuild-tree has been running for a little over an hour
and has degraded to 49 blocks/sec (about 10 days). r-fsck absorbs all
the CPU it can get. The reiserfsck process's memory usage increases by
about 8 bytes per block read, and as far as I can tell all of the RAM
allocated after the first 24 megs or so is active (I determine this by
creating a large process to swap out all the inactive pages, then
counting what remains). Nothing is physically wrong with the disks,
it was just another power failure.
Based on past events, the read speed will probably degrade to zero in a
week or two, if the reiserfsck process doesn't run out of RAM+swap first.
It only takes 20 days to repopulate the disk, so in the past when this
happens I usually just mkreiserfs (or mke2fs -j!) and move on. I've never
seen a reiserfsck --rebuild-tree run to completion.
If you feel that 'debugreiserfs -p ... | bzip2' output would be helpful,
I could generate it, but that's about 40GB of data.
--
Opinions expressed are my own, I don't speak for my employer, and all that.
Encrypted email preferred. Go ahead, you know you want to. ;-)
OpenPGP at work: 3528 A66A A62D 7ACE 7258 E561 E665 AA6F 263D 2C3D
next prev parent reply other threads:[~2002-12-19 16:51 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-25 14:36 reiserfsck --rebuild-tree on a big filesystem Mira Tempír
2002-11-25 14:48 ` Oleg Drokin
[not found] ` <20021125153154.GA19254@mail.cekit.cz>
2002-11-25 15:44 ` Oleg Drokin
2002-11-26 22:56 ` Mira Tempir
2002-11-27 7:33 ` Oleg Drokin
2002-11-27 12:46 ` Vitaly Fertman
2002-11-27 13:38 ` Mira Tempir
2002-12-19 16:51 ` Zygo Blaxell [this message]
2002-12-19 17:00 ` Oleg Drokin
2002-12-19 20:09 ` Zygo Blaxell
2002-12-20 16:12 ` Zygo Blaxell
2002-12-23 7:54 ` Hans Reiser
2002-12-23 7:59 ` Oleg Drokin
2002-11-25 14:59 ` Anders Widman
2002-11-26 10:58 ` SPAMTEST Alexander Lyamin
-- strict thread matches above, loose matches on Subject: below --
2002-11-25 15:38 reiserfsck --rebuild-tree on a big filesystem Mira Tempír
2002-11-27 4:52 ` Todd Lyons
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='atsteb$44s$1@genki.hungrycats.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.