[Date Prev][Date Next] [Thread Prev][Thread Next] [Thread Index] [Date Index] [Author Index]

RE: bad inode number followed by ext3_abort and remount readonly

From: "Joseph D. Wagner" <theman josephdwagner info>
To: "'Theodore Ts'o'" <tytso mit edu>, "'David Shaw'" <dshaw jabberwocky com>
Cc: ext3-users redhat com, 'Andreas Dilger' <adilger clusterfs com>
Subject: RE: bad inode number followed by ext3_abort and remount readonly
Date: Wed, 15 Jun 2005 12:13:34 -0500

> 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?

Joseph D. Wagner

Follow-Ups:
- Re: bad inode number followed by ext3_abort and remount readonly
  - From: 'Andreas Dilger'
- Re: bad inode number followed by ext3_abort and remount readonly
  - From: Theodore Ts'o

References:
- Re: bad inode number followed by ext3_abort and remount readonly
  - From: Theodore Ts'o

[Date Prev][Date Next] [Thread Prev][Thread Next] [Thread Index] [Date Index] [Author Index]