[Lustre-discuss] Client hangs when reading from Lustre ...

[Andreas Dilger]

On Feb 04, 2008  15:47 -0800, Klaus Steden wrote:
> Thanks Andreas ... That would make sense, although the only error message
> (or, message vaguely resembling an error message) that I could find was this
> one:
> 
> -- cut --
> /var/log/messages.1:Feb  1 09:28:09 tiger-oss-0-0 kernel: LDISKFS-fs error
> (device sdb): ldiskfs_journal_start_sb: Detected aborted journal
> -- cut --
> 
> I'm assuming that's causing the problem -- but what's the next step? Punt
> all the clients, stop Lustre, and run e2fsck on the affected device?

Yes.  An aborted journal means an error at the journal layer...  Maybe with
a "JBD" error message?

> On 2/4/08 3:22 PM, "Andreas Dilger" <adilger at Sun.COM>did etch on stone
> tablets:
> 
> > On Feb 04, 2008  13:54 -0800, Klaus Steden wrote:
> >> I'm trying to figure out something odd ... a node in my cluster hangs when I
> >> run 'df', or 'find -exec file {}' or other commands like that.
> >> 
> >> No other clients in the cluster exhibit the same behaviour. I'm seeing a lot
> >> of messages like this in its syslog:
> >> 
> >> -- cut --
> >> Feb  4 13:51:37 tiger-0-6 kernel: LustreError:
> >> 5827:0:(client.c:576:ptlrpc_check_status()) @@@ type == PTL_RPC_MSG_ERR, err
> >> == -30 req at 000001010d30e400 x9218/t0
> >> o8->ost1_UUID at tiger-oss-0-0.local_UUID:6 lens 240/272 ref 1 fl Rpc:R/0/40000
> >> rc 0/-30
> >> -- cut --
> > 
> > /usr/include/asm/errno.h says -30 = -EROFS.  That means your OST filesystem
> > has likely been remounted read-only because of a detected filesystem error.
> > Check your /var/log/messages for something like "LDISKFS-fs error ...:
> > Remounting filesystem read-only".  This will be accompanied by the reason
> > the filesystem is read-only.
> > 
> > Cheers, Andreas
> > --
> > Andreas Dilger
> > Sr. Staff Engineer, Lustre Group
> > Sun Microsystems of Canada, Inc.
> > 

Cheers, Andreas
--
Andreas Dilger
Sr. Staff Engineer, Lustre Group
Sun Microsystems of Canada, Inc.