Accessing /dev/bcache/by-uuid/xxxx deletes the device

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

 



This is the weirdest bug.

gargamel:~# l /dev/bcache/by-uuid/
total 0
drwxr-xr-x 2 root root 60 Mar 24 20:53 ./
drwxr-xr-x 3 root root 60 Mar 24 20:53 ../
lrwxrwxrwx 1 root root 13 Mar 24 20:53 efa850e6-a82b-4b9b-9ae7-1ab9798a25ca -> ../../bcache1

gargamel:~#  cryptsetup luksOpen /dev/bcache/by-uuid/efa850e6-a82b-4b9b-9ae7-1ab9798a25ca dshelf1
Enter passphrase for /dev/bcache/by-uuid/efa850e6-a82b-4b9b-9ae7-1ab9798a25ca:
device-mapper: remove ioctl on temporary-cryptsetup-27100 failed: Device or resource busy
No key available with this passphrase.

gargamel:~# l /dev/bcache*
brw-rw---- 1 root disk 251, 0 Mar 24 21:00 /dev/bcache0
brw-rw---- 1 root disk 251, 1 Mar 24 21:01 /dev/bcache1

Now the /dev/bcache/by-uuid directory is gone (I had already lost the
uuid link for bcache0 ealier).
But the devices under /dev/bcache work fine.

Is that a udev bug of some kind?

I have udev 158-1, I guess I can upgrade but I thought I'd check first.

Thanks,
Marc
-- 
"A mouse is a device used to point at the xterm you want to type in" - A.S.R.
Microsoft is to operating systems ....
                                      .... what McDonalds is to gourmet cooking
Home page: http://marc.merlins.org/                         | PGP 1024R/763BE901
--
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



[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Linux ARM Kernel]     [Linux Filesystem Development]     [Linux ARM]     [Linux Omap]     [Fedora ARM]     [IETF Annouce]     [Security]     [Bugtraq]     [Linux OMAP]     [Linux MIPS]     [ECOS]     [Asterisk Internet PBX]     [Linux API]

  Powered by Linux