Community Packages

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#25720 - [autofs] never unmounts devices

Attached to Project: Community Packages
Opened by name withheld (Gullible Jones) - Monday, 22 August 2011, 20:26 GMT
Last edited by Lukas Fleischer (lfleischer) - Friday, 02 September 2011, 10:42 GMT
Task Type Bug Report
Category Packages
Status Closed
Assigned To Lukas Fleischer (lfleischer)
Architecture i686
Severity Medium
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

When running, autofs will properly mount any mountable device as it is accessed. But when the device stops being accessed, autofs is supposed to unmount it after the appropriate timeout. I have yet to the current version of autofs do this under any circumstances - devices have to be unmounted root.

This was with autofs 5.0.6-2. FWIW I was using Thunar as a file manager - but *without* GVFS/udisks/HAL, or anything else that might have been polling the hardware all the time (AFAIK).

Steps to reproduce:

1. Set autofs to automount a drive. Any drive.

2. Plug in said drive and access it with ls.

3. Wait until the timeout runs out. Wait a few more seconds, or maybe a few minutes.

4. Run df. It will show the drive still mounted.

Note that I've only tested this with i686, it might also apply on x86_64...
This task depends upon

Closed by  Lukas Fleischer (lfleischer)
Friday, 02 September 2011, 10:42 GMT
Reason for closing:  Not a bug
Additional comments about closing:  Seems like this is a gamin issue. Check the comments.
Comment by Lukas Fleischer (lfleischer) - Tuesday, 23 August 2011, 10:43 GMT
I'm pretty sure that this isn't a packaging bug. Did this work for you with autofs<5.0.6? Did you set "$TIMEOUT" or any special arguments in "/etc/conf.d/autofs"?

You could also try running `automount -f -d -v` to check what happens.
Comment by name withheld (Gullible Jones) - Tuesday, 23 August 2011, 15:05 GMT
I did set $TIMEOUT to 2 seconds in /etc/conf.d/automount. Got the same result with --timeout=2. I'll see about 'automount -f -d -v'.

Edit: I'm actually unable to reproduce this now, at least on the CLI. Could it be that gamin was messing things up by polling the directories involved?

Edit again: major duh, several websites mention autofs having trouble with FAM so of course gamin is probably the issue. Sorry about this.

Loading...