zigzam

Well-Known Member
May 9, 2005
206
0
166
Every night my system has been going into read only mode:


Feb 12 07:33:02 hostname kernel: EXT3-fs error (device sda8): ext3_lookup: unlinked inode 55804731 in dir #55804693
Feb 12 07:33:02 hostname kernel: Aborting journal on device sda8.
Feb 12 07:33:02 hostname kernel: __journal_remove_journal_head: freeing b_committed_data
Feb 12 07:33:02 hostname kernel: ext3_abort called.
Feb 12 07:33:02 hostname kernel: EXT3-fs error (device sda8): ext3_journal_start_sb: Detected aborted journal
Feb 12 07:33:02 hostname kernel: Remounting filesystem read-only
Feb 12 07:33:02 hostname kernel: EXT3-fs error (device sda8): ext3_lookup: unlinked inode 55804731 in dir #55804693
I have already tried a normal FSCK, but it did not find any errors. Since it appears to be a bad journal should I run:

tune2fs -O ^has_journal /dev/sda8

then FSCK

tune2fs -j /dev/sda8


Do you think this will work and fix the re-occurring issue?
 

JawadArshad

Well-Known Member
PartnerNOC
Apr 8, 2008
459
7
68
PK
cPanel Access Level
DataCenter Provider
Every night my system has been going into read only mode:




I have already tried a normal FSCK, but it did not find any errors. Since it appears to be a bad journal should I run:

tune2fs -O ^has_journal /dev/sda8

then FSCK

tune2fs -j /dev/sda8


Do you think this will work and fix the re-occurring issue?
This is not the appropriate forum to ask this in my opinion. The only suggestion would be to check your cron jobs or any jobs that run at or around the time your server goes RO.