On Mon, 2013-06-10 at 17:31 +0200, Carlos E. R. wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On 2013-06-10 17:00, Roger Oberholtzer wrote:
On Wed, 2013-06-05 at 20:11 -0400, Anton Aylward wrote:
I see (repeatable and verifiable) that if a removeable disk is in the machine when it boots (*), directories and subdirectories as defined in /etc/fstab are created, and the disk mounted as expected. The same disk, when inserted after the system boots (exact same udev rules and /etc/fstab entries), does not get the same behavior. An even more interesting thing is that when the disks are removed (via umount) the /media entries go away. And since reinsertion after boot does not result in the same mount point creation in /media, we have a problem.
Notice that what is plugged in before booting does not gets mounted by the desktop - that's the difference. I think they get mounted on behalf of "root", but I don't know exactly by what process.
(*) The SuperMicro systems we have require this or the drive bay is disabled by the BIOS. Strange but true. SuperMicro blame the intel chipset that deals with removable SATS disks.
Maybe related.
I got recently a bay for inserting hard disks into my desktop from the outside, hotw-swap. My motherboard has 6 SATA connectors on one side, 2 eSATA connector on the back edge of the board, and 2 connectors inside that are raid capable, and which I had connected via an eSATA plug to the outside.
Our SuperMicro systems are chosen specifically because the disks are hot swappable. The system very happily gets add events when a disk is inserted. Our current udev rules are: SUBSYSTEM=="block", ENV{ID_PATH}=="*-2-scsi-0:0:0:0", ENV{ID_PART_ENTRY_NUMBER}=="1", SYMLINK="cameraA 0:0:0:0", RUN+="/bin/mkdir -p /media/jboc/cameraA", RUN+="/bin/mount -oro /dev/cameraA /media/jboc/cameraA" SUBSYSTEM=="block", ENV{ID_PATH}=="*-2-scsi-1:0:0:0", ENV{ID_PART_ENTRY_NUMBER}=="1", SYMLINK="cameraB 1:0:0:0", RUN+="/bin/mkdir -p /media/jboc/cameraB", RUN+="/bin/mount -oro /dev/cameraB /media/jboc/cameraB" SUBSYSTEM=="block", ENV{ID_PATH}=="*-2-scsi-2:0:0:0", ENV{ID_PART_ENTRY_NUMBER}=="1", SYMLINK="cameraC 2:0:0:0", RUN+="/bin/mkdir -p /media/jboc/cameraC", RUN+="/bin/mount -oro /dev/cameraC /media/jboc/cameraC" SUBSYSTEM=="block", ENV{ID_PATH}=="*-2-scsi-3:0:0:0", ENV{ID_PART_ENTRY_NUMBER}=="1", SYMLINK="cameraD 3:0:0:0", RUN+="/bin/mkdir -p /media/jboc/cameraD", RUN+="/bin/mount -oro /dev/cameraD /media/jboc/cameraD" The ID_PATH tells the physical drive slot. and is system-specific. Note that we make the mount point and do the mount command at that time. Yours sincerely, Roger Oberholtzer Ramböll RST / Systems Office: Int +46 10-615 60 20 Mobile: Int +46 70-815 1696 roger.oberholtzer@ramboll.se ________________________________________ Ramböll Sverige AB Krukmakargatan 21 P.O. Box 17009 SE-104 62 Stockholm, Sweden www.rambollrst.se -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org