On Tue, Apr 1, 2008 at 12:12 AM, Kai Schaetzl <maillists at conactive.com> wrote: > Alain Spineux wrote on Mon, 31 Mar 2008 22:43:33 +0200: > > > > EXT3-fs error (device md1): ext3_journal_start_sb: Detected aborted journal > > Remounting file read-only > > CentOS 4? No Centos 5.1 > > Force a complete filesystem check on that drive. I had this once happen after > a kernel upgrade. Everything seemed okay after rebooting the machine but it > came back each night during the updatedb run. I finally forced a filesystem > repair that fixed it and I haven't heard ever since from it. I tried to get > more information about that problematic inode and it seems it was just > corrupted. The boot up never fixed that. I had no choice, it rebooted in single user mode. I ran a fsck, replied 20 times yes. And now it still in heavy load like yesterday, for more than 12H now > > Kai > > -- > Kai Schätzl, Berlin, Germany > Get your web at Conactive Internet Services: http://www.conactive.com > > > > > > _______________________________________________ > CentOS mailing list > CentOS at centos.org > http://lists.centos.org/mailman/listinfo/centos > -- Alain Spineux aspineux gmail com May the sources be with you