FWIW, just did an upgrade on some systems.
All preices machines, all were running -39
Upgraded to -48, this bug appeared.
Rolled back the clients only to -39, bug disappeared.
Site is a semi heavy web service with 1 NFS server, and 2 NFS clients
running nginx/php.
Issue was seen almost
I was hoping for something we could reproduce at will without impacting
production machines. If you can find a way to simulate the load to
cause this issue*, we can proceed. If not, I'm not sure we have
another way to proceed on this bug.
I'm going to run some of these tests myself, but you
@darylounet
Please tell us more about your setup. On the server, /etc/exports, and on the
client the output of fstab, etc. Are you using kerberos encryption?
How often does it happen? Do you have to do something to casue it?
Can you reproduce it at will?
--
You received this bug
Ok, all my servers are VM hosted on AWS EC2.
I have one NFS server (called back) that I recently upgraded on Ubuntu 13.04
with the saucy 3.9.2 kernel (I haven't tried 3.9.3 yet).
I have 1,n web server(s) (called front) that runs PHP files that read/write
media and cache files on the NFS server.
If you can distill it to an easy to rebuild setup that would be very
helpful (that isn't dependent on AWS). Does the issue happen if you
scale up even if there isn't load? Or, in other words, is one of your
scripts or apps important for reproducing this issue? If so, can it be
narrowed down
No, it happens only on production environment with high load. I think
that it's related to multiple concurrent writes by our software, eZ
Publish.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/932687
I'm running Ubuntu 13.04 for the NFS Server and Ubuntu 12.04.2 on NFS
clients, with the latest saucy kernel 3.9.2 for both clients server.
I'm still having the issue :
2013-05-14 20:13:54.0 front Warnkernel front kernel: [16314892.359664]
NFS: nfs4_reclaim_open_state: Lock reclaim
The 3.9 kernel has been released and if you are still having this issue
please give it a try: http://kernel.ubuntu.com/~kernel-
ppa/mainline/v3.9.1-saucy/
** Changed in: linux (Ubuntu)
Status: Confirmed = Incomplete
--
You received this bug notification because you are a member of Ubuntu
** Changed in: linux (Ubuntu)
Status: Triaged = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/932687
Title:
nfs4_reclaim_locks: unhandled error crashes applications and creates
The v3.9-rc6 kernel has some more fixes that appear to be related.
Could anyone try it? Is anyone still experiencing this issue?
http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.9-rc6-raring/
Instructions are here:
https://wiki.ubuntu.com/Kernel/MainlineBuilds#Installing_Mainline_Kernels
--
The v3.7-rc4 kernel is now available. It would be great if you could
test this latest kernel, which can be downloaded from:
http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.7-rc4-raring/
Note that you need to install both the linux-image and linux-image-extra
packages.
Thanks in advance!
--
Any news on this? We're experiencing exactly the same problems as described by
Peter, except that the workaround doesn't work for us.
We have a lot of Ubuntu 10.04 LTS clients running with /home mounted through
NFSv4, with a Debian 6.0 server. We also had a single test machine running
12.04 for
Since the nfs client-adress is correct, it still works for us with
four 12.04 boxes, no crashes and no error messages anymore. There are
probably serveral causes for the nfs4 reclaim error. Keep in mind, we
have a solaris 10 as nfs-Server ... maybe there is something wrong on
the server-side?
--
We don't use networkmanager but configure the interfaces through
/etc/network/interfaces all the time.. But we still have this problem.
I figured out, that autofs-mounts have the correct clientaddr set while
fstab mounts don't. Our fstab-mounts also have clientaddr=0.0.0.0. But
when I manually
I experienced no server side crashes. This is really a crazy bug!
We have 25 Linux Boxes with 10.04 LTS everything works fine. I start to upgrade
one by one. Still working when i start to upgrade the first box to 12.04.
However, after upgrading the second one, both 12.05 boxes crashes with
After rebooting the ubuntu 12.04 box and login to system, I found the following:
the mount command shows:
server:/path on /home/user type nfs4
(rw,nosuid,proto=tcp,port=2049,sloppy,addr=IP ,clientaddr=0.0.0.0)
clientaddr=0.0.0.0 is definitively wrong.
To correct this, I had to disable
Maybe related to this problem we experienced a crash of our fileserver.
Can you also confirm this on your setup? Because we aren't fully sure if
the one problem is related to the other.
In the meantime, as we couldn't solve this problem, were using NFS3 on
oneiric without problems..
--
You
Are there any news about this issue?.
After upgrading from ubuntu 10.04 to ubuntu 12.04 precise, we are getting the
same errors like it is described in this bug-report. We have an solaris nfs
server and serveral Ubuntu box's as nfsv4 client. This worked fine with 10.04,
with 12.04 we are
** Changed in: linux (Ubuntu)
Status: Confirmed = Triaged
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/932687
Title:
nfs4_reclaim_locks: unhandled error crashes applications and creates
This issue appears to be an upstream bug, since you tested the latest
upstream kernel. Would it be possible for you to open an upstream bug
report at bugzilla.kernel.org [1]? That will allow the upstream
Developers to examine the issue, and may provide a quicker resolution to
the bug.
If you
I will also perform some searches upstream to see if this issue is being
discussed.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/932687
Title:
nfs4_reclaim_locks: unhandled error crashes
Okay some more information:
The problem doesn't appear when just one Oneiric is running (in this
case it's running fine!) but as soon as a second Oneiric-installation is
used at the same time the problem appears. It also appears when I
install the Natty-kernel on both of those machines and they
Okay tested and the problem also appears when both Oneirics are running
kernel 3.3.0-030300rc3-generic
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/932687
Title:
nfs4_reclaim_locks: unhandled
apport information
** Tags added: apport-collected
** Description changed:
We tried to move our Natty clients to Oneiric but have a severe show-
stopper bug. Oneiric seems to have a problem with nfs. We use nfs for
our home-folders with strict permissions. nfs4-server is running
@Joseph: Which kernel do you mean should I test? Here's just v3.2 rc4
for oneiric http://kernel.ubuntu.com/~kernel-ppa/mainline/ or shall I
manually compile the most recent kernel?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Okay downgrading to 3.0.0-12 doesn't change anything, but downgrading to
the latest natty-kernel 2.6.38-13-generic seems to have fixed the
problem, at least so far (no hangs within two hours now).
If someone has the same problem, I just downloaded the natty-kernel
here:
It would be great if you could try the kernel available at:
[1] http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.3-rc3-precise/
There is a .deb file located at that link, so you should be able to
download it and run:
sudo dpkg -i FILE_NAME.deb
--
You received this bug notification because you
Since this is an nfs client issue with kernel backtraces, which means
it's definitely a bug in the kernel, not in the nfs-utils package.
** Changed in: nfs-utils (Ubuntu)
Status: New = Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Since this is an nfs client issue with kernel backtraces, it's
definitely a bug in the kernel, not in the nfs-utils package.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/932687
Title:
Would it be possible for you to test the latest upstream kernel? It
will allow additional upstream developers to examine the issue. Refer to
https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v3.3 kernel[1] (Not a kernel in the daily directory). Once you've
tested the upstream
** Also affects: nfs-utils (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/932687
Title:
nfs4_reclaim_locks: unhandled error crashes applications
31 matches
Mail list logo
