Ariën Huisken wrote: > Hi list, > > I use sw raid in all TSL2.2 systems and monitor them with cat /proc/mdstat. > > Now I use raid 5 on several servers and when I do a mdadm -D /dev/md1 > it shows the array is dirty with one failed disk and /proc/mdstat shows > a clean array: > I asked this question back in April 2004: http://lists.trustix.org/pipermail/tsl-discuss/2004-April/010301.html
One of the answers (http://lists.trustix.org/pipermail/tsl-discuss/2004-April/010381.html) links to another list with this explanation (copy'n paste): <snip> Yes, that is normal. While an array is active, it is 'dirty', as there could be parity blocks that are not correct (new data has hit disc but new parity block hasn't yet, or vice-versa). Whenever you do mdadm -D /dev/mdX you will always get "dirty", unless you have set it to --readonly first. If you shut the array down with mdadm -S /dev/md0 then ook at individual devices with, e.g. mdadm -E /dev/hda1 you will see that the array is clean. </snip> Source: http://www.spinics.net/lists/raid/msg01648.html > It say's the state is dirty, but there's nothing wrong with the array. > > Is this a bug in mdadm or are my array's really bad? > It's just fine as you can read above. I installed an internal TSL 2.2 based FTP server with 4 80GB disks in RAID-5 back in 2004-04-13 and the only problem I had, which I did not see for a long time was that one of the disks crashed. The system ran just fine, a bit slower and in degraded mode, but I was still able to access my files. I replaced the disk and after the startup my system did an automatic rebuild of the array (RAID-5). about 5 hours later it was up and running 100% again. My mdadm -D : [EMAIL PROTECTED] ~# mdadm -D /dev/md0 /dev/md0: Version : 00.90.00 Creation Time : Tue Apr 13 13:06:10 2004 Raid Level : raid5 Array Size : 233649024 (222.83 GiB 239.26 GB) Device Size : 77883008 (74.28 GiB 79.75 GB) Raid Devices : 4 Total Devices : 4 Preferred Minor : 0 Persistence : Superblock is persistent Update Time : Mon Mar 27 13:02:44 2006 State : dirty Active Devices : 4 Working Devices : 4 Failed Devices : 0 Spare Devices : 0 Layout : left-symmetric Chunk Size : 64K UUID : 4ea7bbd8:8ee269e6:e8e32f75:b10e18d6 Events : 0.87 Number Major Minor RaidDevice State 0 3 2 0 active sync /dev/hda2 1 3 66 1 active sync /dev/hdb2 2 22 2 2 active sync /dev/hdc2 3 22 66 3 active sync /dev/hdd2 > -- > Ariën Huisken Christopher Thorjussen _______________________________________________ tsl-discuss mailing list [email protected] http://lists.trustix.org/mailman/listinfo/tsl-discuss
