[Ocfs2-devel] add error check for ocfs2_read_locked_inode() call

[Sunil Mushran]

Joel Becker wrote:
> On Wed, May 13, 2009 at 09:44:57PM +0300, Oleg Gawriloff wrote:
>> Joel Becker пишет:
>>> 	There's no other error messages?  Can you give us a larger
>>> snippet of the log?
>> Here:
>> May 13 19:51:18 falcon-cl5
>> May 13 19:51:18 falcon-cl5 (8824,2):ocfs2_read_locked_inode:466 ERROR: 
>> status = -22
>
> 	This is really weird.  Like Sunil, I looked at the code.  And
> every place that can set status to -EINVAL (-22) has its own ERROR
> message.  So you should be seeing those.
>
> Joel

Exactly. Also, this could be related to that volume going read-only.
But if so, you will atleast see the following message:

        printk(KERN_CRIT "File system is now read-only due to the 
potential "
               "of on-disk corruption. Please run fsck.ocfs2 once the file "
               "system is unmounted.\n");

If the code is the same, then it could be that the difference is in the 
build.
But what, how, I cannot say.

BTW, maybe a good idea to fsck your volumes.

Sunil