| Summary: | sys-apps/hal 0.5.9 does not detect that / is mounted | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | Brian Beardall <brian> |
| Component: | [OLD] Core system | Assignee: | Project Gentopia <gentopia> |
| Status: | RESOLVED FIXED | ||
| Severity: | normal | ||
| Priority: | High | ||
| Version: | 2006.1 | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
| Attachments: | fstab | ||
|
Description
Brian Beardall
2007-04-01 14:35:23 UTC
please attach or paste your /etc/fstab file Created attachment 115203 [details]
fstab
What desktop are you running in? Using Gnome, I don't see this issue at all, and I have a similar fstab equilibrium package.keywords # cat /etc/fstab /dev/hda1 /boot ext2 defaults 1 2 /dev/hda2 none swap sw 0 0 /dev/hda3 / reiserfs defaults 0 1 /dev/hdb1 /home reiserfs defaults 0 1 I am using gnome 2.18 right now. The problem isn't just there, but in hal itself. I'm currently having this problem on two computers. Here is what hal says:
8: udi = '/org/freedesktop/Hal/devices/volume_uuid_8f684969_f163_4fef_a178_717c1
7102a76'
block.minor = 3 (0x3) (int)
volume.label = '' (string)
volume.ignore = false (bool)
org.freedesktop.Hal.Device.Volume.method_names = { 'Mount', 'Unmount', 'Eject'
} (string list)
info.capabilities = { 'volume', 'block' } (string list)
volume.partition.flags = { } (string list)
volume.is_partition = true (bool)
volume.mount_point = '' (string)
info.category = 'volume' (string)
info.product = 'Volume (ext3)' (string)
volume.is_disc = false (bool)
volume.is_mounted = false (bool)
volume.partition.type = '0x83' (string)
block.is_volume = true (bool)
volume.linux.is_device_mapper = false (bool)
block.storage_device = '/org/freedesktop/Hal/devices/storage_serial_SATA_ST320
0827AS_5ND3F3LZ' (string)
info.parent = '/org/freedesktop/Hal/devices/storage_serial_SATA_ST3200827AS_5N
D3F3LZ' (string)
volume.block_size = 512 (0x200) (int)
volume.partition.number = 3 (0x3) (int)
volume.num_blocks = 386620290 (0x170b5b82) (int)
volume.fsversion = '1.0' (string)
block.device = '/dev/sda3' (string)
volume.uuid = '8f684969-f163-4fef-a178-717c17102a76' (string)
volume.partition.label = '' (string)
volume.partition.scheme = 'mbr' (string)
volume.partition.media_size = 200049647616 (0x2e93e36000) (uint64)
volume.partition.uuid = '' (string)
volume.fsusage = 'filesystem' (string)
volume.is_mounted_read_only = false (bool)
org.freedesktop.Hal.Device.Volume.method_argnames = { 'mount_point fstype extr
a_options', 'extra_options', 'extra_options' } (string list)
info.interfaces = { 'org.freedesktop.Hal.Device.Volume' } (string list)
storage.model = '' (string)
volume.size = 197949588480 (0x2e16b70400) (uint64)
info.udi = '/org/freedesktop/Hal/devices/volume_uuid_8f684969_f163_4fef_a178_7
17c17102a76' (string)
volume.mount.valid_options = { 'ro', 'sync', 'dirsync', 'noatime', 'nodiratime
', 'noexec', 'quiet', 'remount', 'exec', 'acl', 'user_xattr', 'data=' } (string
list)
org.freedesktop.Hal.Device.Volume.method_signatures = { 'ssas', 'as', 'as' } (
string list)
block.major = 8 (0x8) (int)
volume.fstype = 'ext3' (string)
org.freedesktop.Hal.Device.Volume.method_execpaths = { 'hal-storage-mount', 'h
al-storage-unmount', 'hal-storage-eject' } (string list)
volume.unmount.valid_options = { 'lazy' } (string list)
linux.hotplug_type = 3 (0x3) (int)
volume.partition.start = 2097446400 (0x7d047e00) (uint64)
linux.sysfs_path = '/sys/block/sda/sda3' (string)
This volume.is_mounted = false (bool) should be volume.is_mounted = true (bool)
and volume.ignore = false (bool) should be volume.ignore = true (bool).
Also it isn't seeing it's mount point, but sda3 is my root partition.
I'm having the same issue here. Anything greater than HAL 0.5.7.1 (0.5.9-rc3 currently) results in bonage, take a look at how volumes on my internal SATA drive are being detected by HAL (and shown in Gnome): http://img110.imageshack.us/img110/8458/volumespl5.png "25.0 GB Volume" is an NTFS partition (/dev/sda3) "25.0 GB Volume (2)" is my ext3 / partition (/dev/sda2) "25.0 GB Volume (3): 25.0 GB Volume (2)" is another NTFS partition (/dev/sda1) Both of the NTFS volumes are declared in /etc/fstab as ntfs3g mounts, as is my / partition, obviously. Double clicking "25.0 GB Volume (2)" (the ext3 partition) does nothing but the other two are accessible at the proper fstab mounts points. Shouldn't these 2 ntfs volumes also be hidden? The good news is, hal 0.5.9 final release is out. The bad news is, now I can replicate. We were previously patching for this, so I need to glance through those again. Unfortunately, I am at work for the next 8 hours. If I get some spare time though, I'll start looking. Another issue has to do with partitions that are in fstab that are mounting in different locations such as /boot that shouldn't be showing in the devices that are mountable by a user. Other than this bug; this is a good release that appears to just work. My last comment can be ignored because since my sata supports hotplug it is considered a hotplug device and so the /boot and other partitions will still show. SATA2 with hotplug. Someone might want to check this again by re-emerging hal-0.5.9. A patch was added on April 24th (files/0.5.9/16_dev_root_is_mounted.patch), which might have solved this bug. It was related to HAL not seeing / as being mounted because it read /proc/mounts which referenced /dev/root as being the block device for /, instead of whatever the real device was. The patch should have solved this problem as well (since I think this is actually the same problem as the other bug was). I did re-emerge hal a few days back after the patch was added. What has to be done now is the symlink /dev/root has to point to /dev/'real root device' and it will show up as being mounted. I'm not sure if this bug should be closed on that, but the script doesn't create the symlink, nor does udev create the symlink automatically. Brian, the that is not the change in that patch. There have been other changes. The issue is that it's a mixed kernel bug and HAL is relying on the kernel to behave properly. Since we can't rely on that, we need a workaround. It's been worked around. Issue is resolved. |
