Re: Funny NFS
Hello Dave, Am 2003-09-22 12:09:10, schrieb Dave: Hi Guys, I recently upgraded from 2.4.18 to 2.4.20 but am getting strange errors(?) whenever I log onto the box now. I loaded the 2.4.18 config with the 2.4.20 source and compiled like that, so I'm sure I never left anything out. [EMAIL PROTECTED]'s password: Last login: Mon Sep 22 09:04:05 2003 from 192.168.11.2 on pts/1 Linux valhalla 2.4.20-valhalla #1 Thu Sep 18 08:21:07 SAST 2003 i686 unknown struct nfs_fh * fh; const char *name; unsigned intle I think, this is a Filesystem-Error because: /usr/src/linux/include/linux/nfs_xdr.h struct nfs_diropargs { struct nfs_fh * fh; const char *name; unsigned intlen; }; struct nfs_createargs { struct nfs_fh * fh; const char *name; unsigned intlen; struct iattr * sattr; }; struct nfs3_createargs { struct nfs_fh * fh; const char *name; unsigned intlen; struct iattr * sattr; enum nfs3_createmodecreatemode; __u32 verifier[2]; }; struct nfs3_mkdirargs { struct nfs_fh * fh; const char *name; unsigned intlen; struct iattr * sattr; }; struct nfs3_mknodargs { struct nfs_fh * fh; const char *name; unsigned intlen; enum nfs3_ftype type; struct iattr * sattr; dev_t rdev; }; Thanks, Dave Greetings from Strasbourg Michelle -- Registered Linux-User #280138 with the Linux Counter, http://counter.li.org. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Funny NFS
Not that I have experienced anything like this before. But it looks as if parts of the kernel source code were in some way corrupted. Otherwise it's difficult to see why that definition would show up. Michael Dave wrote: Hi Guys, I recently upgraded from 2.4.18 to 2.4.20 but am getting strange errors(?) whenever I log onto the box now. I loaded the 2.4.18 config with the 2.4.20 source and compiled like that, so I'm sure I never left anything out. [EMAIL PROTECTED]'s password: Last login: Mon Sep 22 09:04:05 2003 from 192.168.11.2 on pts/1 Linux valhalla 2.4.20-valhalla #1 Thu Sep 18 08:21:07 SAST 2003 i686 unknown struct nfs_fh * fh; const char *name; unsigned intle Last login: Mon Sep 22 09:04:05 2003 from 192.168.11.2 valhalla:~# Been looking online for similar problems but just getting results of OLD NFS bugs. Everything on this box is running fine however. Any help would be greatly appreciated. Thanks, Dave -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Funny NFS
On Mon, 2003-09-22 at 06:09, Dave wrote: [EMAIL PROTECTED]'s password: Last login: Mon Sep 22 09:04:05 2003 from 192.168.11.2 on pts/1 Linux valhalla 2.4.20-valhalla #1 Thu Sep 18 08:21:07 SAST 2003 i686 unknown struct nfs_fh * fh; const char *name; unsigned intle Last login: Mon Sep 22 09:04:05 2003 from 192.168.11.2 valhalla:~# The first thing I would do is login to an account w/o any startup script commands, e.g. biff, setting permission on the tty, umask changes. If you still get the message I would consider starting a login shell of your new, clean account under stace with the follow child PIDs option, and output each child's syscall messages to its own soandso.PID file. You can use *grep to figure out where that output is coming from. I doubt that you have a kernel problem but I suppose it is feasable. It would be better to check other options first. Incidentally I am running 2.4.20 on my home NFS server and have no similar problems. I have not upgraded to 2.4.20 on any of my NFS clients yet. -- Jeff S Wheeler -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Funny NFS
On Mon, 22 Sep 2003 20:09, Dave wrote: I recently upgraded from 2.4.18 to 2.4.20 but am getting strange errors(?) whenever I log onto the box now. I loaded the 2.4.18 config with the 2.4.20 source and compiled like that, so I'm sure I never left anything out. [EMAIL PROTECTED]'s password: Last login: Mon Sep 22 09:04:05 2003 from 192.168.11.2 on pts/1 Linux valhalla 2.4.20-valhalla #1 Thu Sep 18 08:21:07 SAST 2003 i686 unknown struct nfs_fh * fh; Did a file system error over-write /etc/motd with some kernel source? -- http://www.coker.com.au/selinux/ My NSA Security Enhanced Linux packages http://www.coker.com.au/bonnie++/ Bonnie++ hard drive benchmark http://www.coker.com.au/postal/Postal SMTP/POP benchmark http://www.coker.com.au/~russell/ My home page -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
RE: Funny NFS
Thanks! I have NO idea why the motd was overwritten, can't believe it. Must be the lag or something, not sure. I tried checking my kernel config over and over and everything looked peachy. Strange. Thanks again for all the help guys, will let you know when I find out what the hell caused this. Dave -Original Message- From: Russell Coker [mailto:[EMAIL PROTECTED] Sent: 22 September 2003 04:04 To: Dave; Debian-ISP Subject: Re: Funny NFS On Mon, 22 Sep 2003 20:09, Dave wrote: I recently upgraded from 2.4.18 to 2.4.20 but am getting strange errors(?) whenever I log onto the box now. I loaded the 2.4.18 config with the 2.4.20 source and compiled like that, so I'm sure I never left anything out. [EMAIL PROTECTED]'s password: Last login: Mon Sep 22 09:04:05 2003 from 192.168.11.2 on pts/1 Linux valhalla 2.4.20-valhalla #1 Thu Sep 18 08:21:07 SAST 2003 i686 unknown struct nfs_fh * fh; Did a file system error over-write /etc/motd with some kernel source? -- http://www.coker.com.au/selinux/ My NSA Security Enhanced Linux packages http://www.coker.com.au/bonnie++/ Bonnie++ hard drive benchmark http://www.coker.com.au/postal/Postal SMTP/POP benchmark http://www.coker.com.au/~russell/ My home page -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]