Re: why the kernel and mdadm report differently

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

 



On Monday September 5, lfarkas@xxxxxxxxx wrote:
> hi,
> one of our raid array is crash all the time (once a week), 

Any kernel error messages?

> and one more 
> stange thing that it's currently not working, kernel report inactive 
> while mdadm said it's active, degraded. what's more we cant put this 
> array into active state.

Looks like you need to stop in (mdadm -S /dev/md2) and re-assemble it
with --force:
  mdadm -A /dev/md2 -f /dev/sd[abcefgh]1

It looks like the computer crashed and when it came back up it was
missing a drive.  This situation can result in silent data corruption,
which is why md won't automatically assemble it.  When you do assemble
it, you should at least fsck the filesystem, and possibly check for
data corruption if that is possible.  At least be aware that some data
could be corrupt (there is a good chance that nothing is, but it is by
no means certain).


> this is mdadm 1.12, just another site note there is no rpm for version 
> 2.0:-(

No.  I seem to remember some odd compile issue with making the RPM
and thinking "I don't care".   Maybe I should care a bit more....

NeilBronw
-
To unsubscribe from this list: send the line "unsubscribe linux-raid" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
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