RE: bad inode number followed by ext3_abort and remount readonly

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

 



> 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

_______________________________________________

Ext3-users@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/ext3-users

[Index of Archives]         [Linux RAID]     [Kernel Development]     [Red Hat Install]     [Video 4 Linux]     [Postgresql]     [Fedora]     [Gimp]     [Yosemite News]

  Powered by Linux