Searching NFS Archives
Subsystems (2)
Le Mercredi 11 Janvier 2006 10:15, Al Active a =C3=A9crit=C2=A0:
Quoted 37 lines
Hello Vincent,
Quoted 9 lines · Al Active
Quoted 8 lines · Vincent Roqueta
Le Mardi 10 Janvier 2006 17:23, Al Active a =C3=A9crit :
What are the export options, both on data cluster and NFS-Server Cluster ? Can you test Data Cluster to NFS-Shares Import read write access first ?
Vincent
OK, I checked following:
On the Data-Cluster as NFS-Server exporting the Data:
- Directly on the /Data directory (mounted from the
/dev/drbd0primary) All read and writes possible with OpenOffice2 (OO2)
and Linux's Text Editor (clu1 & root)
/Data/Transfer/: chown clu1:users document.doc /Data/Transfer/: chmod 777 document.doc
/Data/Transfer/: ls -l document.doc
-rwxrwxrwx 1 clu1 users 117762006-01-11 08:48 document.doc- Exports from the Data-Cluster as NFS-Server:
/Data/NFS-Server/ *(rw,root_squash,sync)On the NFS-Client:
- /Export/NFS-Server/Transfer/> ls -l document.doc -rwxrwxrwx 1 clu1 users 117762006-01-11 08:48 document.doc
- mount
192.168.0.174:/Data/NFS-Server on /Export/NFS-Server type nfs
(rw,addr=3D192.168.0.174)
Quoted 8 lines
Editing any plain text document works (local clu1 & root) Editing document.doc with OO2 error message:
General input/output error while
accessing /Export/NFS-Server/Transfer/document.docThis error is true for all Microsoft documents (Word, Excel & Access) that produces the error, even when I open it with OO2 on the NFS-Client directly as well.
That is quite strange...
Which kernel version are you using?
Is there something "special" on machine (cpu, 64bits ...)
Quoted 3 lines
Only if this problem gets solved, I can look further at the Samba share error in the windows network (which will probably also be caused by this error)
True
Quoted 4 lines
Can it be something of an incompatibility between the users of the NFS-Server and NFS-Client, even if clu1 has the same UID: 1001 and member of the same groups on both of the two systems? Why only with the Microsoft Office Data Files?
That should not be the case... and even if there was a problem at this poin= t,
the error must be "permission denied", not "I/O error", which reflect an internal NFS problem.
I suppose you are running nfsv3, can you try with the v4 one? (last versions are much more reliables than v3 ones... )
Also, you should have interresting messages in the /var/log/message on NFS client and/or server
Cordialement,
Vincent
=2D------------------------------------------------------
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
_______________________________________________
NFS maillist - [email protected]
https://lists.sourceforge.net/lists/listinfo/nfs
Quoted 10 lines · Vincent Roqueta
Le Mercredi 11 Janvier 2006 10:15, Al Active a =C3=A9crit :
Quoted 9 lines
Hello Vincent,
Quoted 6 lines · Al Active
Quoted 5 lines · Vincent Roqueta
Le Mardi 10 Janvier 2006 17:23, Al Active a =C3=A9crit :
What are the export options, both on data cluster and NFS-Server Cluster ? Can you test Data Cluster to NFS-Shares Import read wr=
ite
Quoted 9 lines
Quoted 9 lines
Quoted 3 lines
Quoted 3 lines
access first ?
Vincent
OK, I checked following:
On the Data-Cluster as NFS-Server exporting the Data:
- Directly on the /Data directory (mounted from the
/dev/drbd0primar=
y)
Quoted 19 lines
Quoted 19 lines
All read and writes possible with OpenOffice2 (OO2) and Linux's Text Editor (clu1 & root) /Data/Transfer/: chown clu1:users document.doc /Data/Transfer/: chmod 777 document.doc /Data/Transfer/: ls -l document.doc
-rwxrwxrwx 1 clu1 users 117762006-01-11 08:48 document.doc- Exports from the Data-Cluster as NFS-Server:
/Data/NFS-Server/ *(rw,root_squash,sync)On the NFS-Client:
- /Export/NFS-Server/Transfer/> ls -l document.doc -rwxrwxrwx 1 clu1 users 117762006-01-11 08:48 document.doc
- mount
192.168.0.174:/Data/NFS-Server on /Export/NFS-Server type nfs
(rw,addr=3D192.168.0.174)
Quoted 7 lines
Quoted 7 lines
Editing any plain text document works (local clu1 & root) Editing document.doc with OO2 error message:
General input/output error while
accessing /Export/NFS-Server/Transfer/document.docThis error is true for all Microsoft documents (Word, Excel & Access) that produces the error, even when I open it with OO2 on the NFS-Clie=
nt
Quoted 5 lines
Quoted 1 line
directly as well.
=20
That is quite strange...
Which kernel version are you using?
Is there something "special" on machine (cpu, 64bits ...)
I am using Novell's SUSE 10.0 purchased Boxed Version. Kernel:
uname -a
Linux L10... 2.6.13-15-default #1 Tue Sep 13 14:56:15 UTC 2005 x86_64 x86_64 x86_64 GNU/Linux
As you can see it is a standard kernel on a x86_64 system
Quoted 2 lines
=20
Quoted 1 line
Only if this problem gets solved, I can look further at the Samba sha=
re
Quoted 1 line
Quoted 1 line
error in the windows network (which will probably also be caused by t=
his
Quoted 7 lines
Quoted 1 line
error)
=20
True
=20Quoted 3 lines
Can it be something of an incompatibility between the users of the NFS-Server and NFS-Client, even if clu1 has the same UID: 1001 and member of the same groups on both of the two systems? Why only with t=
he
Quoted 3 lines
Quoted 1 line
Microsoft Office Data Files?
=20
That should not be the case... and even if there was a problem at this =
point,
Quoted 1 line
the error must be "permission denied", not "I/O error", which reflect a=
n
Quoted 1 line
internal NFS problem.
I hope it is that simple...
Quoted 2 lines
=20
I suppose you are running nfsv3, can you try with the v4 one? (last ver=
sions
Quoted 2 lines
are much more reliables than v3 ones... )
=20
I am using the one with the above kernel. How do I find out which version it is? From the /var/log/messages I see:
"Using /var/lib/nfs/v4recovery as the NFSv4 state recovery directory"; I take it to be v4 then.
Quoted 1 line
Also, you should have interresting messages in the
/var/log/messageon =
NFS
Quoted 2 lines
client and/or server
=20
No messages on the NFS-Server regarding the problem.
On the Client:
Jan 11 11:40:21 L10 kcheckpass[3207]: Authentication failure for clu1 (invoked by uid 1001)=20 Jan 11 11:41:45 L10 su: (to root) clu1 on /dev/pts/6 Jan 11 11:43:10 L10 syslog-ng[3681]: STATS: dropped 88
The passwords are the same on both machines.
Quoted 2 lines
Cordialement,
Vincent
Regards,
:-)
Al
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log fi= les
for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=3D7637&alloc_id=3D16865&op=3Dclick
_______________________________________________
NFS maillist - [email protected]
https://lists.sourceforge.net/lists/listinfo/nfs
Quoted 7 lines · Al Active
On Wed, 2006-01-11 at 11:40 +0100, Vincent Roqueta wrote:
I am using the one with the above kernel. How do I find out which version it is? From the
/var/log/messagesI see:
"Using/var/lib/nfs/v4recoveryas the NFSv4 state recovery directory"; I take it to be v4 then.
Something else from the messages, when I look at the next line. Can this mean something?
...
Jan 11 10:14:09 L10 kernel: NFSD: Using /var/lib/nfs/v4recovery as the
NFSv4 state recovery directory
Jan 11 10:14:09 L10 kernel:
NFSD: recovery directory /var/lib/nfs/v4recovery doesn't exist
^^^^^^^^^^^^^
Jan 11 10:14:09 L10 kernel: NFSD: starting 90-second grace period...
:-)
Al
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
_______________________________________________
NFS maillist - [email protected]
https://lists.sourceforge.net/lists/listinfo/nfs
Quoted 2 lines · Al Active
Quoted 1 line · Al Active
Won't it be appropriate to also change the Subject line with something related to the problem? Like:
"NFS4 & SUSE 10.0 Boxed Version access rights problem with Windows Files"
- The original will not help with a search on topics in the archives. The original problem of reading the archives has cleared by itself:
[email protected] works now for me too.
:-)
Al
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
_______________________________________________
NFS maillist - [email protected]
https://lists.sourceforge.net/lists/listinfo/nfs
Le Mercredi 11 Janvier 2006 11:51, Al Active a =C3=A9crit=C2=A0:
Quoted 13 lines · Vincent Roqueta
Quoted 12 lines
Le Mercredi 11 Janvier 2006 10:15, Al Active a =C3=A9crit :
Quoted 11 lines
Hello Vincent,
Quoted 8 lines · Al Active
Quoted 7 lines · Vincent Roqueta
Le Mardi 10 Janvier 2006 17:23, Al Active a =C3=A9crit :
What are the export options, both on data cluster and NFS-Server Cluster ? Can you test Data Cluster to NFS-Shares Import read write access first ?
Quoted 7 lines
Quoted 7 lines
Quoted 7 lines
Quoted 1 line
Quoted 1 line
Vincent
OK, I checked following:
On the Data-Cluster as NFS-Server exporting the Data:
- Directly on the /Data directory (mounted from the
/dev/drbd0primar=
y)
Quoted 19 lines
Quoted 19 lines
Quoted 19 lines
All read and writes possible with OpenOffice2 (OO2) and Linux's Text Editor (clu1 & root) /Data/Transfer/: chown clu1:users document.doc /Data/Transfer/: chmod 777 document.doc /Data/Transfer/: ls -l document.doc
-rwxrwxrwx 1 clu1 users 117762006-01-11 08:48 document.doc- Exports from the Data-Cluster as NFS-Server:
/Data/NFS-Server/ *(rw,root_squash,sync)On the NFS-Client:
- /Export/NFS-Server/Transfer/> ls -l document.doc -rwxrwxrwx 1 clu1 users 117762006-01-11 08:48 document.doc
- mount
192.168.0.174:/Data/NFS-Server on /Export/NFS-Server type nfs
(rw,addr=3D192.168.0.174)
Quoted 7 lines
Quoted 7 lines
Quoted 7 lines
Editing any plain text document works (local clu1 & root) Editing document.doc with OO2 error message:
General input/output error while
accessing /Export/NFS-Server/Transfer/document.docThis error is true for all Microsoft documents (Word, Excel & Access) that produces the error, even when I open it with OO2 on the NFS-Clie=
nt
Quoted 6 lines
Quoted 5 lines
Quoted 1 line
directly as well.
That is quite strange...
Which kernel version are you using?
Is there something "special" on machine (cpu, 64bits ...)
Quoted 7 lines
I am using Novell's SUSE 10.0 purchased Boxed Version. Kernel:
uname -a
Linux L10... 2.6.13-15-default #1 Tue Sep 13 14:56:15 UTC 2005x86_64x86_64x86_64GNU/LinuxAs you can see it is a standard kernel on a
x86_64system
The kernel is a 64bits one running on x86_64 using the 32 bits emulation fo= r=20
userland libs, right?
That looks like a fs/compat.c problem we had on the client...
Quoted 9 lines
I am using the one with the above kernel. How do I find out which version it is? From the
/var/log/messagesI see:
"Using/var/lib/nfs/v4recoveryas the NFSv4 state recovery directory"; I take it to be v4 then.Jan 11 10:14:09 L10 kernel: NFSD: Using /var/lib/nfs/v4recovery as the NFSv4 state recovery directory Jan 11 10:14:09 L10 kernel:=20NFSD: recovery directory
/var/lib/nfs/v4recoverydoesn't exist
^^^^^^^^^^^^^
Quoted 1 line
Jan 11 10:14:09 L10 kernel: NFSD: starting 90-second grace period
Well, if you didn't specifie nfs4 at mount time, then you are using the v3,= =20
even if the v4 server have been started at boot time.
Don't worry for this messages.
Can you try to test using the v4 version (exports your /export directory wi= th=20
the fsid=3D0 option and mount -t nfs4 nfs-server:/ /mount/point/ )
Vincent
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
_______________________________________________
NFS maillist - [email protected]
https://lists.sourceforge.net/lists/listinfo/nfs
Quoted 6 lines · Vincent Roqueta
Can you try to test using the v4 version (exports your /export directory with the fsid=0 option and mount -t nfs4 nfs-server:/ /mount/point/ )
Vincent
On the NFS-Server, I did the /etc/exports with fsid=0 option
:: exports ::
/Data/NFS-Server/ *(rw,fsid=0,root_squash,sync)
...
and restarted "rcnfsserver restart" and "exportfs -r"; but I do not know if the fsid=0 is active or not. How can I determine that? nfsstat only delivers v2 & v3 stats for server and client though.
Adding the option nfs4 in the fstab of the NFS-Client in place of the existing 'nfs' on the client initially causes an error with 'mount -a' = "can't read superblock". With the 'nfs' option it still worked.
:: fstab ::
...
192.168.0.124:/Data/NFS-Server /Export/NFS-Server nfs4 defaults 0 0
...
I tried again after a new start of the system with the nfs4 option and now it seems to mount normally. I'm not sure if it is nfs4, because the 'mount' command only shows nfs and nfsstat shows nfs2 & nfs3 as file system.
With nfsstat -c I only see nfs client v2 & v3. How do I get client v4 up and running?
:-)
Al
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
_______________________________________________
NFS maillist - [email protected]
https://lists.sourceforge.net/lists/listinfo/nfs