AF:
NF:0
PS:10
SRH:1
SFN:
DSR:
MID:<20090219130531.79d3d3ce@ripper.onstor.net>
CFG:
PT:0
S:andy.sharp@onstor.com
RQ:
SSV:exch1.onstor.net
NSV:
SSH:
R:<otrs@onstor.com>
MAID:1
X-Sylpheed-Privacy-System:
X-Sylpheed-Sign:0
SCF:#mh/Mailbox/sent
RMID:#imap/andys@onstor.net@exch1.onstor.net/INBOX	0	1235076557.719620.210808885.241.2@helpdesk.onstor.net
X-Sylpheed-End-Special-Headers: 1
Date: Thu, 19 Feb 2009 13:06:06 -0800
From: Andrew Sharp <andy.sharp@onstor.com>
To: ONStor Ticket Request System OTRS <otrs@onstor.com>
Subject: Re: [Ticket#10232] conti [...]
Message-ID: <20090219130606.51339a09@ripper.onstor.net>
In-Reply-To: <1235076557.719620.210808885.241.2@helpdesk.onstor.net>
References: <1235076557.719620.210808885.241.2@helpdesk.onstor.net>
Organization: Onstor
X-Mailer: Sylpheed-Claws 2.6.0 (GTK+ 2.8.20; x86_64-pc-linux-gnu)
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit

On Thu, 19 Feb 2009 12:49:17 -0800 ONStor Ticket Request System OTRS
<otrs@onstor.com> wrote:

> Dear Andy Sharp,
> 
> Thank you for your request.
> 02/19/2009 11:40 - OTRS System wrote:
> 
> > There is an update to your Ticket.
> > 
> > > On Thu, 19 Feb 2009 11:20:50 -0800 ONStor Ticket Request System
> > > OTRS <otrs@onstor.com> wrote:
> > > 
> > > > Dear Andy Sharp,
> > > > 
> > > > Thank you for your request.
> > > > 02/19/2009 11:20 - John Rogers wrote:
> > > > 
> > > > > Are there time stamps associated with those events at all?
> > > 
> > > I'll paste from the log file, but remember that since it's NFS
> > > root, the "not responding" time stamps won't necessarily be
> > > completely accurate.
> > > 
> > > 
> > > Feb 19 00:29:05 tuxrx0 kernel: nfs: server 10.0.0.42 not
> > > responding, still trying Feb 19 00:29:38 tuxrx0 kernel: nfs:
> > > server 10.0.0.42 not responding, still trying Feb 19 00:29:38
> > > tuxrx0 last message repeated 2 times Feb 19 00:29:38 tuxrx0
> > > kernel: nfs: server 10.0.0.42 OK Feb 19 00:29:38 tuxrx0 last
> > > message repeated 3 times Feb 19 00:56:39 tuxrx0 -- MARK --
> > > 
> > > 
> > > Feb 19 04:11:32 tuxrx0 kernel: nfs: server 10.0.0.42 not
> > > responding, still trying Feb 19 04:24:07 tuxrx0 kernel: nfs:
> > > server 10.0.0.42 not responding, still trying Feb 19 04:24:07
> > > tuxrx0 last message repeated 8 times Feb 19 04:24:07 tuxrx0
> > > kernel: nfs: server 10.0.0.42 OK Feb 19 04:24:07 tuxrx0 last
> > > message repeated 9 times
> > > 
> > > Feb 19 10:44:01 tuxrx0 kernel: nfs: server 10.0.0.42 not
> > > responding, still trying Feb 19 10:48:31 tuxrx0 kernel: nfs:
> > > server 10.0.0.42 not responding, still trying Feb 19 10:48:31
> > > tuxrx0 last message repeated 7 times Feb 19 10:48:31 tuxrx0
> > > kernel: nfs: server 10.0.0.42 OK Feb 19 10:48:31 tuxrx0 last
> > > message repeated 8 times Feb 19 11:13:32 tuxrx0 -- MARK --
> > > Feb 19 11:22:50 tuxrx0 kernel: nfs: server 10.0.0.42 not
> > > responding, still trying Feb 19 11:22:50 tuxrx0 last message
> > > repeated 10 times Feb 19 11:22:50 tuxrx0 kernel: nfs: server
> > > 10.0.0.42 OK Feb 19 11:22:50 tuxrx0 last message repeated 10 times
> > > 
> 
> Maybe its a bonehead question, but have your peeked at the logs on
> ripper to see if there is any trouble on that nfs server. It seems
> like it may be a moderately loaded nfs server, perhaps there is a
> problem there?

ripper is my workstation, so, no, it has zero load.
