From: Evan Harris <eharris@puremagic.com>
To: Alasdair G Kergon <agk@redhat.com>
Cc: Linux Kernel List <linux-kernel@vger.kernel.org>
Subject: Re: ext3-fs transient corruption with devmapper over md raid, kernel 2.6.16.14
Date: Fri, 26 May 2006 14:35:48 -0500 (CDT) [thread overview]
Message-ID: <Pine.LNX.4.62.0605261425160.19083@kinison.puremagic.com> (raw)
In-Reply-To: <20060523221547.GA1002@agk.surrey.redhat.com>
Luckily the filesystem had no important data on it yet, so I have been
testing various changes.
First I changed the mount from ext3 to plain ext2, and that eventually
produced a series of errors like this:
May 24 03:15:18 localhost kernel: init_special_inode: bogus i_mode (2640)
May 24 03:15:29 localhost kernel: init_special_inode: bogus i_mode (175015)
May 24 03:15:29 localhost kernel: init_special_inode: bogus i_mode (11)
May 24 03:15:29 localhost kernel: init_special_inode: bogus i_mode (161265)
May 24 03:15:29 localhost kernel: init_special_inode: bogus i_mode (0)
May 24 03:15:29 localhost kernel: attempt to access beyond end of device
May 24 03:15:29 localhost kernel: dm-0: rw=0, want=8341843240, limit=2930302464
May 24 03:15:30 localhost kernel: attempt to access beyond end of device
May 24 03:15:30 localhost kernel: dm-0: rw=0, want=9187258480, limit=2930302464
May 24 03:15:30 localhost kernel: attempt to access beyond end of device
May 24 03:15:30 localhost kernel: dm-0: rw=0, want=9184366040, limit=2930302464
May 24 03:15:30 localhost kernel: attempt to access beyond end of device
May 24 03:15:30 localhost kernel: dm-0: rw=0, want=9182932112, limit=2930302464
May 24 03:15:30 localhost kernel: attempt to access beyond end of device
May 24 03:15:30 localhost kernel: dm-0: rw=0, want=8994978168, limit=2930302464
May 24 03:15:30 localhost kernel: attempt to access beyond end of device
May 24 03:15:30 localhost kernel: dm-0: rw=0, want=9187258480, limit=2930302464
May 24 03:15:30 localhost kernel: attempt to access beyond end of device
Then I tried changing from dm-crypt to dm-linear and have not been able to
reproduce the problem using dm-linear. Unfortunately, the test conditions
are not exactly the same because using the dm-crypt module completely pegs
the cpu, while using the linear module is disk-bound not io-bound and the
cpu utilization is MUCH lower.
However, this leads me to suspect that the problem is either in dm-crypt, or
a data corruption problem resulting from a decrypt error from the aes_x86_64
module that dm-crypt is using.
One thing I forgot to mention before is this is on a dual-core box. Just in
case the problem may be related to SMP, I'm planning to try recompiling for
a non-SMP kernel and go back to using dm-crypt and see if I can still
produce the error that way.
If anyone has variations that would be more useful, I can try to test those
first.
Evan
On Tue, 23 May 2006, Alasdair G Kergon wrote:
> On Tue, May 23, 2006 at 01:26:32PM -0500, Evan Harris wrote:
>> I just recently upgraded a machine to use devmapper for an encrypted
>> filesystem on top of a software raid5 array. System is running a
>> stock 2.6.16.14 kernel with no additional patches.
>
>> Happy to provide any further info that may be useful.
>
> This might not be practical for you, but what we're looking for
> is people who can reproduce this on a test system where they can
> try varying things one-at-a-time. For example, replace dm-crypt
> with dm-linear (e.g. a standard unencrypted LVM2 logical volume);
> replace raid5 with (md) linear. Also test with the latest
> development kernels to see if recent md patches fixed the problem.
>
> Alasdair
> --
> agk@redhat.com
next prev parent reply other threads:[~2006-05-26 19:36 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-23 18:26 Evan Harris
2006-05-23 22:15 ` Alasdair G Kergon
2006-05-26 19:35 ` Evan Harris [this message]
2006-05-26 20:30 ` Alasdair G Kergon
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=Pine.LNX.4.62.0605261425160.19083@kinison.puremagic.com \
--to=eharris@puremagic.com \
--cc=agk@redhat.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
all inboxes | Powered by JetHome®