I'm noticing that, with Fedora, dracut is trying to stop the mdraid
devices before bcache stops.
[ 1378.484141] dracut: Waiting for mdraid devices to be clean.
[ 1378.494073] dracut: Disassembling mdraid devices.
mdadm: Cannot get exclusive access to /dev/md1:Perhaps a running
process, mounted filesystem or active volume group?
mdadm: Cannot get exclusive access to /dev/md0:Perhaps a running
process, mounted filesystem or active volume group?
mdadm: Cannot get exclusive access to /dev/md1:Perhaps a running
process, mounted filesystem or active volume group?
mdadm: Cannot get exclusive access to /dev/md0:Perhaps a running
process, mounted filesystem or active volume group?
Powering off.
[ 1379.582761] bcache: bcache_reboot() Stopping all devices:
[ 1379.728768] bcache: bcache_device_free() bcache0 stopped
[ 1379.781601] bcache: cache_set_free() Cache set
4772d958-3d94-4411-b26c-86206cfa551e unregistered
[ 1379.792585] bcache: bcache_reboot() All devices stopped
I haven't seen any data loss or corruption so this doesn't seem to be a
problem but it would be nice to have bcache stop first so I don't get so
alarmed by these messages.
How is the shutdown sequence for bcache controlled? Where can I find the
relevant code?
--Larkin
--
To unsubscribe from this list: send the line "unsubscribe linux-bcache" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
