From: Andreas Steinmetz <ast@domdv.de>
To: "Markus Müller" <mm@priv.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Reiserfsck dies
Date: Wed, 03 May 2006 19:52:15 +0200 [thread overview]
Message-ID: <4458EDCF.4030402@domdv.de> (raw)
In-Reply-To: <4458ECE0.7030901@priv.de>
Markus Müller wrote:
> Hi Andreas Steinmetz,
>
>>Markus Müller wrote:
>>
>>
>>>no, the hdd is a software raid 5, /dev/md0, which is piped through aes
>>>via cryptsetup, so it is accessed via /dev/mapper/hdb
>>>
>>>
>>My experience with such a stacking and reiserfs was horrible. Continous
>>filesystem corruption that finally required reformatting. I then
>>replaced reiserfs with ext3 and the stacking works since then.
>>
>>It is not a dm-crypt problem as the symptoms also occurred with
>>raid5/lvm2/reiserfs, so any raidx/dm/reiserfs stacking seems to be only
>>something for the more adventurous folks. Thus I don't know if the
>>problem still exists with current kernels.
>>
>>
> Ok, maybe. I try now to insert 512 MB more RAM into the machine, more
> than 1 Gig I don't have for this system. I only want the raid to work
> just one time, cause there is data I want to (but not in any case) be
> secured. Then I again install ext3 on it... this worked on this raid
> without any problems at all. And the fsck is about 2 houres, not 28
> hours (--rebuild-tree).
>
> I don't think my kernel is to old, do you?
So it seems the problem still exists (lucky me had lots of backup tapes
plus firewire disk backups). I only remember that finally the fs was to
foobar for reiserfsck to recover in my case.
--
Andreas Steinmetz SPAMmers use robotrap@domdv.de
next prev parent reply other threads:[~2006-05-03 17:52 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-03 14:56 Reiserfsck dies Markus Müller
2006-05-03 16:45 ` Jan Engelhardt
2006-05-03 17:19 ` Markus Müller
2006-05-03 17:30 ` Andreas Steinmetz
2006-05-03 17:48 ` Markus Müller
[not found] ` <4458ECE0.7030901@priv.de>
2006-05-03 17:52 ` Andreas Steinmetz [this message]
2006-05-03 17:56 ` Sergey Vlasov
2006-05-03 18:18 ` Markus Müller
2006-05-03 19:12 ` Jan Engelhardt
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=4458EDCF.4030402@domdv.de \
--to=ast@domdv.de \
--cc=linux-kernel@vger.kernel.org \
--cc=mm@priv.de \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox