Re: RAID5 problem

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

 



On Sunday December 4, aab@xxxxxxxxxxx wrote:
> 
> PS to Neil. I thought I might submit a patch to you that added a little 
> more info the the above lines, the slot number and the raid device
> 
> So it would read:
> 
> mdadm: /dev/hdc3 appears to be part of a raid array:
>      /dev/md0 slot[1] level=5 devices=4 ctime=Fri May 30 14:25:47 2003
> 
> I find this to be information that I have to search for using 'mdadm -E' so it
> would be handy to see it all at once when having to force a broken array to
> assemble.
> 
> Also it would be handy to see the update time rather than the creation time
> (IMHO) so I can see how far apart the devices are (or maybe the event count
> would be better for this) and whether or not the device was marked 'clean'.
> 
> What do you think?

Sounds reasonable - just send that patch.

NeilBrown
-
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