Comment 5 for bug 571972

am-utils is getting harder and harder to keep working. The upstream
project is dead, to all intents and purposes. There hasn't been any
release from them for at least two years, possibly more. The code has
not kept up with changes in the Linux kernel lately. It got so
painful for us at work we switched to autofs instead. Not as feature-
rich, but more active as a project.

I'll have one more go at contacting upstream. If no timeline appears
for further development, I will probably orphan the debian packaging.

Tim

On 21 May 2010, at 12:24, Gabriele Greco <email address hidden>
wrote:

> I've tried to apply the patch with a partial success, the patched
> version is able to mount the NFS filesystems BUT it's not able to go
> past listing the files, I still get this error:
>
> [85349.668258] svc: failed to register lockdv1 RPC service (errno 97).
>
> Then when I try to access the files I get:
>
> ls -lrt /net/wyoming/tmp/
> ls: cannot access /net/wyoming/tmp/testsuite06052010.tar: Input/
> output error
> ls: cannot access /net/wyoming/tmp/RIEPILOGO PROGETTI.doc: Input/
> output error
> ls: cannot access /net/wyoming/tmp/MCT2_2.15.3.run: Input/output error
>
> I tried also with the patch on the debian bug tracking without any
> success... (same behaviour of the unpatched version)
>
> --
> With Lucid Lynx after upgrade or install mounts mounted with
> automounter daemon don't mount
> https://bugs.launchpad.net/bugs/571972
> You received this bug notification because you are subscribed to am-
> utils in ubuntu.
>
> Status in “am-utils” package in Ubuntu: New
>
> Bug description:
> Binary package hint: am-utils
>
> 1. This occurs both in upgrades from 9.10 and Fresh Installs.
>
> 2. Recreation method: Start am-utils
>
> 3. Significant error messages (similar too)
>
> Apr 29 17:42:02 temp6 amd[4285]/error: '/net': mount: No
> locks available
>
> or
> Apr 29 17:42:03 temp6 amd[4283]/fatal: amfs_toplvl_mount:
> amfs_mount failed: No locks available
>
>
> This occurs with configuration files that prior to the upgrade/
> install worked fine. This does however have a work around that for
> me at least has proven 100% effective. Adding this line to the
> [global] section of /etc/am-utils/amd.conf
>
> mount_type = autofs
>
> Seems that this is actually an upstream kernel problem with kernels
> above 2.6.24, however I felt it would be best to report it for the
> purpose of tracking and finding a way to alert people on how to
> manage this problem. Additionally I've tested putting the line into
> the amd.conf of 9.10 systems and it has had no negative affect on
> performance.
>
>