On 10 Jun 2008, at 9:27 pm, Philippe Troin wrote:
This is caused by amd's top-level mounts which are mounted by default
with NLM locks enabled (lock mount option). Locks are not required
for the top-level mounts. The attached patch passes "nolock" to
top-level mount requests.
The attached pa
On 11 Jun 2008, at 6:53 am, Philippe Troin wrote:
Where at? I've just seen the bug log.
Let me rummage through my email a second ... see:
http://bugzilla.kernel.org/show_bug.cgi?id=10349
and
https://bugzilla.am-utils.org/show_bug.cgi?id=612
for various discussions. The second one shows
Tim Cutts <[EMAIL PROTECTED]> writes:
> On 10 Jun 2008, at 9:27 pm, Philippe Troin wrote:
>
> > This is caused by amd's top-level mounts which are mounted by default
> > with NLM locks enabled (lock mount option). Locks are not required
> > for the top-level mounts.
>
> > The attached patch pa
On 10 Jun 2008, at 9:27 pm, Philippe Troin wrote:
This is caused by amd's top-level mounts which are mounted by default
with NLM locks enabled (lock mount option). Locks are not required
for the top-level mounts.
The attached patch passes "nolock" to
top-level mount requests.
It's a more
This is caused by amd's top-level mounts which are mounted by default
with NLM locks enabled (lock mount option). Locks are not required
for the top-level mounts. The attached patch passes "nolock" to
top-level mount requests.
The attached patch fixes the problem.
Phil.
diff -ruN am-utils-6.1.5
On 7 May 2008, at 9:50 am, Fredrik Olofsson wrote:
On Wednesday, May 07, 2008 at 09:10:58 +0100, Tim Cutts wrote:
This is a well known upstream bug, and affects kernels from 2.6.24
onward. I believe there is a workaround - use autofs as the default
mount type, so in your /etc/am-utils/amd.con
On Wednesday, May 07, 2008 at 09:10:58 +0100, Tim Cutts wrote:
> This is a well known upstream bug, and affects kernels from 2.6.24
> onward. I believe there is a workaround - use autofs as the default
> mount type, so in your /etc/am-utils/amd.conf [global] section, you
> need:
>
> mount_ty
This is a well known upstream bug, and affects kernels from 2.6.24
onward. I believe there is a workaround - use autofs as the default
mount type, so in your /etc/am-utils/amd.conf [global] section, you
need:
mount_type = autofs
Obviously, for this to work you need autofs support in your
Package: am-utils
Version: 6.1.5-9
Severity: normal
After upgrading to 2.6.25 amd complains about no locks available and do
not work. This is logged in daemon.log when running
/etc/init.d/am-utils start:
May 7 09:49:19 pcfredriko amd[10040]: '/net': mount: No locks available
May 7 09:49:20 pcfr
9 matches
Mail list logo
