linux-kernel - Raid 10 Problems?

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Message-ID: <742277.25048.qm@web52514.mail.yahoo.com>
Date:	Sun, 4 Mar 2007 08:25:09 -0800 (PST)
From:	Marc Perkel <mperkel@...oo.com>
To:	linux-kernel@...r.kernel.org
Subject: Raid 10 Problems?

Running into a problem and not sure what I'm doing
wrong. Created a software raid 10 array. Everything
seems to be normal except that if you take the array
down and run e2fsck on it there are always errors,
mostly all little stuff and it recovers without losing
any data.

I'm running the latest OpenVZ kernel 2.6.18. I'm not
sure if this is a factor or not as the problem occurs
without starting any VEs.

The problem will happen most all the time. I can
format the partition, put the data on it then shut it
down and run 2efsck and there will be some errors to
fix.

In the past after running for weeks the raid array
will unexpectedly go inti read only mode due to the
errors. After running e2fsck it will run normal again.

I've never used raid 10 before (stripes on top of 2
mirrors) so I don't have anything to compare this
with. I'm just wondering if I'm doing something wrong.
I am using ACL and dir_index attributes.

If I run e2fsck twice in a row it comes up with no
errors he second time. However if I mount the /dev/md2
device and then immediately umount it and run e2fsck
again I get some errors. Here's a run I did just
mounting and unmounting immediately.

e2fsck 1.39 (29-May-2006)
Pass 1: Checking inodes, blocks, and sizes
Inode 17172774, i_blocks is 8304, should be 19272.
Fix? yes

Inode 37126149, i_blocks is 872, should be 2192. Fix?
yes

Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information
Block bitmap differences: +(39500534--39501904)
+(74267806--74267970)
Fix? yes

Free blocks count wrong for group #1205 (1371,
counted=0).
Fix? yes

Free blocks count wrong for group #2266 (17206,
counted=17041).
Fix? yes

Free blocks count wrong (218321825,
counted=218320289).
Fix? yes

/vz: ***** FILE SYSTEM WAS MODIFIED *****

125791 inodes used (0.11%)
451 non-contiguous inodes (0.4%)
# of inodes with ind/dind/tind blocks: 7086/648/0
15831007 blocks used (6.76%)
0 bad blocks
3 large files

107783 regular files
11529 directories
1584 character device files
10 block device files
3 fifos
1 link
4872 symbolic links (4864 fast symbolic links)
1 socket
--------
125783 files

____________________________________________________________________________________
Get your own web address.  
Have a HUGE year through Yahoo! Small Business.
http://smallbusiness.yahoo.com/domains/?p=BESTDEAL
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/