Re: Fix for fd0 and sr0 in /proc/partitions

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

 



Right, mdadm should skip those.  For me, I also want the option to not
add at least fd0 to /proc/partitions but that's nothing to do with
mdadm (I maintain a portable emergency boot disk that has to work on
countless unknown system configurations).  That is the way it was
before updating udev which now needs devtmpfs.   I already patched
mdadm to ignore the floppy and cdrom device types so at least it
doesn't hang on boot, only when things like fdisk -l are run.

On Tue, Oct 1, 2019 at 12:55 PM Andreas Klauer
<Andreas.Klauer@xxxxxxxxxxxxxx> wrote:
>
> On Tue, Oct 01, 2019 at 11:59:14AM -0700, David F. wrote:
> > mdadm shouldn't be scanning fd0 or sr0 by default
>
> First of all I apologize, it's my misunderstanding completely.
> For some reason I thought you wanted it removed from /proc/partitions...
>
> For mdadm, there are plenty of devices it should not touch.
> Such as device mapper, network block device, and md devices.
> Well, that applies for my system anyway.
>
> Hence my mdadm.conf restricts it to /dev/sd* /dev/loop*
> And loop devices are only included because I like to
> experiment with those.
>
> Since it can be configured I never had an issue with it,
> so not sure what the default should be.
>
> Regards
> Andreas Klauer



[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