Re: mdadm --detail works, mdadm --stop says "does not appear to be an md device"

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

 



On Mon, Mar 20, 2023 at 03:36:39PM +0100, Mariusz Tkaczyk wrote:
> Hi,
> mdadm is unable to complete this task because it cannot ensure that it is safe
> to stop the array. It cannot open the array with O_EXCL.
> If it is mounted then it may hang if filesystem needs to flush some data.
 
Thanks for the reply. The array was not mounted, that said, given that
it was fully down, there wasn't a way to flush the data if it had been
(cable problem to an enclosure, all the drives disappeared at once)

> Please, try umount the array if it mounted somewhere and then try:
> 
> # echo inactive > /sys/block/md6/md/array_state
> # echo clear > /sys/block/md6/md/array_state

I can try this next time (already had to reboot), thanks.

That said, mdadm should output a better message in this case
> > mdadm: /dev/md6 does not appear to be an md device
is clearly wrong 

Is that something easy to fix/improve?

Thanks,
Marc
-- 
"A mouse is a device used to point at the xterm you want to type in" - A.S.R.
 
Home page: http://marc.merlins.org/  



[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