Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 154648 - sys-apps/hal-0.5.7.x - autofs mounts loop
Summary: sys-apps/hal-0.5.7.x - autofs mounts loop
Status: RESOLVED FIXED
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: [OLD] Core system (show other bugs)
Hardware: All Linux
: High normal (vote)
Assignee: Project Gentopia
URL:
Whiteboard:
Keywords:
: 154647 (view as bug list)
Depends on:
Blocks:
 
Reported: 2006-11-10 02:02 UTC by Sergey A. Sukiyazov
Modified: 2007-02-09 08:02 UTC (History)
2 users (show)

See Also:
Package list:
Runtime testing required: ---


Attachments
Patch (origin by John (J5) Palmieri <johnp@redhat.com>, added support 'subfs') solves this problem. (hal-0.5.7-fix-for-nfs-and-autofs.patch,2.98 KB, patch)
2006-11-10 02:05 UTC, Sergey A. Sukiyazov
Details | Diff
Sample configuration for using autofs and hal in gentoo (config-autofs+hal-gentoo.tar,50.00 KB, application/x-tar)
2007-02-09 07:49 UTC, Sergey A. Sukiyazov
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Sergey A. Sukiyazov 2006-11-10 02:02:13 UTC
On mounts managed by autofs (fstype == 'autofs') or submount (fstype == 'subfs') accessing 
files below the mount point cause the mount point to be remounted after an unmount.HAL daemon
try check for the .created-by-hal file on mounts under autofs mount points, then autofs (or
submount) mount filesystem again - we have dead loop.
Comment 1 Jakub Moc (RETIRED) gentoo-dev 2006-11-10 02:05:26 UTC

*** This bug has been marked as a duplicate of 154647 ***
Comment 2 Sergey A. Sukiyazov 2006-11-10 02:05:34 UTC
Created attachment 101589 [details, diff]
Patch (origin by John (J5) Palmieri <johnp@redhat.com>, added support 'subfs') solves this 
problem.

Patch (origin by John (J5) Palmieri <johnp@redhat.com>, added support 'subfs') solves this problem. In hal >= 0.5.8.x this problem alredy solved.

Keep list of autofs (subfs) filesystem so we do not check for the .created-by-hal file on mounts under autofs mount points
Comment 3 Jakub Moc (RETIRED) gentoo-dev 2006-11-10 02:06:45 UTC
Don't restrict bugs without any reason. Just leave the checkboxes alone if you have no clue what are they used for. Also fix your browser refresh.
Comment 4 Jakub Moc (RETIRED) gentoo-dev 2006-11-10 02:07:06 UTC
*** Bug 154647 has been marked as a duplicate of this bug. ***
Comment 5 Peter Volkov (RETIRED) gentoo-dev 2007-01-30 12:16:41 UTC
Any progress here? BTW. Does anybody knows why hal-0.5.8.1 is not in portage?
Comment 6 Peter Volkov (RETIRED) gentoo-dev 2007-01-30 12:22:15 UTC
Remi already answered me, why new hal version is not in portage (in bug #160377).
Comment 7 Doug Goldstein (RETIRED) gentoo-dev 2007-01-30 16:35:32 UTC
pva: Quit being a ricer. hal 0.5.8.1 is broken. It's not going in the tree. You sound like a whiny user... not a dev..

On a related note, this will be in hal-0.5.7.1-r4
Comment 8 realw98 2007-02-09 06:27:07 UTC
sys-apps/hal-0.5.7.1-r4 still has the same problem with autofs, although patch exists and applied successfully.
Comment 9 Sergey A. Sukiyazov 2007-02-09 07:49:39 UTC
Created attachment 109602 [details]
Sample configuration for using autofs and hal in gentoo

It is my configuration for use hal and autofs, to access removable media without calling mount command (tarball packed relative root directory). When
media inserted, hal create directory '/mnt/autfs/<media name>' and symlink 'auto' to path '/var/lib/autofs/hal/<device udi>'. When media removed, hal also remove directory '/mnt/autfs/<media name>'
Comment 10 Sergey A. Sukiyazov 2007-02-09 07:57:59 UTC
(In reply to comment #8)
> sys-apps/hal-0.5.7.1-r4 still has the same problem with autofs, although patch
> exists and applied successfully.
> 

You use KDE and konquerror as filemanager with treeview for directory structure?
If not, please send your configuration (hals *.fdi, autofs files and etc.)
Comment 11 Sergey A. Sukiyazov 2007-02-09 08:02:38 UTC
At me (with sys-apps/hal-0.5.7.1-r4) this problem does not occured. Try configuration from attachment #2 [details].