From: Pavol Luptak <P.Luptak@sh.cvut.cz>
To: linux-kernel@vger.kernel.org
Cc: linux-raid@vger.kernel.org
Subject: SW RAID5 + cryptoloop problem: data corruption in 2.6.3
Date: Sun, 22 Feb 2004 15:09:29 +0100 [thread overview]
Message-ID: <20040222140928.GG29211@psilocybus> (raw)
[-- Attachment #1: Type: text/plain, Size: 2222 bytes --]
Hello,
I created software RAID5 from 4 disks (two Western Digital 120 GB JB 8MB and
another two Western Digital 120 GB Serial ATA) each on a separate channel
using standart AMD/nVidia IDE disk driver and SII 3112 serial ATA disk
driver. I use A7N8X Deluxe mainboard and the latest vanilla 2.6.3 kernel.
For the RAID I choosed left-symmetric parity-algoritm and 256 kb chunksize
(I found this value is optimal for my purposes). I set up crypto loop device on
my raid device and choosed AES for encryption. On the loop device I created
ext2 filesystem using 'mke2fs -b 4096 -R stride=64 /dev/loop0'. I mounted this
device and started to copying about the 250 GB of data from unencrypted IDE
disk to the encrypted RAID (it took a lot of hours with permanent load average
7.0-8.0).
I got a lot of these messages in the random time interval (for a few minutes
after one or two hours)
Feb 21 13:58:45 psil kernel: init_special_inode: bogus i_mode (54131)
Feb 21 13:58:47 psil kernel: init_special_inode: bogus i_mode (162354)
Feb 21 13:58:47 psil kernel: init_special_inode: bogus i_mode (52412)
Feb 21 15:23:27 psil kernel: init_special_inode: bogus i_mode (54131)
Feb 21 15:23:28 psil kernel: init_special_inode: bogus i_mode (171767)
Feb 21 15:23:29 psil kernel: init_special_inode: bogus i_mode (153374)
Feb 21 15:45:54 psil kernel: init_special_inode: bogus i_mode (165515)
Feb 21 16:45:26 psil kernel: init_special_inode: bogus i_mode (54131)
Feb 21 16:45:27 psil kernel: init_special_inode: bogus i_mode (153374)
Feb 21 22:53:14 psil kernel: init_special_inode: bogus i_mode (54131)
Feb 21 22:53:17 psil kernel: init_special_inode: bogus i_mode (50242)
..
Each message corresponds to the invalid (and unusable) creation of file on my
crypto RAID (creation of invalid i-node).
I have no problem with cryptoloop + SW RAID1 (two parallel ATA disks) on
2.6.1/2.6.2.
Can someone explain this behaviour?
I have no idea if this problem is in SII3122 disk driver, RAID5 or cryptoloop
driver.
Regards,
Pavol Luptak
--
_____________________________________________________________________________
[wilder@hq.sk] [http://trip.sk/wilder/] [talker: ttt.sk 5678] [ICQ: 133403556]
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
reply other threads:[~2004-02-22 14:09 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20040222140928.GG29211@psilocybus \
--to=p.luptak@sh.cvut.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-raid@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;
as well as URLs for NNTP newsgroup(s).