Re: RAID5 kicks non-fresh drives

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

 



On Fri, 2006-05-26 at 12:45 -0400, Mark Hahn wrote:
> I think the current situation is good, since there is some danger of 
> going too far.  for instance, testing each partition to see whether 
> it contains a valid superblock would be pretty crazy, right?  requiring
> either the "auto-assemble-me" partition type, or explicit partitions 
> given in a config file is a happy medium...
> 

I created my array in 1/2003, don't know versions of kernel or mdadm I
was using then.

In my situation over the past few days.
  kernel 2.4.30 kicked non-fresh
  kernel 2.6.11.8 kicked non-fresh
  kernel 2.6.18.8 didn't mention anything, just skipped my 'linux'
partitions

These kernels auto-assemble prior to mounting /. So the kernel doesn't
consult my 
/etc/mdadm/mdadm.conf file. Is this correct? 



> 
-- 
------------------------------------------------------------
Dr. Craig Hollabaugh, craig@xxxxxxxxxxxxxx, 970 240 0509
Author of Embedded Linux: Hardware, Software and Interfacing
www.embeddedlinuxinterfacing.com

-
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