All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Markus Müller" <mm@priv.de>
To: Andreas Steinmetz <ast@domdv.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Reiserfsck dies
Date: Wed, 03 May 2006 19:48:38 +0200	[thread overview]
Message-ID: <4458ECF6.8060602@priv.de> (raw)
In-Reply-To: <4458E8C4.3060902@domdv.de>

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?

stacker:/# uname -a
Linux stacker.websrv.de 2.6.16.9 #2 SMP PREEMPT Sun Apr 30 09:44:06 CEST 
2006 i686 GNU/Linux
stacker:/#

Regards,
Markus Mueller


  reply	other threads:[~2006-05-03 17:48 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 [this message]
     [not found]       ` <4458ECE0.7030901@priv.de>
2006-05-03 17:52         ` Andreas Steinmetz
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=4458ECF6.8060602@priv.de \
    --to=mm@priv.de \
    --cc=ast@domdv.de \
    --cc=linux-kernel@vger.kernel.org \
    /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.