Re: bad inode number followed by ext3_abort and remount readonly

["'Andreas Dilger'" <adilger clusterfs com>]

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.

Cheers, Andreas
--
Andreas Dilger
Principal Software Engineer
Cluster File Systems, Inc.