Red Hat Bugzilla – Bug 472778
RHEL 5.2: /proc/mounts cluttered when using NFS&snapshots on NetApp NAS
Last modified: 2011-08-06 00:22:14 EDT
Description of problem:
/proc/mounts gets cluttered when browsing snapshots on NFS mounted volume from NetappNAS
Version-Release number of selected component (if applicable):
affects all recent 2.6.18 kernels, it does not affect 2.6.8 kernel line (RHEL-4). Also, NFSv4 mounted volumes are not affected.
Steps to Reproduce:
1. mount a NFS share from NetApp NAS.
2. Enter snapshots directory (usually .snapshot) and browse via "ls -alR"
3. see the messy /proc/mounts
/proc/mounts get messed up with record for every single directory in that snapshots.
Gnome-VFS is relying on /proc/mounts and is it gets too big Gnome-VFS stops responding and all Gnome session freezes on the affected machine.
/proc/mounts should be possible left intact by this (ls -laR) operation.
It only affect NFSv3 mounted volumes, not NFSv4.
What do you mean by "gets cluttered"? Could you post an example?
Created attachment 324624 [details]
Example of /proc/mounts when this happens
After discussing this with Ondrej I asked for examples of /proc/mounts and /etc/mtab and here they are.
Created attachment 324625 [details]
Example of /etc/mtab when this happens
And here is /etc/mtab.
According to this:
is what we see an expected (and correct) behavior. The NFS client in 2.6.9 is not behaving correctly (according to this).
Which means that there is a bug in RHEL5 kernels which prevents the internally mounted filesystems (forced by a different FSID) to be automatically unmounted (after timeout). I see this has been fixed in 2.8.24. Can we have this backported into RHEL5 please?
(In reply to comment #4)
> According to this:
> is what we see an expected (and correct) behavior. The NFS client in 2.6.9 is
> not behaving correctly (according to this).
> Which means that there is a bug in RHEL5 kernels which prevents the internally
> mounted filesystems (forced by a different FSID) to be automatically unmounted
> (after timeout). I see this has been fixed in 2.8.24. Can we have this
> backported into RHEL5 please?
I can't seem to see anything between RHEL 2.6.18 and vanilla 2.6.24
that looks like it relates to this. What information do you have
I can not replicate this reliably - possibly something to do with my local configuration. Not a bug. Sorry for wasting your time. Can you close this issue (can not do it myself)? Thanks. Ondrej
(In reply to comment #9)
> I can not replicate this reliably - possibly something to do with my local
> configuration. Not a bug. Sorry for wasting your time. Can you close this issue
> (can not do it myself)? Thanks. Ondrej
Right, and I couldn't see anything that looked related.
So, if there is an issue, it's likely much more subtle
which would be much harder to port or even identify the
If you get more information, please re-open this bug.