I've a strange issue with an NFS mount on a F13-Beta.
The nfs server is a RHELv4 system. The exports contains....
/home/egreshko 192.168.0.0/255.255.255.0(rw,sync,fsid=0,nohide)
This is mounted just fine on a F11 system whose fstab contains...
misty:/ /home/egreshko/misty nfs4 rw
On the F13 system the fstab contains....
192.168.0.55:/ /media/test nfs4 rw
Now the weirdness, on the F13 system....
[egreshko@f13 media]$ ls -l total 12 drwx------. 170 nobody nobody 8192 Apr 25 10:22 test
[egreshko@f13 media]$ ls -n total 12 drwx------. 170 99 99 8192 Apr 25 10:22 test
[egreshko@f13 media]$ touch test/x [egreshko@f13 media]$ ll test/x -rw-rw-r--. 1 nobody nobody 0 Apr 25 10:23 test/x
[egreshko@f13 media]$ ls -n test/x -rw-rw-r--. 1 99 99 0 Apr 25 10:23 test/x
If I go to the RHELv4 system or the F11 system I see....
[egreshko@meimei misty]$ ll x -rw-rw-r--. 1 egreshko egreshko 0 2010-04-25 10:23 x
[egreshko@meimei misty]$ ls -n x -rw-rw-r--. 1 500 500 0 2010-04-25 10:23 x
I'm thinking it must be related to the idmapd process.... I find it strange that the log file shows....
rpc.idmapd[3376]: nss_getpwnam: name 'egreshko@localdomain' does not map into domain 'greshko.com'
when.... [root@f13 etc]# hostname f13.greshko.com [root@f13 etc]# host f13.greshko.com f13.greshko.com has address 192.168.0.196
and the idmapd.conf contains....
Domain = greshko.com
Since this works fine on F11, and I'm pretty sure it worked just fine when testing on F12, it would seem to be something with F13....unless I'm missing something.
On Mon, 26 Apr 2010 06:51:06 +0800 Ed Greshko wrote:
Since this works fine on F11, and I'm pretty sure it worked just fine when testing on F12, it would seem to be something with F13....unless I'm missing something.
Do you use NIS or ldap or something so that user information is available on all the systems? I think nobody is what you get when it can't identify an NFS user (maybe :-).
On 04/26/2010 07:10 AM, Tom Horsley wrote:
On Mon, 26 Apr 2010 06:51:06 +0800 Ed Greshko wrote:
Since this works fine on F11, and I'm pretty sure it worked just fine when testing on F12, it would seem to be something with F13....unless I'm missing something.
Do you use NIS or ldap or something so that user information is available on all the systems? I think nobody is what you get when it can't identify an NFS user (maybe :-).
No ldap or NIS.... Plain F13 install.
On Sun, Apr 25, 2010 at 6:51 PM, Ed Greshko Ed.Greshko@greshko.com wrote:
I've a strange issue with an NFS mount on a F13-Beta.
The nfs server is a RHELv4 system. The exports contains.... /home/egreshko 192.168.0.0/255.255.255.0(rw,sync,fsid=0,nohide)
This is mounted just fine on a F11 system whose fstab contains... misty:/ /home/egreshko/misty nfs4 rw
On the F13 system the fstab contains.... 192.168.0.55:/ /media/test nfs4 rw
Now the weirdness, on the F13 system....
[egreshko@f13 media]$ ls -l total 12 drwx------. 170 nobody nobody 8192 Apr 25 10:22 test
[egreshko@f13 media]$ ls -n total 12 drwx------. 170 99 99 8192 Apr 25 10:22 test
[egreshko@f13 media]$ touch test/x [egreshko@f13 media]$ ll test/x -rw-rw-r--. 1 nobody nobody 0 Apr 25 10:23 test/x
[egreshko@f13 media]$ ls -n test/x -rw-rw-r--. 1 99 99 0 Apr 25 10:23 test/x
If I go to the RHELv4 system or the F11 system I see....
[egreshko@meimei misty]$ ll x -rw-rw-r--. 1 egreshko egreshko 0 2010-04-25 10:23 x
[egreshko@meimei misty]$ ls -n x -rw-rw-r--. 1 500 500 0 2010-04-25 10:23 x
I'm thinking it must be related to the idmapd process.... I find it strange that the log file shows....
rpc.idmapd[3376]: nss_getpwnam: name 'egreshko@localdomain' does not map into domain 'greshko.com'
when.... [root@f13 etc]# hostname f13.greshko.com [root@f13 etc]# host f13.greshko.com f13.greshko.com has address 192.168.0.196
and the idmapd.conf contains.... Domain = greshko.com
Since this works fine on F11, and I'm pretty sure it worked just fine when testing on F12, it would seem to be something with F13....unless I'm missing something.
Is rpc.idmapd running on the F13 box?
On 04/27/2010 03:43 AM, Tom H wrote:
On Sun, Apr 25, 2010 at 6:51 PM, Ed Greshko Ed.Greshko@greshko.com wrote:
I've a strange issue with an NFS mount on a F13-Beta.
The nfs server is a RHELv4 system. The exports contains.... /home/egreshko 192.168.0.0/255.255.255.0(rw,sync,fsid=0,nohide)
This is mounted just fine on a F11 system whose fstab contains... misty:/ /home/egreshko/misty nfs4 rw
On the F13 system the fstab contains.... 192.168.0.55:/ /media/test nfs4 rw
Now the weirdness, on the F13 system....
[egreshko@f13 media]$ ls -l total 12 drwx------. 170 nobody nobody 8192 Apr 25 10:22 test
[egreshko@f13 media]$ ls -n total 12 drwx------. 170 99 99 8192 Apr 25 10:22 test
[egreshko@f13 media]$ touch test/x [egreshko@f13 media]$ ll test/x -rw-rw-r--. 1 nobody nobody 0 Apr 25 10:23 test/x
[egreshko@f13 media]$ ls -n test/x -rw-rw-r--. 1 99 99 0 Apr 25 10:23 test/x
If I go to the RHELv4 system or the F11 system I see....
[egreshko@meimei misty]$ ll x -rw-rw-r--. 1 egreshko egreshko 0 2010-04-25 10:23 x
[egreshko@meimei misty]$ ls -n x -rw-rw-r--. 1 500 500 0 2010-04-25 10:23 x
I'm thinking it must be related to the idmapd process.... I find it strange that the log file shows....
rpc.idmapd[3376]: nss_getpwnam: name 'egreshko@localdomain' does not map into domain 'greshko.com'
when.... [root@f13 etc]# hostname f13.greshko.com [root@f13 etc]# host f13.greshko.com f13.greshko.com has address 192.168.0.196
and the idmapd.conf contains.... Domain = greshko.com
Since this works fine on F11, and I'm pretty sure it worked just fine when testing on F12, it would seem to be something with F13....unless I'm missing something.
Is rpc.idmapd running on the F13 box?
Yes... Didn't you see the log entry that I posted above, that comes from rpc.imapd?
On Mon, Apr 26, 2010 at 7:32 PM, Ed Greshko Ed.Greshko@greshko.com wrote:
On 04/27/2010 03:43 AM, Tom H wrote:
On Sun, Apr 25, 2010 at 6:51 PM, Ed Greshko Ed.Greshko@greshko.com wrote:
I've a strange issue with an NFS mount on a F13-Beta.
The nfs server is a RHELv4 system. The exports contains.... /home/egreshko 192.168.0.0/255.255.255.0(rw,sync,fsid=0,nohide)
This is mounted just fine on a F11 system whose fstab contains... misty:/ /home/egreshko/misty nfs4 rw
On the F13 system the fstab contains.... 192.168.0.55:/ /media/test nfs4 rw
Now the weirdness, on the F13 system....
[egreshko@f13 media]$ ls -l total 12 drwx------. 170 nobody nobody 8192 Apr 25 10:22 test
[egreshko@f13 media]$ ls -n total 12 drwx------. 170 99 99 8192 Apr 25 10:22 test
[egreshko@f13 media]$ touch test/x [egreshko@f13 media]$ ll test/x -rw-rw-r--. 1 nobody nobody 0 Apr 25 10:23 test/x
[egreshko@f13 media]$ ls -n test/x -rw-rw-r--. 1 99 99 0 Apr 25 10:23 test/x
If I go to the RHELv4 system or the F11 system I see....
[egreshko@meimei misty]$ ll x -rw-rw-r--. 1 egreshko egreshko 0 2010-04-25 10:23 x
[egreshko@meimei misty]$ ls -n x -rw-rw-r--. 1 500 500 0 2010-04-25 10:23 x
I'm thinking it must be related to the idmapd process.... I find it strange that the log file shows....
rpc.idmapd[3376]: nss_getpwnam: name 'egreshko@localdomain' does not map into domain 'greshko.com'
when.... [root@f13 etc]# hostname f13.greshko.com [root@f13 etc]# host f13.greshko.com f13.greshko.com has address 192.168.0.196
and the idmapd.conf contains.... Domain = greshko.com
Since this works fine on F11, and I'm pretty sure it worked just fine when testing on F12, it would seem to be something with F13....unless I'm missing something.
Is rpc.idmapd running on the F13 box?
Yes... Didn't you see the log entry that I posted above, that comes from rpc.imapd?
Thought that it came from the RHEL server not the F13 client.
On 04/27/2010 12:44 PM, Tom H wrote:
On Mon, Apr 26, 2010 at 7:32 PM, Ed Greshko Ed.Greshko@greshko.com wrote:
On 04/27/2010 03:43 AM, Tom H wrote:
On Sun, Apr 25, 2010 at 6:51 PM, Ed Greshko Ed.Greshko@greshko.com wrote:
I've a strange issue with an NFS mount on a F13-Beta.
The nfs server is a RHELv4 system. The exports contains.... /home/egreshko 192.168.0.0/255.255.255.0(rw,sync,fsid=0,nohide)
This is mounted just fine on a F11 system whose fstab contains... misty:/ /home/egreshko/misty nfs4 rw
On the F13 system the fstab contains.... 192.168.0.55:/ /media/test nfs4 rw
Now the weirdness, on the F13 system....
[egreshko@f13 media]$ ls -l total 12 drwx------. 170 nobody nobody 8192 Apr 25 10:22 test
[egreshko@f13 media]$ ls -n total 12 drwx------. 170 99 99 8192 Apr 25 10:22 test
[egreshko@f13 media]$ touch test/x [egreshko@f13 media]$ ll test/x -rw-rw-r--. 1 nobody nobody 0 Apr 25 10:23 test/x
[egreshko@f13 media]$ ls -n test/x -rw-rw-r--. 1 99 99 0 Apr 25 10:23 test/x
If I go to the RHELv4 system or the F11 system I see....
[egreshko@meimei misty]$ ll x -rw-rw-r--. 1 egreshko egreshko 0 2010-04-25 10:23 x
[egreshko@meimei misty]$ ls -n x -rw-rw-r--. 1 500 500 0 2010-04-25 10:23 x
I'm thinking it must be related to the idmapd process.... I find it strange that the log file shows....
rpc.idmapd[3376]: nss_getpwnam: name 'egreshko@localdomain' does not map into domain 'greshko.com'
when.... [root@f13 etc]# hostname f13.greshko.com [root@f13 etc]# host f13.greshko.com f13.greshko.com has address 192.168.0.196
and the idmapd.conf contains.... Domain = greshko.com
Since this works fine on F11, and I'm pretty sure it worked just fine when testing on F12, it would seem to be something with F13....unless I'm missing something.
Is rpc.idmapd running on the F13 box?
Yes... Didn't you see the log entry that I posted above, that comes from rpc.imapd?
Thought that it came from the RHEL server not the F13 client.
It is the client.... If idmap isn't running the result on the client side is....
drwx------. 170 4294967294 4294967294 8192 Apr 26 08:11 test
Looks like not many folks are testing NFS....or this problem is strange or related to the RHELv4 server.
On 04/27/2010 05:02 AM, Ed Greshko wrote:
Looks like not many folks are testing NFS....or this problem is strange or related to the RHELv4 server.
Well we did hold a test day https://fedoraproject.org/wiki/Test_Day:2010-02-04_NFS
We can always do better with an extra hand and all ideas about improving our tests and adding more test cases are well appreciated.
JBG
On 04/27/2010 01:02 PM, Ed Greshko wrote:
It is the client.... If idmap isn't running the result on the client side is....
drwx------. 170 4294967294 4294967294 8192 Apr 26 08:11 test
Looks like not many folks are testing NFS....or this problem is strange or related to the RHELv4 server.
As Emily Litella would say...."Never mind".
Someone had rolled back the rhelv4 server to a previous snapshot where the idmapd.conf hadn't been modified correctly. I made the common mistake of assuming....
On Tue, Apr 27, 2010 at 1:02 AM, Ed Greshko Ed.Greshko@greshko.com wrote:
On 04/27/2010 12:44 PM, Tom H wrote:
On Mon, Apr 26, 2010 at 7:32 PM, Ed Greshko Ed.Greshko@greshko.com wrote:
On 04/27/2010 03:43 AM, Tom H wrote:
On Sun, Apr 25, 2010 at 6:51 PM, Ed Greshko Ed.Greshko@greshko.com wrote:
Is rpc.idmapd running on the F13 box?
Yes... Didn't you see the log entry that I posted above, that comes from rpc.imapd?
Thought that it came from the RHEL server not the F13 client.
It is the client.... If idmap isn't running the result on the client side is.... drwx------. 170 4294967294 4294967294 8192 Apr 26 08:11 test
I thought that it might not be because of the "localdomain" in the idmapd log.
Anyway, you were screwed by a colleague; it's happened to all of us. :)
Ed Greshko wrote:
On 04/27/2010 12:44 PM, Tom H wrote:
On Mon, Apr 26, 2010 at 7:32 PM, Ed Greshko Ed.Greshko@greshko.com wrote:
On 04/27/2010 03:43 AM, Tom H wrote:
On Sun, Apr 25, 2010 at 6:51 PM, Ed Greshko Ed.Greshko@greshko.com wrote:
I've a strange issue with an NFS mount on a F13-Beta.
The nfs server is a RHELv4 system. The exports contains.... /home/egreshko 192.168.0.0/255.255.255.0(rw,sync,fsid=0,nohide)
This is mounted just fine on a F11 system whose fstab contains... misty:/ /home/egreshko/misty nfs4 rw
On the F13 system the fstab contains.... 192.168.0.55:/ /media/test nfs4 rw
Now the weirdness, on the F13 system....
[egreshko@f13 media]$ ls -l total 12 drwx------. 170 nobody nobody 8192 Apr 25 10:22 test
[egreshko@f13 media]$ ls -n total 12 drwx------. 170 99 99 8192 Apr 25 10:22 test
[egreshko@f13 media]$ touch test/x [egreshko@f13 media]$ ll test/x -rw-rw-r--. 1 nobody nobody 0 Apr 25 10:23 test/x
[egreshko@f13 media]$ ls -n test/x -rw-rw-r--. 1 99 99 0 Apr 25 10:23 test/x
If I go to the RHELv4 system or the F11 system I see....
[egreshko@meimei misty]$ ll x -rw-rw-r--. 1 egreshko egreshko 0 2010-04-25 10:23 x
[egreshko@meimei misty]$ ls -n x -rw-rw-r--. 1 500 500 0 2010-04-25 10:23 x
I'm thinking it must be related to the idmapd process.... I find it strange that the log file shows....
rpc.idmapd[3376]: nss_getpwnam: name 'egreshko@localdomain' does not map into domain 'greshko.com'
when.... [root@f13 etc]# hostname f13.greshko.com [root@f13 etc]# host f13.greshko.com f13.greshko.com has address 192.168.0.196
and the idmapd.conf contains.... Domain = greshko.com
Since this works fine on F11, and I'm pretty sure it worked just fine when testing on F12, it would seem to be something with F13....unless I'm missing something.
Is rpc.idmapd running on the F13 box?
Yes... Didn't you see the log entry that I posted above, that comes from rpc.imapd?
Thought that it came from the RHEL server not the F13 client.
It is the client.... If idmap isn't running the result on the client side is....
drwx------. 170 4294967294 4294967294 8192 Apr 26 08:11 test
Looks like not many folks are testing NFS....or this problem is strange or related to the RHELv4 server.
Either that or not bothering to report bugs. Given the response to the FC[6,9,10,11} NFS bug I reported just being marked WONTFIX, I only report new and serious NFS breakage in FC13, I assume the old bugs aren't of interest.
On Mon, 2010-05-03 at 15:13 -0400, Bill Davidsen wrote:
Either that or not bothering to report bugs. Given the response to the FC[6,9,10,11} NFS bug I reported just being marked WONTFIX, I only report new and serious NFS breakage in FC13, I assume the old bugs aren't of interest.
The comment posted to the bug when it was closed explained clearly why: F11 is end-of-life. All bugs on a release are closed when it goes end-of-life, and Fedora releases go end-of-life 12 months after they're released.