bad inode number followed by ext3_abort and remount readonly

[Theodore Ts'o]

On Wed, Jun 15, 2005 at 01:22:05PM -0400, 'Andreas Dilger' wrote:
> On Jun 15, 2005  12:13 -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?
> 
> Seems unlikely, as it isn't very easy to create a filesystem that uses
> 4B inodes.  Would have to change a lot of config options to do that and
> have a very large device.

Not to mention that we don't do any arithmetic operations on inode
numbers, so you're not going to see an overflow.

						- Ted