Re: Mdadm dirty, no errors?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Friday August 23, stclists@wearesimply.com wrote:
...
>           State : dirty, no-errors
...
> 
> Again,  why is State:  dirty, no-errors??  Is this normal?
> 

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.

NeilBrown

-
To unsubscribe from this list: send the line "unsubscribe linux-raid" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

[Index of Archives]     [Linux RAID Wiki]     [ATA RAID]     [Linux SCSI Target Infrastructure]     [Linux Block]     [Linux IDE]     [Linux SCSI]     [Linux Hams]     [Device Mapper]     [Device Mapper Cryptographics]     [Kernel]     [Linux Admin]     [Linux Net]     [GFS]     [RPM]     [git]     [Yosemite Forum]


  Powered by Linux