mdadm --misc --readonly -> ENODEV indefinitely

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

 



So I was trying to flip on the RAID journal now I'd fully populated my
array and cut over to it. So, from early userspace, I did

   # first line done by initramfs scripting
   /sbin/mdadm --assemble --scan --auto=md --freeze-reshape
   mdadm --misc --readonly /dev/md/fast
   mdadm --manage /dev/md/fast --add-journal /dev/ssd1
   mdadm --misc --readwrite /dev/md/fast

This did not work as planned, or indeed at all. After the first
--readonly, all requests for /dev/md/fast report "No such device or
address" until a reboot, though /proc/mdstat says the thing is still
there and /sys/block/md125/dev reports no change in major/minor numbers.
(I don't have udev in my early-userspace environment, but mdev reports
no change, either.)

It's a bit hard to do anything else after that, like, say, turn the
journal on.

... maybe an mdadm --assemble --scan --auto=md --readonly in one go
would work better, rather than starting with the default (?read-mostly?)
and flipping it? I'll give that a try later.
--
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