On 7 October 2014 21:52:05 GMT+01:00, jd1008 <jd1008@xxxxxxxxx> wrote: ># mount | grep sdc3 >/dev/mapper/HGST_HTS721010A9E630_JR10006P0BSEEF3 on /sdc3 type ext4 >(rw,relatime,journal_checksum) > >So, how come I do not see it listed as I see /dev/sda3. To wit: ># mount | grep sda3 >/dev/sda3 on / type ext4 (rw,relatime,data=ordered) > >If I unmount /dev/mapper/HGST_HTS721010A9E630_JR10006P0BSEEF3 > ># umount /dev/mapper/HGST_HTS721010A9E630_JR10006P0BSEEF3 > >and I try ># mount /dev/sdc3 /sdc3 >mount: special device /dev/sdc3 does not exist > ># grep sdc3 /etc/fstab > >UUID=e64d7b94-1ffb-4a2e-ae59-5f8e54b6cab9 /sdc3 ext4 >noauto,data=ordered,journal_checksum 3 3 > ># blkid /dev/sdc3 >/dev/sdc3: UUID="e64d7b94-1ffb-4a2e-ae59-5f8e54b6cab9" TYPE="ext2" >PARTUUID="96e20bf8-03" > > >dmesg shows these errors: > >[ 25.083098] systemd-udevd[385]: inotify_add_watch(7, /dev/sdc3, 10) >failed: No such file or directory >[ 25.084057] systemd-udevd[386]: inotify_add_watch(7, /dev/sdc4, 10) >failed: No such file or directory >[ 25.085042] systemd-udevd[384]: inotify_add_watch(7, /dev/sdc2, 10) >failed: No such file or directory >[ 25.087052] systemd-udevd[381]: inotify_add_watch(7, /dev/sdc1, 10) >failed: No such file or directory > > >Runing partprobe: > ># partprobe >device-mapper: remove ioctl on HGST_HTS721010A9E630_JR10006P0BSEEF4 >failed: Device or resource busy >device-mapper: remove ioctl on HGST_HTS721010A9E630_JR10006P0BSEEF3 >failed: Device or resource busy >device-mapper: remove ioctl on HGST_HTS721010A9E630_JR10006P0BSEEF2 >failed: Device or resource busy >device-mapper: remove ioctl on HGST_HTS721010A9E630_JR10006P0BSEEF1 >failed: Device or resource busy >Warning: parted was unable to re-read the partition table on >/dev/mapper/HGST_HTS721010A9E630_JR10006P0BSEEF (Device or resource >busy). This means Linux won't know anything about the modifications >you >made. >device-mapper: create ioctl on HGST_HTS721010A9E630_JR10006P0BSEEF1 >failed: Device or resource busy >device-mapper: remove ioctl on HGST_HTS721010A9E630_JR10006P0BSEEF1 >failed: Device or resource busy >device-mapper: create ioctl on HGST_HTS721010A9E630_JR10006P0BSEEF2 >failed: Device or resource busy >device-mapper: remove ioctl on HGST_HTS721010A9E630_JR10006P0BSEEF2 >failed: Device or resource busy >device-mapper: create ioctl on HGST_HTS721010A9E630_JR10006P0BSEEF3 >failed: Device or resource busy >device-mapper:remove ioctl on HGST_HTS721010A9E630_JR10006P0BSEEF3 >failed: Device or resource busy >device-mapper: create ioctl on HGST_HTS721010A9E630_JR10006P0BSEEF4 >failed: Device or resource busy >device-mapper: remove ioctl on HGST_HTS721010A9E630_JR10006P0BSEEF4 >failed: Device or resource busy >device-mapper: remove ioctl on WDC_WD20NPVX-00EA4T0_WD-WXV1E53KAE83p3 >failed: Device or resource busy >Warning: parted was unable to re-read the partition table on >/dev/mapper/WDC_WD20NPVX-00EA4T0_WD-WXV1E53KAE83 (Device or resource >busy). This means Linux won't know anything about the modifications >you >made. >device-mapper: create ioctl on WDC_WD20NPVX-00EA4T0_WD-WXV1E53KAE83p3 >failed: Device or resource busy >device-mapper: remove ioctl on WDC_WD20NPVX-00EA4T0_WD-WXV1E53KAE83p3 >failed: Device or resource busy > >So, whatmight be causing this? > >-- >users mailing list >users@xxxxxxxxxxxxxxxxxxxxxxx >To unsubscribe or change subscription options: >https://admin.fedoraproject.org/mailman/listinfo/users >Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct >Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines >Have a question? Ask away: http://ask.fedoraproject.org What's the output of lsblk? It looks a bit like your using LVM -- Junk -- users mailing list users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
