Summary: | 2.6.2-mm series kernel nfs client cannot report df on mounted share | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Steve Romanow <slestak989> |
Component: | [OLD] Server | Assignee: | x86-kernel (DEPRECATED) <x86-kernel> |
Status: | RESOLVED UPSTREAM | ||
Severity: | normal | CC: | andre.hinrichs, andreas, genone, steel300 |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | x86 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: | strace output of df on my system |
Description
Steve Romanow
2004-01-26 17:13:32 UTC
Some things I've tried: 1) reemerged sys-apps/coreutils-5.0.91-r4, provides df 2) reemerged net-fs/nfs-utils-1.0.6, provides netmount 3) I was running nfs and netmount on client machine (2.4 and 2.6 kernels), Stopped using nfs, just netmount at default runlevel now. Still have access to nfs share. 4) fstab mount options: lol2:/usr/portage/distfiles /usr/portage/distfiles nfs rsize=8192,wsize=81 92,timeo=14,rw,intr lol2:/home/public /home/public nfs rsize=8192,wsize=8192,timeo=14,rw,intr Removed rsize and wsize, remounted, no effect. 5) Untarred coreutils source to poke around and see if I can find error message text. May look in kernel source next. fwiw, I used to have the same problem, it seems to be fixed now. server1/client1 - 2.6.1-mm4 client2/server2 - 2.6.0+other patches cleint3 - 2.4.24pre2+patches I don't know if updating the server to 2.6 fixed it, or if it's just some new utils that fix it (although I appear to be running the same versions as you). see this link from mm, related to statfs64 patch with reiserfs. My exported files system on server is reiserfs. http://www.ussg.iu.edu/hypermail/linux/kernel/0306.1/1633.html Created attachment 25050 [details]
strace output of df on my system
as an update, since I upgraded my server to 2.6.2-mm1, df now works. if the server wasnt busy right id'd reboot and see if its a 2.4 server -> 2.6 client issue. maybe tomorrow. Looks like it really is a problem with 2.4 server and 2.6 client as I still have it (server: grsec-sources-2.4.25, client: mm-sources-2.6.4) I have the same issue with 2.6.3-gentoo-r1 client and 2.4.22-gentoo-r7 server... Maybe its time to go 2.6 on the server. Steve does everything workout ok for you now? yes, everything is well using nfs v3 on both server and client. I should have been more clear. nfs v3 and 2.6* on server and client works well. I'm having the same problem. Client is Gentoo with 2.6.3-gentoo-r1 kernel. Server is SuSE with 2.4.20 kernel. Will install Gentoo on the server as well soon, but... I think it is a bad thing that this is not working. There will be a lot of people with big servers running somewhat 'old' systems. Think about the poor admins forced to upgrade all file servers running NFS just because of this. Has anybody tried 2.6.4 or 2.6.5-rc1? Did anybody notify Andrew Morton about this thread? Hi Andre, As far as I know, no one has contacted upstream maintainer. I have already upgraded my server. So dont really want to take it back to 2.4 to continue. Went as far at one point as to read the df source code (from coreutils ebuild I think). Do some of the newer kernel's fix this? (ie. 2.6.4, or perhaps mm-sources on the client)? It's not fixed in 2.6.5-rc3-mm1. I'm not finding anything upstream on this one. Either it's a known issue (my bet) or we're the first to experience it. Either way, I think we're kind of stuck here. All we can do really is wait for upstream to fix it and send it to linus or andrew. Andrew's been doing lot's of work in the NFS code, so I wouldn't be surprised if this was resolved relatively shortly. This is definitely something that has to be resolved upstream. We've got our hands tied with this one. |