Hi,
the issue is, i'm in the filerteam, an the sunteam calls me and says, we've got write errors and mount problems. So it's my turn. I make a test mount and say, everything is all right. But now we need a statement, whats the reason for the standing databases...
so i wanna see, what the filer says on the times, the sunserver got problems. I don't can run commands on the sun side, but i've become a logfile form the sunteam:
Aug 22 19:20:46 rd2c03 nfs: [ID 277861 kern.notice] NFS write error on host erpvfiler: error 145. Aug 22 19:20:46 rd2c03 nfs: [ID 702911 kern.notice] (file handle: 22018100 bcf22707 20080000 17bf48b 62c93907 7a7133b9 40000000 70a27100) Aug 22 19:20:46 rd2c03 nfs: [ID 664466 kern.notice] NFS write failed for server erpvfiler: error 5 (RPC: Timed out) Aug 22 19:20:46 rd2c03 last message repeated 2 times Aug 22 19:20:46 rd2c03 nfs: [ID 277861 kern.notice] NFS write error on host erpvfiler: error 145. Aug 22 19:20:46 rd2c03 last message repeated 2 times Aug 22 19:20:46 rd2c03 nfs: [ID 702911 kern.notice] (file handle: 22018100 bcf22707 20080000 17bf48b 62c93907 7a7133b9 40000000 70a27100) Aug 22 19:20:46 rd2c03 last message repeated 2 times Aug 22 19:20:46 rd2c03 nfs: [ID 664466 kern.notice] NFS write failed for server erpvfiler: error 5 (RPC: Timed out) Aug 22 19:20:46 rd2c03 last message repeated 1 time Aug 22 19:20:46 rd2c03 nfs: [ID 277861 kern.notice] NFS write error on host erpvfiler: error 145. Aug 22 19:20:46 rd2c03 nfs: [ID 664466 kern.notice] NFS write failed for server erpvfiler: error 5 (RPC: Timed out) Aug 22 19:20:46 rd2c03 nfs: [ID 277861 kern.notice] NFS write error on host erpvfiler: error 145.
if nothing matches in the /etc/log/ems, is it right when i say: It's not a filer problem?
greetings
Philipp
-----Ursprüngliche Nachricht----- Von: Buerger, Andreas [mailto:andreas.buerger@wincor-nixdorf.com] Gesendet: Freitag, 24. August 2007 11:40 An: Zeitschel, Philipp; toasters@mathworks.com Betreff: RE: nfs logging / debugging
Hi,
Whats your detailed problem with NFS?
Yes, the nfs.mountd.trace option is logging into /etc/log/ems. There should be also some additional output on the console and to /etc/messages with that option. I don't know if there's any tool to view the ems log, another thing you can do is to create some traces with pktt. You can view these traces and watch for the client you have problems with. Perhaps nfsstat -d can help you, too.
bye andreas ________________________________
From: owner-toasters@mathworks.com [mailto:owner-toasters@mathworks.com] On Behalf Of Zeitschel, Philipp Sent: Friday, August 24, 2007 10:01 AM To: toasters@mathworks.com Subject: nfs logging / debugging
Hi,
I'm new to this list, and my english is not very well...
i've got some nfs problems, so i wan't to read some log's. With the option nfs.mountd.trace on the filer logs some stuff to /etc/log/ems, is that right?
the ems log, looks like some pseudo xml, is there a special tool to analyze the file?
are there other possibilitys to debug nfs on the filer?
NetApp Release 7.2.3
greeting
Philipp