Description of problem: I have three SATA drives on my PC. The first is used for the system, two others for data. I have set a label to the second and third drives. I have added two lines in my fstab to automount rw those two drives. If I enable automount in DISK MOUNTER thoses drives appear twice ! One time as mounted (by fstab) and another time with (2) behind. This like a conflict between fstab and disk-mounter (??) So I am able to mount them a second time ! If i remove the two lines in my fstab this problem go away, BUT my drives are not mounted. This problem is new with Fedora 8. I didn't get this with fedora 7. Version-Release number of selected component (if applicable): How reproducible: each time Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info: the two lines of my fstab: LABEL=vmware /mnt/vmware ext3 rw,users,auto 0 0 LABEL=virtual-machines /mnt/vmware/virtual-machines ext3 rw,users,auto 0 0
(In reply to comment #0) > Description of problem: > I have three SATA drives on my PC. The first is used for the system, two others > for data. I have set a label to the second and third drives. I have added two > lines in my fstab to automount rw those two drives. If I enable automount in > DISK MOUNTER thoses drives appear twice ! One time as mounted (by fstab) and > another time with (2) behind. This like a conflict between fstab and > disk-mounter (??) > So I am able to mount them a second time ! Not sure you are. It's a bug in gnome-vfs2's handling of HAL that it's shown twice. Reassigning. > If i remove the two lines in my fstab this problem go away, BUT my drives are > not mounted. This problem is new with Fedora 8. I didn't get this with fedora 7. It's new in Fedora 8 that we should non-removable drives. To mount them you need to put in the root password but this authorization can be kept indefinitely. So effectively they will get automounted thereafter. > > Version-Release number of selected component (if applicable): > > > How reproducible: > each time > > Steps to Reproduce: > 1. > 2. > 3. > > Actual results: > > > Expected results: > > > Additional info: > the two lines of my fstab: > LABEL=vmware /mnt/vmware ext3 rw,users,auto 0 0 > LABEL=virtual-machines /mnt/vmware/virtual-machines ext3 rw,users,auto 0 0
David pleae, could you tell me what I have to do : either wait for this bug to be fixed, and keep my current config ? either remove the two lines in my fstab and enable automount in diskmounter ? thank you.
This message is a reminder that Fedora 8 is nearing its end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 8. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '8'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 8's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 8 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora please change the 'version' of this bug to the applicable version. If you are unable to change the version, please add a comment here and someone will do it for you. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
Fedora 8 changed to end-of-life (EOL) status on 2009-01-07. Fedora 8 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. Thank you for reporting this bug and we are sorry it could not be fixed.