Similar symptoms (uid/gid 4294967294) can also be caused by running
against the root's keyring quota in the kernel, which is used to store
all the id_resolv/id_legacy keys for each uid and gid.
The default kernel keyring quotas (200 keys!) in jessie's 3.16 kernel
work poorly for NFSv4 setups
Hi all,
As far as I can see, the nfs4 jessie clients caused serious problems on
the serving nfs server (which is a wheezy system), leading to an nfsd
kernel crash on the wheezy system.
FYI: the server is an up-to-date wheezy system (kernel 3.2.60-1+deb7u3).
The dumps got away as soon as I
On Fri, Sep 05, 2014 at 11:19:35AM +0200, Piet Plomp wrote:
Hi Iustin,
On 2014-09-04 19:11, Iustin Pop wrote:
[...]
Just another datapoint: this is different from my case. No new users
created, randomly new files get -1 for a while, after which the correct
UID is listed.
No, this
Hi Iustin,
On 2014-09-04 19:11, Iustin Pop wrote:
[...]
Just another datapoint: this is different from my case. No new users
created, randomly new files get -1 for a while, after which the correct
UID is listed.
No, this is not different: all new users get new files, which have never
been
Dear all,
This bug might be related to recency. I created accounts for our new
students last week. Now, a listing of the home directories on the jessie
systems shows about half of the _new_ accounts the identity as the
infamous 4294967294.
Since the new accounts were created, no reboots were
On Thu, Sep 04, 2014 at 12:32:07PM +0200, Piet Plomp wrote:
Dear all,
This bug might be related to recency. I created accounts for our new
students last week. Now, a listing of the home directories on the jessie
systems shows about half of the _new_ accounts the identity as the
infamous
Hi Ben and other readers,
I tried to find more on this issue. I have a fix, that make things
better, but not good.
First, on one of the jessie systems, I created the file
/etc/request-key.d/id_legacy.conf containing:
create id_legacy * * /usr/sbin/nfsidmap -t 600 %k %d
This itself does not make
On Mon, 2014-08-26 20:47, Ben Hutchings wrote:
Can you also test with Linux 3.16, which is packaged in experimental?
I did. This does _not_ solve the problem.
Piet
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact
Hi Ben,
Here are some tests:
A wheezy system:
For a new test I took a standard _wheezy_ system without systemd,
3.2.0-4 kernel (Debian 3.2.60-1+deb7u3). No nfs problem.
I upgraded libc6 to jessie's 2.19.9: no nfs problem.
Then I installed the linux-image-3.14.2-amd64
Control: reassign -1 src:linux 3.14.15-2
Control: found -1 3.13.10-1
Control: found -1 3.14.12-1
On Mon, 2014-08-25 at 14:43 +0200, Piet Plomp wrote:
Hi Ben,
Here are some tests:
A wheezy system:
For a new test I took a standard _wheezy_ system without systemd,
3.2.0-4 kernel
On Mon, Aug 25, 2014 at 11:47:46AM -0700, Ben Hutchings wrote:
On Mon, 2014-08-25 at 14:43 +0200, Piet Plomp wrote:
Hi Ben,
Here are some tests:
A wheezy system:
For a new test I took a standard _wheezy_ system without systemd,
3.2.0-4 kernel (Debian 3.2.60-1+deb7u3). No
Control: tag -1 moreinfo
On Fri, 2014-08-22 at 12:06 +0200, Piet Plomp wrote:
[...]
* What exactly did you do (or not do) that was effective (or
ineffective)?
aptitude update, which pulled in kernel 3.14.12, systemd for the first
time, and libc6 2.19.9? Problem has also been
Package: nfs-common
Version: 1:1.2.8-9
Severity: important
Dear Maintainer,
I'm reporting this bug in nfs (4)? where client's uid's/gid's are shown as
them instead of their regular ownerships. This has been puzzling me for over
a month now. The problem appeared after a system upgrade in jessie.
13 matches
Mail list logo