Re: [Jfs-discussion] read-only after diRead: i_ino != di_number

[Sonny R. <so...@bu...>]

On Mon, Jul 10, 2006 at 01:34:05PM -0700, Alex Lisker wrote:
> Dear jfs heads
> 
> Recently i've been unfortunate to experience the following problem with JFS.
> Periodically, but at irregular intervals, my jfs partition would remount
> itself as read-only after about a dozen of these messages seen in dmesg:
> 
> 	ERROR: (device sdc): diRead: i_ino != di_number
> 
> I can't decisively tell what i'm doing wrong, hence i request your expertize.
> Let me tell you about the environment.
> 
> The head node is a Xeon 3.40GHz running a fedora core 4's latest kernel -
> 2.6.17-1.2141_FC4smp.  (I installed the kernel 2 days ago to replace a much older
> 2.6.11-1.1369_FC4smp, however the inode problem persisted.)

Is this a SMP system/kernel?  I know that various locking fixes have
gone in recently, but this may be entirely unrelated.

i_ino != di_number implies that the on_disk inode number doesn't match
up with the inode-extent that it resides in.  Basically, we're having
to read an inode in from disk and sanity checking is triggering this
warning and rejecting that on-disk inode.

It would be interesting to know how far off the two numbers
are.. i.e. are we talking about one or two bits or just complete
garbage.  Debugfs would let us do that if we knew which inode numbers
were triggering this message.