[opensuse] openSUSE 12.3. automount, /media
Hi, Since I've upraded to 12.3 I don't understand the automounting logic anymore. Some external medias are mounted in /media and some in /var/run/user/$USER. I want to have automount independent from any particular user. Usually there are none, one or many users logged in and it's not clear who has insterted the media and who wants to do use it. How can I set that always /media is used again? And how can set the permissions which should be used? cu, Rudi -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Wednesday, 2013-07-17 at 22:50 +0200, Ruediger Meier wrote:
Since I've upraded to 12.3 I don't understand the automounting logic anymore. Some external medias are mounted in /media and some in /var/run/user/$USER.
I want to have automount independent from any particular user. Usually there are none, one or many users logged in and it's not clear who has insterted the media and who wants to do use it.
in "/etc/udev/rules.d/99-correct-media-mount-point.rules" write: ENV{ID_FS_USAGE}=="filesystem|other|crypto", ENV{UDISKS_FILESYSTEM_SHARED}="1" then run udevadm control --reload
And how can set the permissions which should be used?
Dunno. - -- Cheers, Carlos E. R. (from 12.3 x86_64 "Dartmouth" at Telcontar) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (GNU/Linux) iEYEARECAAYFAlHnH8UACgkQtTMYHG2NR9UlKgCfTjfV/PXQlf2VXqJ2S7KLf0JR MhEAn2iTrtJ7GMZQiSukUc6QX/HUPoln =yJaM -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Thursday 18 July 2013, Carlos E. R. wrote:
On Wednesday, 2013-07-17 at 22:50 +0200, Ruediger Meier wrote:
Since I've upraded to 12.3 I don't understand the automounting logic anymore. Some external medias are mounted in /media and some in /var/run/user/$USER.
I want to have automount independent from any particular user. Usually there are none, one or many users logged in and it's not clear who has insterted the media and who wants to do use it.
in "/etc/udev/rules.d/99-correct-media-mount-point.rules" write: ENV{ID_FS_USAGE}=="filesystem|other|crypto", ENV{UDISKS_FILESYSTEM_SHARED}="1"
then run
udevadm control --reload
Thanks, I couldn't yet really check whether this is working or not because I can't reproduce the mounting under /var/run/user/$USER It's a real pain. Now automounting stopped working at all since I have invoked one time udevadm monitor How can I enable it again? cu, Rudi -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Thursday 18 July 2013, Carlos E. R. wrote:
On Wednesday, 2013-07-17 at 22:50 +0200, Ruediger Meier wrote:
Since I've upraded to 12.3 I don't understand the automounting logic anymore. Some external medias are mounted in /media and some in /var/run/user/$USER.
I want to have automount independent from any particular user. Usually there are none, one or many users logged in and it's not clear who has insterted the media and who wants to do use it.
in "/etc/udev/rules.d/99-correct-media-mount-point.rules" write: ENV{ID_FS_USAGE}=="filesystem|other|crypto", ENV{UDISKS_FILESYSTEM_SHARED}="1" then run
udevadm control --reload
OK, this works. This rule is only needed when using udisks2. It's really strange that we have udisks 1 and 2 running in parallel. It's a race whether udisks 1 or 2 gets a media mounted first.
And how can set the permissions which should be used?
I've got it working now. The easiest way is to not use udisks at all. Just mount medias directly with udev rules before udisks is able to do something strange. For now I am using quick and dirty this rule https://wiki.archlinux.de/title/Udev#Unter_.2Fmedia_einbinden.3B_Partitions_... It's still not perfect but seems to do what I want already. cu, Rudi -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Saturday, 2013-07-20 at 11:44 +0200, Ruediger Meier wrote:
On Thursday 18 July 2013, Carlos E. R. wrote:
in "/etc/udev/rules.d/99-correct-media-mount-point.rules" write: ENV{ID_FS_USAGE}=="filesystem|other|crypto", ENV{UDISKS_FILESYSTEM_SHARED}="1" then run
udevadm control --reload
OK, this works. This rule is only needed when using udisks2. It's really strange that we have udisks 1 and 2 running in parallel. It's a race whether udisks 1 or 2 gets a media mounted first.
Oh :-( This is what I have installed: Telcontar:~ # rpm -qa | grep udisks libudisks2-0-2.0.0-5.4.1.x86_64 udisks-glue-1.3.1-86.1.1.x86_64 udisks-1.0.4-11.1.1.x86_64 udisks2-2.0.0-5.4.1.x86_64 Telcontar:~ # However, another machine freshly installed only has: eleanor3:~ # rpm -qa | grep udisks udisks2-2.0.0-5.4.1.x86_64 libudisks2-0-2.0.0-5.4.1.x86_64 eleanor3:~ # ie, only version 2. What needs version 1? :-?
And how can set the permissions which should be used?
I've got it working now. The easiest way is to not use udisks at all. Just mount medias directly with udev rules before udisks is able to do something strange. For now I am using quick and dirty this rule https://wiki.archlinux.de/title/Udev#Unter_.2Fmedia_einbinden.3B_Partitions_...
It's still not perfect but seems to do what I want already.
- -- Cheers, Carlos E. R. (from 12.3 x86_64 "Dartmouth" at Telcontar) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (GNU/Linux) iEYEARECAAYFAlHqfY8ACgkQtTMYHG2NR9XgagCfT0ltkFR4wSY/5/E0aep76+sH YqcAnRKpYSEbaJeuc8nesvFrzv9Sfaer =EaIv -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Saturday 20 July 2013, Carlos E. R. wrote:
On Saturday, 2013-07-20 at 11:44 +0200, Ruediger Meier wrote:
On Thursday 18 July 2013, Carlos E. R. wrote:
in "/etc/udev/rules.d/99-correct-media-mount-point.rules" write: ENV{ID_FS_USAGE}=="filesystem|other|crypto", ENV{UDISKS_FILESYSTEM_SHARED}="1" then run
udevadm control --reload
OK, this works. This rule is only needed when using udisks2. It's really strange that we have udisks 1 and 2 running in parallel. It's a race whether udisks 1 or 2 gets a media mounted first.
Oh :-(
This is what I have installed:
Telcontar:~ # rpm -qa | grep udisks libudisks2-0-2.0.0-5.4.1.x86_64 udisks-glue-1.3.1-86.1.1.x86_64 udisks-1.0.4-11.1.1.x86_64 udisks2-2.0.0-5.4.1.x86_64 Telcontar:~ #
However, another machine freshly installed only has:
eleanor3:~ # rpm -qa | grep udisks udisks2-2.0.0-5.4.1.x86_64 libudisks2-0-2.0.0-5.4.1.x86_64 eleanor3:~ #
ie, only version 2. What needs version 1? :-?
It comes with KDE3 rudi@tenfore:~> rpm -q --whatrequires udisks kdebase3-workspace-3.5.10.1-50.1.2.x86_64 rudi@tenfore:~> rpm -q --whatrequires udisks-glue kdebase3-workspace-3.5.10.1-50.1.2.x86_64 see rudi@tenfore:~> grep udisks /opt/kde3/bin/startkde killall udisks-glue /usr/bin/udisks-glue --config /opt/kde3/share/config/udisks-glue.conf That means there is always udisks-glue running after logging into kde3. And it will not be killed after loging out ... much fun for the next user who logs in and tries to mount something. BTW KDE3 on SUSE 12.3 has udisk2 support, so udisks2 would be used when mounting devices by mouse click from the system:/media page. The funny thing is that you can't use udisks2 (udisksctl) on devices which were mounted by udisks-1, so the "safely remove button" won't work because of the running udisks-glue. I'd say udisk-1 should be de-installed to avoid these stupid conflicts. On the other hand running udisks-glue would be nice if you want to automount independent from the used windowmanager. Pity that udisks-glue does not use the udisk2 interface. But as said before, probably I will disable both udisks-1 and 2, using udev directly. udisks default mount options are useless anyway if you have multiple users. I see no way to get them configured to do something useful. cu, Rudi -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
В Sat, 20 Jul 2013 15:37:56 +0200 Ruediger Meier <sweet_f_a@gmx.de> пишет:
But as said before, probably I will disable both udisks-1 and 2, using udev directly. udisks default mount options are useless anyway if you have multiple users. I see no way to get them configured to do something useful.
udisks takes mount options from client. I do not know the current state of KDE, but in GNOME3 there is no way to customize mount options, at least I could not find any. You can supply mount options using e.g. "udiskctl mount -o ... " -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
After noticing: Jul 19 00:19:32 wahoo smartd[5815]: Device: /dev/sdc [SAT], FAILED SMART self-check. BACK UP DATA NOW! Jul 19 00:19:33 wahoo smartd[5815]: Device: /dev/sdc [SAT], Failed SMART usage Attribute: 5 Reallocated_Sector_Ct. I made a complete backup: wahoo:~ # pvdisplay --- Physical volume --- PV Name /dev/sdc VG Name pictures PV Size 698.64 GiB / not usable 888.00 KiB Allocatable yes (but full) PE Size 4.00 MiB Total PE 178851 Free PE 0 Allocated PE 178851 PV UUID 0E32Pe-jLlc-TmaC-bh1B-FkTI-hclJ-5KjFK6 wahoo:~ #hwinfo --disk 25: IDE 200.0: 10600 Disk [Created at block.243] UDI: /org/freedesktop/Hal/devices/storage_serial_ST3750640AS_5QD11H9W Unique ID: _kuT.dg173GjeJJ4 Parent ID: RE4e.L7HgSFR5QYC SysFS ID: /class/block/sdc SysFS BusID: 2:0:0:0 SysFS Device Link: /devices/pci0000:00/0000:00:08.0/host2/target2:0:0/2:0:0:0 Hardware Class: disk Model: "ST3750640AS" Device: "ST3750640AS" Revision: "3.AA" Serial ID: "5QD11H9W" Driver: "sata_nv", "sd" Driver Modules: "sata_nv" Device File: /dev/sdc Device Files: /dev/sdc, /dev/block/8:32, /dev/disk/by-id/ata-ST3750640AS_5QD11H9W, /dev/disk/by-id/scsi-SATA_ST3750640AS_5QD11H9W, /d$ Device Number: block 8:32-8:47 BIOS id: 0x83 Geometry (Logical): CHS 91201/255/63 Size: 1465149168 sectors a 512 bytes Geometry (BIOS EDD): CHS 1453521/16/63 Size (BIOS EDD): 1465149168 sectors Geometry (BIOS Legacy): CHS 1023/255/63 Config Status: cfg=no, avail=yes, need=no, active=unknown Attached to: #10 (IDE interface) I am considering replacing the hdd with a Seagate SATA3 4TB. Will suse kernel 2.6.38 recognize > 2TB. tks, -- (paka)Patrick Shanahan Plainfield, Indiana, USA HOG # US1244711 http://wahoo.no-ip.org Photo Album: http://wahoo.no-ip.org/gallery2 http://en.opensuse.org openSUSE Community Member Registered Linux User #207535 @ http://linuxcounter.net -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Saturday, 2013-07-20 at 10:15 -0400, Patrick Shanahan wrote: You, doing a thread hijack? X'-)
After noticing: Jul 19 00:19:32 wahoo smartd[5815]: Device: /dev/sdc [SAT], FAILED SMART self-check. BACK UP DATA NOW! Jul 19 00:19:33 wahoo smartd[5815]: Device: /dev/sdc [SAT], Failed SMART usage Attribute: 5 Reallocated_Sector_Ct.
You have to look at the output of "smartctl -a /dev/sdc".
I am considering replacing the hdd with a Seagate SATA3 4TB. Will suse kernel 2.6.38 recognize > 2TB.
The question is not only the kernel, but partitioning tools. You need to use GPT on such a disk. By the way: "2TB < size < 2 TiB" is no problem. But "size ≥ 2 TiB" is a problem. You could consider instead 2 disks of 2 TB each. IIRC, the price per gigabyte maybe lower. And 2 disks allow distributing load. - -- Cheers, Carlos E. R. (from 12.3 x86_64 "Dartmouth" at Telcontar) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (GNU/Linux) iEYEARECAAYFAlHqpXkACgkQtTMYHG2NR9WMfgCcCbQNhyG2oCMaXpQVCICJWFC9 cxYAn0DTNYwESN7PDyxfYYVXlCT1fq76 =eYky -----END PGP SIGNATURE-----
Hello, On Sat, 20 Jul 2013, Patrick Shanahan wrote:
After noticing: Jul 19 00:19:32 wahoo smartd[5815]: Device: /dev/sdc [SAT], FAILED SMART self-check. BACK UP DATA NOW! Jul 19 00:19:33 wahoo smartd[5815]: Device: /dev/sdc [SAT], Failed SMART usage Attribute: 5 Reallocated_Sector_Ct.
Oy! I use to phase out disks after they develop even 1-5 errors (i.e. use them only for cache etc. until they're too small anyway)
I am considering replacing the hdd with a Seagate SATA3 4TB. Will suse kernel 2.6.38 recognize > 2TB.
Yes. You should use a GPT though[1]. Just use 'gdisk' instead of 'fdisk'. As long as you don't want to boot from that disk, you need not to worry. HTH, -dnh [1] you _must_ once the disk is 4 TiB though. You can massage the MBR for a 2 TiB-1Sector partition + a 2^32-x sector long partition, but I advise against that. Use GPT. Unless you boot from it or Winders is involved, it's absolutely no hassle. That comes with UEFI, Winders and the usual crap involved. -- "I guess some Ba'als are bigger than others." -- Vala, SG-1 10x04 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Saturday 20 July 2013, Andrey Borzenkov wrote:
В Sat, 20 Jul 2013 15:37:56 +0200
Ruediger Meier <sweet_f_a@gmx.de> пишет:
But as said before, probably I will disable both udisks-1 and 2, using udev directly. udisks default mount options are useless anyway if you have multiple users. I see no way to get them configured to do something useful.
udisks takes mount options from client. I do not know the current state of KDE, but in GNOME3 there is no way to customize mount options, at least I could not find any.
You can supply mount options using e.g. "udiskctl mount -o ... "
Of course you can still use udisksctl (or udisks) to mount manually with the right options. Unfortunately "-o remount" is not supported so you can't correct your stupid window manager without u/mounting. The udisks-glue user daemon supports setting default mount options in it's config file but as said it's using udisks-1 and conflicts with recent window managers with udisk2 support. I don't understand why udisks daemon itself does not seem to support configurable default mount options and the ability to mount automatically without any further actions by users. I mean how stupid is the whole concept that you need at laest 5-6 daemons to just to get a media auto-mounted: - dbus - udev - polkit - consolekit? - udisks-daemon - and a client daemon for example udisks-glue And the whole construct is still not able to cover simple use cases. Moreover it is full of conflicts and race conditions and unstable/incompatible interfaces, random mount points, etc. cu, Rudi -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
* Ruediger Meier <sweet_f_a@gmx.de> [07-20-13 09:40]: [...]
I'd say udisk-1 should be de-installed to avoid these stupid conflicts. On the other hand running udisks-glue would be nice if you want to automount independent from the used windowmanager. Pity that udisks-glue does not use the udisk2 interface.
But as said before, probably I will disable both udisks-1 and 2, using udev directly. udisks default mount options are useless anyway if you have multiple users. I see no way to get them configured to do something useful.
fwiw: I run Tumbleweed and have no kde3 libs or apps. After ensuring that I could reinstall if necessary, I removed udisks and udisks-glue and the only change I noticed was umounting an external drive complained the request was not made by the mounting user and asked for root password. Subsequent mount/umount and display operations proceeded w/o complaint or *noticed* differences. intel system containing ide/sata2/sata3/usb2/usb3 storage devices. -- (paka)Patrick Shanahan Plainfield, Indiana, USA HOG # US1244711 http://wahoo.no-ip.org Photo Album: http://wahoo.no-ip.org/gallery2 http://en.opensuse.org openSUSE Community Member Registered Linux User #207535 @ http://linuxcounter.net -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
participants (5)
-
Andrey Borzenkov -
Carlos E. R. -
David Haller -
Patrick Shanahan -
Ruediger Meier