> Hm, OK. Have you tried taking it upstream? It seems fairly obscure to
> me...
I'm fine with the current state of affairs and will wait until all our
kernels are updated; it the bug still persists, I'll take it upstream. Of
course, if you happen to be in contact with them, feel free to refer them
On Thu, Apr 12, 2007 at 05:29:12PM +0300, Juha Jäykkä wrote:
> Hard to say, but you seem to be correct at least in some aspects: it
> looks like the timestamps of the ticket caches have something to do
> with it.
Hm, OK. Have you tried taking it upstream? It seems fairly obscure to me...
/* Stein
> > of the services has no effect what so ever. It simply fixes itself
> > after some time. Umounting and mounting the fs immediately fixes it,
> Any progress on this?
Hard to say, but you seem to be correct at least in some aspects: it
looks like the timestamps of the ticket caches have something
On Fri, Mar 30, 2007 at 10:59:14AM +0300, Juha Jäykkä wrote:
> Just saw it all happen with nfs-common/1:1.0.12-4+b1. Restarting any of
> the services has no effect what so ever. It simply fixes itself after
> some time. Umounting and mounting the fs immediately fixes it, IIRC. But
> umounting an fs
> Yes, please. I don't think there's been huge changes, but both the
> client and server sides have gotten a few fixes since this.
Just saw it all happen with nfs-common/1:1.0.12-4+b1. Restarting any of
the services has no effect what so ever. It simply fixes itself after
some time. Umounting and
> You will definitely need to include your nfs-utils version.
Ach, sorry. I assume you mean nfs-common (there is no nfs-utils), which is
nfs-common:
Installed: 1:1.0.10-5
I realise this is rather old. Should we hold on until I see the same
happen with a current version? This has, otoh, been oc
On Tue, Mar 27, 2007 at 01:16:49PM +0300, Juha Jäykkä wrote:
> nfs-common:
> Installed: 1:1.0.10-5
>
> I realise this is rather old. Should we hold on until I see the same
> happen with a current version?
Yes, please. I don't think there's been huge changes, but both the client and
server sides
On Tue, Mar 27, 2007 at 10:20:53AM +0300, Juha Jäykkä wrote:
> Package: nfs-kernel-server
> Severity: important
You will definitely need to include your nfs-utils version.
> Kernel: Linux 2.6.17+juhaj+v1.0
Is this the same on the client and the server? Have you tried a newer kernel,
if possible?
Package: nfs-kernel-server
Severity: important
We have an environment with some NFSv4 mounts (of the type sec/krb5). These
work like a charm, UNTIL intermittently the mounts become inaccessible.
Sometimes the mounts only become read-only, sometimes totally inaccessible.
This can happen during the
9 matches
Mail list logo
