bad inode number followed by ext3_abort and remount readonly

[Theodore Ts'o]

On Wed, Jun 15, 2005 at 12:13:34PM -0500, Joseph D. Wagner wrote:
> > The only other possible explanation I can imagine, beyond a
> > hardware problem
> 
> Just off the top of my head, could the number be reaching its limit
> and rolling over somehow?

The inode number?  No.

					- Ted