Linux fedora filesystem going on read only mode

[sanwin]

Hi,
Fedora filesystems are going on read only mode suddenly. i could not find the reason behind this behaviour. Can anyone help me.

EXT3-fs error (device dm-2): ext3_journal_start_sb: Detected aborted journal
Remounting filesystem read-only
sd 0:0:0:0: SCSI error: return code = 0x20008
end_request: I/O error, dev sda, sector 8674469
sd 0:0:0:0: SCSI error: return code = 0x20008
end_request: I/O error, dev sda, sector 8674477
sd 0:0:0:0: SCSI error: return code = 0x20008
end_request: I/O error, dev sda, sector 8674485
sd 0:0:0:0: SCSI error: return code = 0x20008
end_request: I/O error, dev sda, sector 8674493
sd 0:0:0:0: SCSI error: return code = 0x20008
end_request: I/O error, dev sda, sector 8674501
Buffer I/O error on device dm-3, logical block 9583
lost page write due to I/O error on dm-3
Aborting journal on device dm-3.
ext3_abort called.
EXT3-fs error (device dm-3): ext3_journal_start_sb: Detected aborted journal
Remounting filesystem read-only


Thanks,
Regards,
Sanwin

[Steven E. Protter]

Shalom,

There has been a disk problem. The file system is corrupted.

fsck.ext3 needs to be run. If fsck can correct the problem, then everything should be fine.

SEP

[Heironimus]

Those I/O errors may mean a failed drive, cable, or controller. fsck may not be able to repair the damage if the underlying problem is the hardware, and you probably shouldn't rely on the drive.

[dirk dierickx]

ext3_journal_start_sb: Detected aborted journal

i think that error says it all, there is something wrong with the journal of that fs. fsck might be able to solve it, unless you have a bad disk. check with SMART tools to query the disk health or browse through you syslogs if there were any physical disk errors.

[Roman Schmidt]

check if you have following entry in your /etc/fstab:

[device] [mountpoint] ext3 errors=remount-ro 0 0

errors=remount-ro tells the filesystem explicitly to remount in readonly modus if there are i/o errors.

if i were you i would leave it like that because writing on a corrupted filesystem surely will corrupt it even more.

instead you should do an fsck.

if this happens too often maybe the disk or cables have to be replaced.

[Tim Towers]

It looks to me like your first disk (sda) has gained a clump of bad sectors. Maybe it received a hard knock whilst in use, maybe it became unplugged briefly or maybe it is failing.

You may be able to make the disk consistent again by running fsck but any data that has been lost by this event is unrecoverable.

Assuming the damage is not bad enough to prevent the system starting up the easiest way to check it and remount it readonly is to reboot but make sure a backup is run before you do so because there is a chance that the system will not recover.

If nothing obvious happened that explains the fault (like a loose cable) then you should start the warranty repair process. The disk vendor may request you run a diagnostic tool to check how badly the disk is damaged. These are always available as bootable USB,floppy or CD images.

You can try to fix the inconsistency with "fsck /dev/dm-3" and turn on writability with "mount -o rw,remount /dev/dm-3" but if you have not identified the root cause you are likely to make the data loss worse.