** Changed in: nfs-utils (Debian)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1124250
Title:
Partially incorrect uid mapping with nfs4/idmapd/ldap-auth
To
Launchpad has imported 42 comments from the remote bug at
https://bugzilla.redhat.com/show_bug.cgi?id=876705.
If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://hel
Hi, I'm still seeing this error.
root@XX:~# uname -r
3.13.0-77-generic
root@XX~#
root@~# cat /etc/issue
Ubuntu 14.04.4 LTS \n \l
root@:~#
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1124250
Title
Hi, Am I still hitting this bug ?
root@XX:~# uname -r
3.13.0-77-generic
root@XX~#
root@~# cat /etc/issue
Ubuntu 14.04.4 LTS \n \l
root@:~#
root@prod-login-west01:~# ls -l /u4/ | head
total 9356
drwx--x--x 6 nobody staff4096 Jun 24 2013 aabdul
drwx--x--x 75 nobody staff
** Changed in: nfs-utils (Debian)
Status: Fix Released => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1124250
Title:
Partially incorrect uid mapping with nfs4/idmapd/ldap-auth
To
To clarify the above comment:
Precise running 3.2 kernel: not affected
Precise running 3.13 lts kernel: affected
Trusty running 3.13 kernel: not affected
In the Precise + lts kernel case, it's possible to hack around the
userland tools to make the keys become permanent (keyutils +
libkeyutils1 +
This bug affects Precise, but it's not marked so. Back in June, I had
mentioned that it was possible to make the keys permanent by using the
trusty versions of keyutils + libkeyutils1 + libnfsidmap2. This is now
not possible anymore with the latest kernel versions available on
Precise.
I underst
Amending #71: still seeing this problem.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1124250
Title:
Partially incorrect uid mapping with nfs4/idmapd/ldap-auth
To manage notifications about this b
I'm running into this problem (keys don't get automatically renewed and
are expired after 10 minutes) on a precise server running the trusty lts
kernel.
I've just rebooted into the latest version (3.13.0.53.46), and the
problem is still present.
#33 mentions that installing keyutils fixes this.
Still see this with 3.13.0-53-generic
Installing larger values as suggested above wasn't initially very
successful. As suggested a "nfsidmap -c" and that seemed to have worked
for now.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
h
Hi,
the prolem is still present with
dpkg -s linux-image-3.16.0-38-generic
Package: linux-image-3.16.0-38-generic
Status: install ok installed
Priority: optional
Section: kernel
Installed-Size: 43744
Maintainer: Ubuntu Kernel Team
Architecture: amd64
Source: linux-lts-utopic
Version: 3.16.0-38.5
If I understood correctly, historically there have been two
independently developed alternative user-space mechanisms that can
perform uid <-> user name lookups for the Linux NFSv4 implementation in
the kernel, one from the University of Michigan and one from NetApp:
A) /usr/sbin/rpc.idmapd runs
I can confirm that the problem persists (and possibly even has become
more common) here with the recent kernel update:
$ ls -ld /some-nfsv4-mounted-directory ; cat /proc/key-users ; uname -a
drwxrwsr-x 2 4294967294 4294967294 4096 Dec 20 2007 .
/proc/key-users: 0:60 59/59 53/2000 1226/400
Hi Dariusz,
the problem is still present with Linux version 3.13.0-52-generic.
dpkg -s linux-image-3.13.0-52-generic
Package: linux-image-3.13.0-52-generic
Status: install ok installed
Priority: optional
Section: kernel
Installed-Size: 41219
Maintainer: Ubuntu Kernel Team
Architecture: amd64
Sour
Thank you Stef. I have verified the fix on trusty with trusty kernel. I
will try to set up a precise environment with trusty kernel and
reproduce this issue.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bu
Hi Dariusz,
I think
Linux version 3.13.0-51-generic (buildd@tipua) (gcc version 4.6.3
(Ubuntu/Linaro 4.6.3-1ubuntu5) ) #84~precise1-Ubuntu SMP Wed Apr 15 21:45:46
is the latest kernel.
dpkg -s linux-image-3.13.0-51-generic
Package: linux-image-3.13.0-51-generic
Status: install ok installed
Prio
Stef, thanks for the update.
Can you please confirm that you have upgraded your kernel to version
3.13.0-51.84 or later? This is the first release that has this fix. The version
you mentioned earlier (3.13.0.51.44) is expected to be still affected by this
bug.
Thank you.
--
You received this
Dariusz:
Today the problem has occurred again:
sudo cat /proc/key-users
0:65 64/64 58/200 810/2
and the /var/mail folder was hit in this case.
After a while (about 1 hour) the problem diminishes with the following
key-users result:
0:21 20/20 14/200 194/2
As I don´t understa
This bug was fixed in the package linux - 3.16.0-36.48
---
linux (3.16.0-36.48) utopic; urgency=low
[ Luis Henriques ]
* Release Tracking Bug
- LP: #1443946
* Merged back Ubuntu-3.16.0-34.47 security release
linux (3.16.0-35.46) utopic; urgency=low
[ Brad Figg ]
* Re
This bug was fixed in the package linux - 3.13.0-51.84
---
linux (3.13.0-51.84) trusty; urgency=low
[ Luis Henriques ]
* Release Tracking Bug
- LP: #1444141
* Merged back Ubuntu-3.13.0-49.83 security release
linux (3.13.0-50.82) trusty; urgency=low
[ Brad Figg ]
* Re
This bug was fixed in the package linux - 3.13.0-51.84
---
linux (3.13.0-51.84) trusty; urgency=low
[ Luis Henriques ]
* Release Tracking Bug
- LP: #1444141
* Merged back Ubuntu-3.13.0-49.83 security release
linux (3.13.0-50.82) trusty; urgency=low
[ Brad Figg ]
* Re
This bug was fixed in the package linux - 3.16.0-36.48
---
linux (3.16.0-36.48) utopic; urgency=low
[ Luis Henriques ]
* Release Tracking Bug
- LP: #1443946
* Merged back Ubuntu-3.16.0-34.47 security release
linux (3.16.0-35.46) utopic; urgency=low
[ Brad Figg ]
* Re
** Tags removed: verification-needed-trusty verification-needed-utopic
** Tags added: verification-done-trusty verification-done-utopic
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1124250
Title:
P
stef: can you please check after you observe the problem if your key quota is
not exceeded? You may do this with:
$ sudo cat /proc/key-users
This fix is known to solve the expired keys problem, but if the cause of
the issue you are experiencing is the capacity of the key quota you may
have to ex
I have tried yesterday the image linux-image-3.13.0-51-generic for Precise
(linux-signed-image-generic-lts-trusty 3.13.0.51.44).
With no luck. I have again after some time the userid 4294967294 in shown for a
lot of files and users.
So the problem seams unfixed for me.
Stef
--
You received th
Thanks for the fix.
Is there also a linux-image-generic-lts-trusty (for 12.04LTS )test kernel
available?
Stef
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1124250
Title:
Partially incorrect uid m
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
utopic' to 'verification-done-utopic'.
If verification is not done by 5 working days from t
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
trusty' to 'verification-done-trusty'.
If verification is not done by 5 working days from t
Ah, excellent. That release is in the kernel-team PPA - that'll do for
the moment!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1124250
Title:
Partially incorrect uid mapping with nfs4/idmapd/ldap-
The fix has been tagged as:
- Ubuntu-3.13.0-50.82 for Trusty
- Ubuntu-3.16.0-35.46 for Utopic
I don't see those version available in -updates yet, so please give it
some more time to be release.
Thanks!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subs
Is there an ETA on including this in the main repos? I notice there's
been a kernel update since Dariusz's patched kernel but it looks like
this fix wasn't included.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpa
** Changed in: linux (Ubuntu Utopic)
Status: In Progress => Fix Committed
** Changed in: linux (Ubuntu Trusty)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.n
** No longer affects: nfs-utils (Ubuntu)
** No longer affects: nfs-utils (Ubuntu Trusty)
** No longer affects: nfs-utils (Ubuntu Utopic)
** Changed in: linux (Ubuntu Trusty)
Assignee: (unassigned) => Dariusz Gadomski (dgadomski)
** Changed in: linux (Ubuntu Utopic)
Assignee: (unassign
** Description changed:
+ [Impact]
+
+ * This bug is likely to cause an incorrect UID/GID mapping for NFS
+ shares in case of large numbers of differend UIDs/GIDs or in case of
+ expired UID/GID mappings (stored as keys in the kernel).
+
+ [Test Case]
+
+ 1. Setup a nfs4 server exporting /hom
Moving linux tracks back to In Progress due different solution.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1124250
Title:
Partially incorrect uid mapping with nfs4/idmapd/ldap-auth
To manage not
** Changed in: linux (Ubuntu Utopic)
Status: Won't Fix => In Progress
** Changed in: linux (Ubuntu Trusty)
Status: Won't Fix => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/
** Changed in: nfs-utils (Debian)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1124250
Title:
Partially incorrect uid mapping with nfs4/idmapd/ldap-auth
To
@Dariusz: As I have similar problems with the HWE-Kernel of trusty for my
precise installation, is it possible for ayou to build the fixed kernel also
for trusty?
Or is there a plan to include the patch in the official trusty kernel?
I have tried your trusty-kernel, but I was not able to load th
Carl, I have backported the fixes to trusty kernel. Could you please
give them a try in your environment?
The build is available in my PPA (ppa:dgadomski/kernel-nfs).
Thanks!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bu
I believe this is the commit in question:
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=0b0a84154eff56913e91df29de5c3a03a0029e38
Looks like a good canditate for considering a cherry-pick.
--
You received this bug notification because you are a member of Ubuntu
Bugs,
The fixes for the problem I was seeing related to this bug are in Linux
3.18:
https://lkml.org/lkml/2014/12/7/202
(by David Howells).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1124250
Title:
P
@Bryan
Yes, you're right. It should hit vivid and since it is already
configurable by sysctl there is no point in backporting.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1124250
Title:
Partially
@Dariusz
My understanding is that we can't backport a config change (say to
trusty). Since that was done upstream won't it just hit vivid in it's
own time? In the mean time, this is configurable so a user can change
their config in trusty.
--
You received this bug notification because you are
Hello Bryan,
The commit that has fixed this was
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=738c5d190f6540539a04baf36ce21d46b5da04bd
I think we can make use of it.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed t
It turns out in 3.17rc4 the root_maxkeys/bytes were greatly increased
which is actually what solved my issue.. Sorry for the noise.
Raw notes:
with key utils - 3.17.rc7 - main issue gone, nogroup is now 4294967294
without key utils - 3.17-rc7 - main issue gone, nogroup is fine too
all rest with
Or not.. it seems my issue was fixed somewhere between 3.13 and
3.17rc7...
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1124250
Title:
Partially incorrect uid mapping with nfs4/idmapd/ldap-auth
To
Works for original case, except nogroup now returns 4294967294, will
ping list with results..
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1124250
Title:
Partially incorrect uid mapping with nfs4/i
I think this patch:
http://article.gmane.org/gmane.linux.nfs/67156
is another fix for this bug. I'm sure it is more elegant than mine. @Bryan:
perhaps you could test it?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.l
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: nfs-utils (Ubuntu Trusty)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1124250
Ti
@carlh
Ah, your kernel patch also fixes the case where the key cache get's filled.
(Which is my issue)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1124250
Title:
Partially incorrect uid mapping
Bryan: AFAICS the thing is that keyutils changes things so that the
id_resolv uid:user@fqdn keys never expire. Without it, they expire
after 10 minutes, and that triggers the bug which my kernel patch
"fixes".
--
You received this bug notification because you are a member of Ubuntu
Bugs, which i
Interesting.. keyutils doesn't seem to help in my case.I'm running
ls on the ~27000 user accounts home directory..
I don't understand why this would help... all nfsidmap would do is clear
it once, and then it can fill up again/expire again.
--
You received this bug notification because you a
Hi Michael,
Thanks... installing keyutils seems to work for me too (without the
kernel patch). I haven't investigated too closely, but it looks like
the two fixes are sort-of equivalent. The userspace fix is far more
appealing, though!
--
You received this bug notification because you are a me
I am not entirely sure if this is 100%ly related to this bug, but let me
tell you my story here (contains another workaround):
I was also experiencing the problem of frequently having my files owned by
4294967294.
Setup is Ubuntu 14.04 with automounted nfs4/kerberos homes, the NFS server is
runn
For anyone following at home:
http://www.spinics.net/lists/linux-nfs/msg47185.html
@Carl, For the future, it's probably better to use
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/ at
least when you're pushing upstream. It does help a lot for possibly
SRUing to know that it wo
Hi Bryan, I'm glad it's working, thanks for the report. No response on
LKML yet; here's the message:
https://lkml.org/lkml/2014/9/30/435
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1124250
Title:
nfs_patch2.patch works for me w/ ~27000 home directory setup. Thanks!
Please do link to the lkml if you can (might take a few days to appear).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1124250
T
Actually, I think this patch is a bit less invasive. I'll submit to the
mainline kernel list and pick up my fire extinguisher ;)
** Patch added: "nfs_patch2.patch"
https://bugs.launchpad.net/ubuntu/+source/nfs-utils/+bug/1124250/+attachment/4220337/+files/nfs_patch2.patch
--
You received th
@Carl Hetherington
Your patch is interesting. Please submit it to the mainline kernel, and
to stable if you feel it deserves to go into stable. Once it hits
stable it will then likely get picked up by the Ubuntu 3.13 kernel.
--
You received this bug notification because you are a member of Ubu
The ubuntu kernel uses the same values as the upstream kernel in regards
to these values. They are tunable for exactly this kind of case.
I brought this case up with the Ubuntu Kernel team, and unfortunately
due to the fact that this could potentially be used in a memory-
exhaustion, denial of se
** Changed in: linux (Ubuntu Utopic)
Status: Confirmed => Won't Fix
** Changed in: linux (Ubuntu Trusty)
Status: New => Won't Fix
** Changed in: linux (Ubuntu Trusty)
Importance: Undecided => Low
--
You received this bug notification because you are a member of Ubuntu
Bugs, whi
** Also affects: nfs-utils (Ubuntu Trusty)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Trusty)
Importance: Undecided
Status: New
** Also affects: nfs-utils (Ubuntu Utopic)
Importance: Undecided
Assignee: Dariusz Gadomski (dgadomski)
Status:
The attachment "0001-Invalidate-expired-keys-when-they-are-requested-
in-o.patch" seems to be a patch. If it isn't, please remove the "patch"
flag from the attachment, remove the "patch" tag, and if you are a
member of the ~ubuntu-reviewers, unsubscribe the team.
[This is an automated message per
The attached patch is a hack (to Ubuntu's 3.13.0 as shipped with 14.04)
which seems to help here. I am no kernel developer, but maybe it will
help to describe the problem and suggest a proper solution.
** Patch added:
"0001-Invalidate-expired-keys-when-they-are-requested-in-o.patch"
https://
I have poked at this a bit. On my system, running this:
#!/bin/bash
while [ 1 ]; do
touch foo
test=`ls -lh foo | grep -v c.hetherington`
if [ "$test" == "" ]; then
echo "OOPS"
echo $test
fi
sleep 1s
rm foo
done
prints OOPS exactly 10 minutes after the first resolution of my u
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu)
Status: New => Confirmed
** Changed in: linux (Ubuntu)
Importance: Undecided => Low
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscri
William,
I'm sorry, but I cannot reproduce this issue with the kernels you
mentioned.
Are you able to provide me sosreport from the affected system?
You could also try adding -vvv option to your
/etc/request-key.d/id_resolver.conf to make it look like this:
create id_resolver * *
** Changed in: nfs-utils (Debian)
Status: Unknown => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1124250
Title:
Partially incorrect uid mapping with nfs4/idmapd/ldap-auth
To man
** Bug watch added: Debian Bug tracker #758870
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=758870
** Also affects: nfs-utils (Debian) via
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=758870
Importance: Unknown
Status: Unknown
--
You received this bug notification because
Here's an example of a broken machine with the increased maxkeys and
maxbytes. It doesn't look different to me from the one in #19.
# cat /proc/key-users
0:23 22/22 16/1 322/20
11254: 5 5/5 5/1 49/20
We also tried installing the 3.16.3-031603-generic #201409171435 kern
Hello William,
Regarding your comment #20: did the contents of /proc/key-users when you
observe to issue somehow differ from the ones you posted in comment#19?
What I am trying to determine is whether for some reasons the quota is
hit on your machine when you observe the issue or is it caused by
Still seeing the issue after increasing maxkeys and maxbytes as
specified in the last comment.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1124250
Title:
Partially incorrect uid mapping with nfs4/
Hi Dariusz,
chicken:~# cat /proc/key-users
0:32 31/31 25/1 537/20
3404: 4 4/4 4/200 38/2
11254: 3 3/3 3/200 39/2
I'm seeing the issue on both of the latest kernels 3.13.0.36.43 and
3.13.0.35.42
Increasing the values maxkeys and maxbytes and rebooting seems to ha
@blkperl
William, could you please confirm that you are using kernel at least
3.13.0-35.62 (this is a solution to #1344405 which may also cause
similar effects).
Could you also please provide the output of:
$ sudo cat /proc/key-users
You may also try to increase values (beside their root_* count
The work around in the RH ticket did not fix my issues on Ubuntu Trusty
# uname -a
Linux gentoo 3.13.0-35-generic #62-Ubuntu SMP Fri Aug 15 01:58:42 UTC 2014
x86_64 x86_64 x86_64 GNU/Linux
# cat /proc/sys/kernel/keys/root_maxbytes
20
#cat /proc/sys/kernel/keys/root_maxkeys
1
# cat /
** Changed in: nfs-utils (Ubuntu)
Assignee: (unassigned) => Dariusz Gadomski (dgadomski)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1124250
Title:
Partially incorrect uid mapping with nfs4/i
Maybe this will help: issuing of 'sudo nfsidmap -c' solves problem
immediately till next time.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1124250
Title:
Partially incorrect uid mapping with nfs4/
Confirm this for 14.04 with 3.13.0-35-generic kernel on server and
clients (all are x86_64).
Had to use nfds.nfs4_disable_idmapping=0 in order for allow idmapping to
work on old (10.04 and RHEL58) clients.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is s
Confirm this for 12.04 with hwe and trusty-kernel
(linux-3.13.0-32-generic #57~precise1-Ubuntu)
We have less than 100 ldap users and under 100 groups.
On some clients here we have to use hwe with a newer kernel to support the
hardware.
And on exactly those and only those clients from time to tim
** Also affects: fedora via
https://bugzilla.redhat.com/show_bug.cgi?id=876705
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1124250
Title:
Partially
Confirmed on ubuntu 14.04 kernel 3.13.0-27-generic with NFSv4 mounts to
an Isilon filesystem - even with very high values for the various
kernel.keys parameters, we still get sporadic failures for UID/username
mappings resulting in user or group IDs on new files showing up as
4294967294 rather than
I have created and attached a file 30-nfsv4-quota.conf for
/etc/sysctl.d/ that ups the limit at boot time for ubuntu. It fixes the
limit problem but I still have 4294967294 showing up instead of nobody
or nogroup.
** Attachment added: "this fixes the issue"
https://bugs.launchpad.net/ubuntu/+s
running:
sudo sysctl kernel.keys.root_maxkeys=1000
sudo sysctl kernel.keys.maxkeys=1000
fixes the issue for me to some extent. I still have some files with
4294967294 instead of nobody or nogroup.
I only see the problem on one ldap and nfsv4 client running ubuntu 14.04
LTS (as a testbed). My othe
For your reference:
before applying the "fix" in comment #9 the keys seem to be saturated (199/200).
(That was after "ls -al" in a nfs4 mounted dir with ~500 different owners)
# cat /proc/key-users
0: 204 203/203 199/200 6275/2
After enabling the new key quotas it showed:
# cat /proc
I was encountering the very same problem in an identical environment (nfs4 and
LDAP based nameservice) but on DEBIAN (!).
Since I was not able to find any relevant bug reports within the Debian bug
tracking system, I was very delighted to find someone having the same problem
and reporting it her
unfortunately, like comment #3 reported, the quota is not the problem.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1124250
Title:
Partially incorrect uid mapping with nfs4/idmapd/ldap-auth
To man
@denys.duchier As I understood by reading the code, this is not a bug
but a feature. In Linux 3.4 they dropped their own B-tree uid/username
caching in favor of the "key" infrastructure which, by design, includes
quota. While this is a pain in this case, it mitigates the risk of DOS
attack by fill
I am experiencing exactly the same problem. has there been progress on
this issue? is there an update available that fixes it?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1124250
Title:
Partiall
Using `git bisect`, It appears that this bug has been introduced between
v3.3 and v3.4 by this commit:
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=57e62324e469e092ecc6c94a7a86fe4bd6ac5172
--
You received this bug notification because you are a member of Ubuntu
Bugs,
Have you tried with an older kernel ? I face the same bug when using
3.10.x while there is no problem when using 3.2.x.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1124250
Title:
Partially incorre
No, it doesn't fixes the problem for me :-(
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1124250
Title:
Partially incorrect uid mapping with nfs4/idmapd/ldap-auth
To manage notifications about thi
Have a look into /proc/key-users to see if user root reaches its quotas:
0: 1029 1028/1028 10/100 2345/2
means that root uses 1022 from 1 possible an uses 2345 bytes from
maximum 2.
You may have to encrease both. For each user and group you should
increase it by one. So if you 1
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: nfs-utils (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1124250
Title:
93 matches
Mail list logo
