[opensuse] unounting external HD is not permitted
Hello: This occurs in openSUSE 13.1 with KDE3 as default desktop. I have a Samsung external USB hard drive. When I plug it in it becomes mounted: df -h /dev/sdd1 932G 270G 662G 29% /media/SAMSUNG ls -l /dev/sdd1 brw-rw---- 1 root disk 8, 49 Mar 9 23:12 /dev/sdd1 The desktop user is member of group disk. When I try to unmount the device I get:
umount /dev/sdd1 umount: /media/SAMSUNG: umount failed: Operation not permitted
Why is this and how can I fix it? It is interesting that plugged USB flash disk also becomes mounted but I can unmount it: df -h /dev/sdd1 7.4G 6.7G 671M 92% /media/KINGSTON umount /dev/sdd1 ~> Thanks, Istvan -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 03/09/2016 02:25 PM, Istvan Gabor wrote:
Hello:
This occurs in openSUSE 13.1 with KDE3 as default desktop. I have a Samsung external USB hard drive. When I plug it in it becomes mounted:
df -h /dev/sdd1 932G 270G 662G 29% /media/SAMSUNG
ls -l /dev/sdd1 brw-rw---- 1 root disk 8, 49 Mar 9 23:12 /dev/sdd1
The desktop user is member of group disk.
When I try to unmount the device I get:
umount /dev/sdd1 umount: /media/SAMSUNG: umount failed: Operation not permitted
Why is this and how can I fix it?
It is interesting that plugged USB flash disk also becomes mounted but I can unmount it:
df -h /dev/sdd1 7.4G 6.7G 671M 92% /media/KINGSTON
umount /dev/sdd1 ~>
Thanks,
Istvan
Are you SURE that nothing is using it at that moment? Even leaving a Dolphin file manager instance looking at the drive will prevent dismount, but also any shell script starting from that drive will be an issue. Who mounted it? You or root, or kde's auto mount service? If kde mounted it either root or kde has to unmount it, because kde hands that task off to root. Check permissions /dev/sdd1 sudo umount /dev/sdd1 My ability to make and specific recommendations is hindered by not having had kde3 running on any machine for something like 5 years now. -- After all is said and done, more is said than done. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Istvan Gabor composed on 2016-03-09 23:25 (UTC+0100):
This occurs in openSUSE 13.1 with KDE3 as default desktop. I have a Samsung external USB hard drive. When I plug it in it becomes mounted:
df -h /dev/sdd1 932G 270G 662G 29% /media/SAMSUNG
ls -l /dev/sdd1 brw-rw---- 1 root disk 8, 49 Mar 9 23:12 /dev/sdd1
The desktop user is member of group disk.
When I try to unmount the device I get:
umount /dev/sdd1 umount: /media/SAMSUNG: umount failed: Operation not permitted
Why is this and how can I fix it?
It is interesting that plugged USB flash disk also becomes mounted but I can unmount it:
df -h /dev/sdd1 7.4G 6.7G 671M 92% /media/KINGSTON
umount /dev/sdd1 ~>
IIRC: I think if you peruse the opensuse-kde3 mailing list archives that you'll find Ilya's explanation of a problem someone else would have to provide the best fix for. Setting up http://download.opensuse.org/repositories/KDE:/KDE3:/HAL-enabled/openSUSE_13... as a repo changes things somehow that I cannot remember. I don't think I ever enabled it when I was using 13.1. Now I'm on 42.1, still umounting USB sticks as root. I'm pretty sure sure that this was long ago solved in TDE by removing the need for HAL. -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Istvan Gabor wrote:
Hello:
This occurs in openSUSE 13.1 with KDE3 as default desktop. I have a Samsung external USB hard drive. When I plug it in it becomes mounted:
df -h /dev/sdd1 932G 270G 662G 29% /media/SAMSUNG
ls -l /dev/sdd1 brw-rw---- 1 root disk 8, 49 Mar 9 23:12 /dev/sdd1
The desktop user is member of group disk. === That only lets the user write directly to the device, doesn't control mount privs.
Your /etc/fstab needs to have an entry for the mount with "user" in the options to allow users to mount/umount it. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 03/10/2016 02:42 AM, Linda Walsh wrote:
Istvan Gabor wrote:
Hello:
This occurs in openSUSE 13.1 with KDE3 as default desktop. I have a Samsung external USB hard drive. When I plug it in it becomes mounted:
df -h /dev/sdd1 932G 270G 662G 29% /media/SAMSUNG
ls -l /dev/sdd1 brw-rw---- 1 root disk 8, 49 Mar 9 23:12 /dev/sdd1
The desktop user is member of group disk. === That only lets the user write directly to the device, doesn't control mount privs.
Your /etc/fstab needs to have an entry for the mount with "user" in the options to allow users to mount/umount it.
NOT! There's something wrong with a setup here but I can't say what; maybe there's been some specific DM setting for the device with that name. When i insert a USB stick in the front of my computer and am logged in under KDE4 I get a popup from the "Device notifier" in my bottom panel's System Tray offering option to do with mounting/opening the USB. it get mounted under /run, the tmpfs. Here are the entries from mnttab: /dev/sdb1 on /run/media/anton/c73c2779-c12a-48ef-ae0d-7b2017d848dc type btrfs (rw,nosuid,nodev,relatime,space_cache,subvolid=5,subvol=/,uhelper=udisks2) /dev/sdb1 on /var/run/media/anton/c73c2779-c12a-48ef-ae0d-7b2017d848dc type btrfs (rw,nosuid,nodev,relatime,space_cache,subvolid=5,subvol=/) The stick in question is one that I put a bootable system on. hence the BtrFS. That's beside the point. This is dynamically generated by rules for udisk. (Aks "more systemd nonsense") There is NO NEED FOR AN ENTRY IN /etc/fstab !! Of course those rules determine not only the 'where' but also the permissions :-) The action of the Device Notfier can, under KDE4, by overridden. There's a option under Device Notifier Settings -> Removable Devices to alter all this behaviour, as well as to have specific actions based on the "name" of the USB device attached, action if a device previously mounted is seen again and more. But all this is dealt with completely without the need for an entry in /etc/fstab. The difference here is that Istvan is running KDE3 under 13.1 and I'm running KDE4 under 13.1. -- A: Yes. > Q: Are you sure? >> A: Because it reverses the logical flow of conversation. >>> Q: Why is top posting frowned upon? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Anton Aylward írta:
On 03/10/2016 02:42 AM, Linda Walsh wrote:
Istvan Gabor wrote:
Hello:
This occurs in openSUSE 13.1 with KDE3 as default desktop. I have a Samsung external USB hard drive. When I plug it in it becomes mounted:
df -h /dev/sdd1 932G 270G 662G 29% /media/SAMSUNG
ls -l /dev/sdd1 brw-rw---- 1 root disk 8, 49 Mar 9 23:12 /dev/sdd1
The desktop user is member of group disk. === That only lets the user write directly to the device, doesn't control mount privs.
Your /etc/fstab needs to have an entry for the mount with "user" in the options to allow users to mount/umount it.
NOT!
There's something wrong with a setup here but I can't say what; maybe there's been some specific DM setting for the device with that name.
When i insert a USB stick in the front of my computer and am logged in under KDE4 I get a popup from the "Device notifier" in my bottom panel's System Tray offering option to do with mounting/opening the USB. it get mounted under /run, the tmpfs. Here are the entries from mnttab:
/dev/sdb1 on /run/media/anton/c73c2779-c12a-48ef-ae0d-7b2017d848dc type btrfs (rw,nosuid,nodev,relatime,space_cache,subvolid=5,subvol=/,uhelper=udisks2) /dev/sdb1 on /var/run/media/anton/c73c2779-c12a-48ef-ae0d-7b2017d848dc type btrfs (rw,nosuid,nodev,relatime,space_cache,subvolid=5,subvol=/)
The stick in question is one that I put a bootable system on. hence the BtrFS. That's beside the point.
This is dynamically generated by rules for udisk. (Aks "more systemd nonsense") There is NO NEED FOR AN ENTRY IN /etc/fstab !!
Of course those rules determine not only the 'where' but also the permissions :-)
The action of the Device Notfier can, under KDE4, by overridden. There's a option under Device Notifier Settings -> Removable Devices to alter all this behaviour, as well as to have specific actions based on the "name" of the USB device attached, action if a device previously mounted is seen again and more.
But all this is dealt with completely without the need for an entry in /etc/fstab.
The difference here is that Istvan is running KDE3 under 13.1 and I'm running KDE4 under 13.1.
Thank you all. I checked the permissions of the mounted directories and they are as follows: For the flash disk:
ls -l /media/ total 16 drwx------ 46 user users 16384 Jan 1 1970 KINGSTON
For the external HD: ls -l /media/ total 8 drwx------ 1 user users 8192 Jan 11 01:57 SAMSUNG There is no difference in owner and permissions. But there are differences in the dates probably because of the file systems are different. Can the different file systems cause the problem? The file system reported by df -T are: /dev/sdd1 vfat 7673968 6987632 686336 92% /media/KINGSTON /dev/sdd1 fuseblk 976760000 282945316 693814684 29% /media/SAMSUNG The devices are mounted by KDE media mounter/manager (KDE daemon is the title of the popup window shown after plugging in the device). Immediately after mounting I try unmount the devices but if fails in case of the external hard drive (SAMSUNG). What I don't understand why I can unmount the flash disk and can not unmount the HD. Felix, the kdebase I have is not the hal-enabled version. This problem I have now is different from that safely remove is not working. My problem applies to unmounting the device in a terminal using umount command. Istvan -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2016-03-11 21:50, Istvan Gabor wrote:
There is no difference in owner and permissions. But there are differences in the dates probably because of the file systems are different. Can the different file systems cause the problem? The file system reported by df -T are:
/dev/sdd1 vfat 7673968 6987632 686336 92% /media/KINGSTON /dev/sdd1 fuseblk 976760000 282945316 693814684 29% /media/SAMSUNG
fuse might mean that it is an NTFS device. Ah. I remember now. That's why you can not umount it. You need fuse tools suid, and maybe not even then. -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" at Telcontar)
Istvan Gabor wrote:
/dev/sdd1 vfat 7673968 6987632 686336 92% /media/KINGSTON /dev/sdd1 fuseblk 976760000 282945316 693814684 29% /media/SAMSUNG
Does your fstab have an entry for either of those? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Linda Walsh írta:
Istvan Gabor wrote:
/dev/sdd1 vfat 7673968 6987632 686336 92% /media/KINGSTON /dev/sdd1 fuseblk 976760000 282945316 693814684 29% /media/SAMSUNG
Does your fstab have an entry for either of those?
Linda, have you read my previous posts at all? I don't understand what my problem has got to do with fstab entries. Answering your question, I don't have fstab entry for any of the above devices. Still, after plugging in, both devices become mounted automatically in /media/<device-name> (by KDE3 mount manager, I guess), despite of the lacking fstab entries. But while I can manually unmount KINGSTON flash disk, I can not manually unmount SAMSUNG extarnal HD. How do you explain this? Thanks, Istvan -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Le 12/03/2016 12:26, Istvan Gabor a écrit :
in /media/<device-name> (by KDE3 mount manager, I guess)
no idea how kde3 manage this , despite of
the lacking fstab entries. But while I can manually unmount KINGSTON flash disk, I can not manually unmount SAMSUNG extarnal HD. How do you explain this?
as root or user? I have to say I tend to ignore kde3 threads :-( normally this mean the disk is not free, lsof should give clue. I use kde4, and some disks are mounted as user (automatically), some others are not and I have to mount them manually, and I don't know why :-( as I'm the only user I log as root and mount them or use udisksctl... sorry jdd -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 03/12/2016 06:34 AM, jdd wrote:
Le 12/03/2016 12:26, Istvan Gabor a écrit :
in /media/<device-name> (by KDE3 mount manager, I guess)
no idea how kde3 manage this
Its the kernel and udevd that do it, so it works with all the DMs -- A: Yes. > Q: Are you sure? >> A: Because it reverses the logical flow of conversation. >>> Q: Why is top posting frowned upon? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
12.03.2016 14:26, Istvan Gabor пишет:
Linda Walsh írta:
Istvan Gabor wrote:
/dev/sdd1 vfat 7673968 6987632 686336 92% /media/KINGSTON /dev/sdd1 fuseblk 976760000 282945316 693814684 29% /media/SAMSUNG
How comes you have apparently the same device for two different mount points?
--- Does your fstab have an entry for either of those?
Linda, have you read my previous posts at all? I don't understand what my problem has got to do with fstab entries. Answering your question, I don't have fstab entry for any of the above devices.
I would expect different error then - something like bor@bor-Latitude-E5450:~/src/grub$ LANG=C umount /dev/sda1 umount: /dev/sda1 is not in the fstab (and you are not root) Actually, that you cannot unmount is normal and expected - the real question is, why you *can* unmount. Please show strace -f -o /tmp/some-file umount ...etc... for both filesystems.
Still, after plugging in, both devices become mounted automatically in /media/<device-name> (by KDE3 mount manager, I guess), despite of the lacking fstab entries. But while I can manually unmount KINGSTON flash disk, I can not manually unmount SAMSUNG extarnal HD. How do you explain this?
Thanks,
Istvan
-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Andrei Borzenkov írta:
12.03.2016 14:26, Istvan Gabor пишет:
Linda Walsh írta:
Istvan Gabor wrote:
/dev/sdd1 vfat 7673968 6987632 686336 92% /media/KINGSTON /dev/sdd1 fuseblk 976760000 282945316 693814684 29% /media/SAMSUNG
How comes you have apparently the same device for two different mount points?
--- Does your fstab have an entry for either of those?
Linda, have you read my previous posts at all? I don't understand what my problem has got to do with fstab entries. Answering your question, I don't have fstab entry for any of the above devices.
I would expect different error then - something like
bor@bor-Latitude-E5450:~/src/grub$ LANG=C umount /dev/sda1 umount: /dev/sda1 is not in the fstab (and you are not root)
Actually, that you cannot unmount is normal and expected - the real question is, why you *can* unmount.
Please show
strace -f -o /tmp/some-file umount ...etc...
Thanks Andrei. The resulted files are quite big to insert them here, I sent them to your address as attachments. Thanks, Istvan -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
15.03.2016 18:50, Istvan Gabor пишет:
Andrei Borzenkov írta:
12.03.2016 14:26, Istvan Gabor пишет:
Linda Walsh írta:
Istvan Gabor wrote:
/dev/sdd1 vfat 7673968 6987632 686336 92% /media/KINGSTON /dev/sdd1 fuseblk 976760000 282945316 693814684 29% /media/SAMSUNG
How comes you have apparently the same device for two different mount points?
--- Does your fstab have an entry for either of those?
Linda, have you read my previous posts at all? I don't understand what my problem has got to do with fstab entries. Answering your question, I don't have fstab entry for any of the above devices.
I would expect different error then - something like
bor@bor-Latitude-E5450:~/src/grub$ LANG=C umount /dev/sda1 umount: /dev/sda1 is not in the fstab (and you are not root)
Actually, that you cannot unmount is normal and expected - the real question is, why you *can* unmount.
Please show
strace -f -o /tmp/some-file umount ...etc...
Thanks Andrei.
The resulted files are quite big to insert them here, I sent them to your address as attachments.
One is using umount.udisks and another tries to unmount directly. Could you show "udiskctl dump" with either of them connected? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2016-03-15 19:45, Andrei Borzenkov wrote:
15.03.2016 18:50, Istvan Gabor пишет:
One is using umount.udisks and another tries to unmount directly. Could you show "udiskctl dump" with either of them connected?
Remember that you can not (u)mount ntfs partitions as user unless ntfs-3g is suid. And in openSUSE it is not, by default. The man page says so, and I verified that I can not umount them from the command line. Same situation as the OP. -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" at Telcontar)
On 2016-03-12 12:26, Istvan Gabor wrote:
Still, after plugging in, both devices become mounted automatically in /media/<device-name> (by KDE3 mount manager, I guess), despite of the lacking fstab entries. But while I can manually unmount KINGSTON flash disk, I can not manually unmount SAMSUNG extarnal HD. How do you explain this?
I answered that already, didn't you read it? :-? Proof: cer@Telcontar:~> mount ... /dev/sdg1 on /media/EMTEC_16G type fuseblk (rw,nosuid,nodev,relatime,user_id=0,group_id=0,default_permissions,allow_other,blksize=4096) cer@Telcontar:~> umount /dev/sdg1 umount: /media/EMTEC_16G: umount failed: Operation not permitted cer@Telcontar:~> cer@Telcontar:~> umount /media/EMTEC_16G umount: /media/EMTEC_16G: umount failed: Operation not permitted cer@Telcontar:~> fuseblk --> ntfs disk. You can not umount it on the command line by user. However, it can be done on the desktop. At least, XFCE on 13.1 does. -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" at Telcontar)
Anton Aylward wrote:
On 03/10/2016 02:42 AM, Linda Walsh wrote:
Istvan Gabor wrote:
Hello:
This occurs in openSUSE 13.1 with KDE3 as default desktop. I have a Samsung external USB hard drive. When I plug it in it becomes mounted:
df -h /dev/sdd1 932G 270G 662G 29% /media/SAMSUNG
ls -l /dev/sdd1 brw-rw---- 1 root disk 8, 49 Mar 9 23:12 /dev/sdd1
The desktop user is member of group disk. === That only lets the user write directly to the device, doesn't control mount privs.
Your /etc/fstab needs to have an entry for the mount with "user" in the options to allow users to mount/umount it.
NOT!
Ah, the inscrutable Anton. NOT _WHAT_? My man page for mount has: FILESYSTEM-INDEPENDENT MOUNT OPTIONS ... user Allow an ordinary user to mount the filesystem. The name of the mounting user is written to mtab (or to the private libmount file in /run/mount on system without regular mtab) so that he can unmount the filesystem again. This option implies the options noexec, nosuid, and nodev (unless overridden by subse- quent options, as in the option line user,exec,dev,suid). nouser Forbid an ordinary (i.e., non-root) user to mount the filesys- tem. This is the default; it does not imply any other options. users Allow every user to mount and unmount the filesystem. This option implies the options noexec, nosuid, and nodev (unless overridden by subsequent options, as in the option line users,exec,dev,suid). ----- The default for mounts is "nouser" which forbids an ordinary non-root user to mount a file system. Using 'user' or 'users' allow [a] normal user[s] to mount & unmount a file system. What does your mount manpage say?
There is NO NEED FOR AN ENTRY IN /etc/fstab !!
Oh? I didn't see him give any of the 'user' options on his mount option besides which they wouldn't work unless he was root.
The difference here is that Istvan is running KDE3 under 13.1 and I'm running KDE4 under 13.1.
And I am on 13.2. You are saying there was a special FS under 13.1 that didn't exist before or after? If that's the case, you are being exceptionally rude to someone who was quoting the system manpages... though, I grant that it might not be exceptional for you. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 03/11/2016 10:34 PM, Linda Walsh wrote:
There is NO NEED FOR AN ENTRY IN /etc/fstab !!
Oh? I didn't see him give any of the 'user' options on his mount option besides which they wouldn't work unless he was root.
I stand by my statement that there is no need for an entry in /etc/fstab for pluggable devices such as USB sticks. The kernel sees the 'event' of the USB stick being inserted and triggers udev for the appropriate rules. The stick gets mounted under /run/media I forget when this was introduced to the kernel, but it pre-dates the kernel distributed with 13.1 and I doubt very much it has been removed as it still works with my 4.4 kernels. You can demonstrate this quite easily by doing a 'tail -f /var/log/messages' while inserting and removing a USB stick **WITHOUT THERE BEING AN ENTRY FOR USB IN THE /etc/fstab**. Not all systems seem to have the necessary udev rules, it seems the Pi lacks them: http://www.axllent.org/docs/view/auto-mounting-usb-storage/ For example, I get 2016-03-12T12:13:40.856891-05:00 Mainbox kernel: [174321.320028] usb 1-4: new high-speed USB device number 6 using ehci-pci 2016-03-12T12:13:40.988721-05:00 Mainbox mtp-probe: checking bus 1, device 6: "/sys/devices/pci0000:00/0000:00:1a.7/usb1/1-4" 2016-03-12T12:13:40.988935-05:00 Mainbox kernel: [174321.452880] usb 1-4: New USB device found, idVendor=abcd, idProduct=1234 2016-03-12T12:13:40.988942-05:00 Mainbox kernel: [174321.452887] usb 1-4: New USB device strings: Mfr=1, Product=2, SerialNumber=3 2016-03-12T12:13:40.988944-05:00 Mainbox kernel: [174321.452891] usb 1-4: Product: 2016-03-12T12:13:40.988945-05:00 Mainbox kernel: [174321.452894] usb 1-4: Manufacturer: General 2016-03-12T12:13:40.988946-05:00 Mainbox kernel: [174321.452898] usb 1-4: SerialNumber: Љ 2016-03-12T12:13:40.988948-05:00 Mainbox kernel: [174321.453311] usb-storage 1-4:1.0: USB Mass Storage device detected 2016-03-12T12:13:40.988949-05:00 Mainbox kernel: [174321.453453] scsi host10: usb-storage 1-4:1.0 2016-03-12T12:13:41.005765-05:00 Mainbox mtp-probe: bus: 1, device: 6 was not an MTP device 2016-03-12T12:13:41.988901-05:00 Mainbox kernel: [174322.452798] scsi 10:0:0:0: Direct-Access General 5.00 PQ: 0 ANSI: 2 2016-03-12T12:13:41.988922-05:00 Mainbox kernel: [174322.453097] sd 10:0:0:0: Attached scsi generic sg3 type 0 2016-03-12T12:13:41.988924-05:00 Mainbox kernel: [174322.453652] sd 10:0:0:0: [sdb] 7987200 512-byte logical blocks: (4.09 GB/3.81 GiB) 2016-03-12T12:13:41.988926-05:00 Mainbox kernel: [174322.454371] sd 10:0:0:0: [sdb] Write Protect is off 2016-03-12T12:13:41.988927-05:00 Mainbox kernel: [174322.454378] sd 10:0:0:0: [sdb] Mode Sense: 0b 00 00 08 2016-03-12T12:13:41.988928-05:00 Mainbox kernel: [174322.455024] sd 10:0:0:0: [sdb] No Caching mode page found 2016-03-12T12:13:41.988929-05:00 Mainbox kernel: [174322.455027] sd 10:0:0:0: [sdb] Assuming drive cache: write through 2016-03-12T12:13:41.996981-05:00 Mainbox kernel: [174322.461779] sdb: sdb1 2016-03-12T12:13:42.000951-05:00 Mainbox kernel: [174322.465020] sd 10:0:0:0: [sdb] Attached SCSI removable disk 2016-03-12T12:13:42.281331-05:00 Mainbox kernel: [174322.747787] FAT-fs (sdb1): Volume was not properly unmounted. Some data may be corrupt. Please run fsck. 2016-03-12T12:13:42.291391-05:00 Mainbox udisksd[24555]: Mounted /dev/sdb1 at /run/media/anton/88D8-01F5 on behalf of uid 501 which is followed by my KDE Device Notifier producing a popup from my bottom panel, as I described in my earlier email, asking me what I want to do with this new device. Similarly I can simply pull that disk, but the 'unmounting' may not necessarily be reliable. I repeat, for pluggable devices THERE IS NO NEED FOR AN ENTRY IN /etc/fstab -- A: Yes. > Q: Are you sure? >> A: Because it reverses the logical flow of conversation. >>> Q: Why is top posting frowned upon? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
participants (8)
-
Andrei Borzenkov -
Anton Aylward -
Carlos E. R. -
Felix Miata -
Istvan Gabor -
jdd -
John Andersen -
Linda Walsh