- To: linux-raid <linux-raid@xxxxxxxxxxxxxxx>
- Subject: On mdadm 3.2 and bad-block-log
- From: Asdo <asdo@xxxxxxxxxxxxx>
- Date: Tue, 12 Jun 2012 18:51:25 +0200
- User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:10.0.2) Gecko/20120216 Thunderbird/10.0.2
Hello
is it possible to keep mdadm 3.2 installed in the system (e.g. 3.2 as
the monitoring daemon) and have an array with bad-block functionality
(created with 3.3) running, or this will do a mess?
Bad-block functionality is in mdadm-3.3 but this has not been released
yet. I was thinking about using it only once to create the array.
However I am still missing the manual for mdadm-3.3, where is that?
without that I don't know how I should launch it to create an array with
bad blocks.
Another question: are older kernels such as 3.0 capable to run an array
created with bad-block-log, obviously without using the bad-block-log
functionality? oh but that could be dangerous, couldn't it...
Thank you
A.
--
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
[ATA RAID]
[Linux SCSI Target Infrastructure]
[Managing RAID on Linux]
[Linux IDE]
[Linux SCSI]
[Linux Hams]
[Device-Mapper]
[Kernel]
[Linux Books]
[Linux Admin]
[Linux Net]
[GFS]
[RPM]
[git]
[Photos]
[Yosemite Photos]
[Yosemite News]
[AMD 64]
[Linux Networking]