strange NFS behaviour after upgrade to F13
Julian C. Dunn
lists at aquezada.com
Fri Jun 4 03:02:21 UTC 2010
On 06/03/2010 10:39 PM, Julian C. Dunn wrote:
> I have upgraded both a NFS client and NFS server to F13 from F12.
> Now, on the client, all the files in my NFS home directory appear to be
> owned by nobody:nobody. It's as though they were being mysteriously
> root_squashed even though they're not owned by root.
> Oddly enough, all read/write operations seem to work. The only reason I
> noticed is because I tried to SSH to the server and ssh(1) refused to
> read the $HOME/.ssh/config.
> Anyone have any ideas? On the client I have:
> demeter:/home /home nfs defaults 0 0
> in /etc/fstab and on the server:
> /home 192.168.5.0/24(rw,sync)
> in /etc/exports.
Hmm... seems like I might be the victim of a kernel bug:
IMA: unmeasured files on fsmagic: EF53
ima_dec_counts: open/free imbalance (r:1 w:-1 o:0)
Pid: 1292, comm: nfsd Not tainted 220.127.116.11-112.fc13.x86_64 #1
[<ffffffffa035cb7a>] nfsd_close+0x9/0xb [nfsd]
[<ffffffffa036e9aa>] release_open_stateid+0x3a/0x47 [nfsd]
[<ffffffffa03718b9>] nfsd4_close+0x8c/0x112 [nfsd]
[<ffffffffa0366a84>] nfsd4_proc_compound+0x211/0x3d2 [nfsd]
[<ffffffffa0358365>] nfsd_dispatch+0xec/0x1c7 [nfsd]
[<ffffffffa02e9a94>] svc_process_common+0x2b9/0x4b4 [sunrpc]
[<ffffffffa02e9eae>] svc_process+0x121/0x135 [sunrpc]
[<ffffffffa03588a1>] nfsd+0xf1/0x13a [nfsd]
[<ffffffffa03587b0>] ? nfsd+0x0/0x13a [nfsd]
[<ffffffff81064341>] ? kthread+0x0/0x82
[<ffffffff8100a920>] ? kernel_thread_helper+0x0/0x10
iint_free: readcount: 1
iint_free: writecount: -1
The filesystem fscks clean, so I guess I'll file a Bugzilla report...
More information about the users