From: Andrea Gelmini <andrea.gelmini@gmail.com>
To: linux-kernel@vger.kernel.org
Subject: 2.6.16/MD/DM-crypt/fs corruption
Date: Wed, 3 May 2006 11:16:53 +0200 [thread overview]
Message-ID: <20060503091653.GA5940@gelma.net> (raw)
Hi all,
to make short a long story:
a) five pata disks Maxtor 500GB each one;
b) one big software raid 5 (/dev/md1);[1]
c) dmcrypt-ing /dev/md1;[2]
d) after 500GB copied I've got fs corruption;[3]
vanilla kernel, well tested hardware,[4] debian testing (to have
dm-crypt).
I'm using same configuration (md+dm-crypt+ext2/3) on other server,
without problem, from years.
It's first time I use it on big partitions (1.9TB), sure there are
situations with much bigger storage, and it's first time I've got
problems. So:
a) is anybody outthere using this kind of configuration with
success?
b) what can I do to debug the problem? I've spent last weeks
working on hardware (dell servers mostly), to be sure to avoid
hardware problems;
c) has someone (OSDL?) regression tests on md+dm-crypt?
Thanks a lot for your time,
gelma
----
[1] /root/mdadm -Cv /dev/md1 --bitmap-chunk=1024 --chunk=256 \
--assume-clean --bitmap=internal -l5 -n5 /dev/hd[aefgh]
[2] mkfs.ext3 -L 'tritone' -m0 -N 5000000 /dev/mapper/raidone
[3] usually metadata, files checksum is good, but I have a lot of files in
/lost+found, after fsck, and sometimes I have to use debugfs to
unlink some of them (chatt/lsatt doesn't work on them). I can see the
problem with ext2/ext3/reiserfs.
[4] memtest and so on. I also tried the same box of disks on totally
different hardware, with same results. changed from ATA cable to RAM.
I tried also different IDE controller (the one on motherbords, old HPT
370/372, new HPT 302).
next reply other threads:[~2006-05-03 9:17 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-03 9:16 Andrea Gelmini [this message]
2006-05-03 15:50 ` 2.6.16/MD/DM-crypt/fs corruption Andrea Gelmini
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=20060503091653.GA5940@gelma.net \
--to=andrea.gelmini@gmail.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox