[Lustre-discuss] inode weirdness

[Stuart Midgley]

Evening

The file was created on the same node it was access from.

The error isn't permanent.  When the job crashed, I went and started  
investigating and the file was fine.

No, the file is never unlinked.

How do I go about getting a lustre log?


-- 
Dr Stuart Midgley
sdm900 at gmail.com



On 04/09/2009, at 11:28 PM, Oleg Drokin wrote:

> Hello!
>
> On Sep 4, 2009, at 5:35 AM, Stu Midgley wrote:
>
>> I am having jobs on a cluster client crash.  The job creates a small
>> text file (using cp) and then immediately tries to use it with  
>> another
>> application.  The application fails saying the file doesn't exist.
>
> That's quite strange for such a sequence of actions.
> Is the file created on one node and accessed on another?
> How permanent is the error ? (i.e. does it still happen when you  
> later access the file again?)
> Is the file unlinked at any time, could there be a race with unlink  
> by any chance?
>
>> In the client /var/log/messages, I'm seeing
>> Sep  4 15:58:17 clus039 kernel: LustreError:
>> 15249:0:(file.c:2930:ll_inode_revalidate_fini()) failure -2 inode
>> 75792903
>
> There is bug 16377 about this same message, though it is not clear  
> what happened there.
> Perhaps you can gather -1 lustre logs from mds and a client that  
> creates
> and client that accesses this file and gets an error and attach  
> those to the bug 16377?
>
> Bye,
>    Oleg