Hi All, Again iam facing the same issues as turned back to read mode. please find below dmesg log and these are the lines which is above and below the line *"Journal has aborted"*
""" Buffer I/O error on device dm-2, logical block 1309683 lost page write due to I/O error on dm-2 Buffer I/O error on device dm-2, logical block 1309684 lost page write due to I/O error on dm-2 Buffer I/O error on device dm-2, logical block 1309685 lost page write due to I/O error on dm-2 JBD2: Detected IO errors while flushing file data on dm-2-8 Aborting journal on device dm-2-8. EXT4-fs error (device dm-2) in ext4_reserve_inode_write: Journal has aborted EXT4-fs error (device dm-2) in ext4_reserve_inode_write: Journal has aborted EXT4-fs error (device dm-2) in ext4_reserve_inode_write: Journal has aborted EXT4-fs error (device dm-2) in ext4_reserve_inode_write: Journal has aborted EXT4-fs error (device dm-2): ext4_journal_start_sb: Detected aborted journal EXT4-fs (dm-2): Remounting filesystem read-only EXT4-fs error (device dm-4): ext4_journal_start_sb: Detected aborted journal EXT4-fs (dm-4): Remounting filesystem read-only EXT4-fs (dm-4): ext4_da_writepages: jbd2_start: 1024 pages, ino 130322; err -30 EXT4-fs error (device dm-2): mpage_da_map_and_submit: Failed to mark inode 134396 dirty EXT4-fs (dm-2): ext4_da_writepages: jbd2_start: 1022 pages, ino 134396; err -30 EXT4-fs error (device dm-2) in ext4_reserve_inode_write: Journal has aborted journal commit I/O error JBD2: Detected IO errors while flushing file data on dm-2-8 journal commit I/O error (END) Please help me out with the reasons. Thanks, HariPrasadh On Thu, Oct 17, 2013 at 12:11 AM, Arun Khan <[email protected]> wrote: > On Wed, Oct 16, 2013 at 10:03 PM, hari prasadh <[email protected]> > wrote: > > Thanks for your responses.It has 13%usage only while checking with df -h > > and all the necessary permissions present in folder and partition > > level.atthat time i haven't any clues...i have checked for > > /var/log/messages and > > dmesg|less too.i havent got any clues and iam in short of time to analyse > > further).Finally i have rebooted the system and got resolved. > > Does your /etc/fstab have options to mount the partition in ro mode if > there are errors in the file system? If so, it is likely that > partition was mounted in ro mode because of file system errors. Boot > with a Live CD and run fsck on the concerned partitions. > > Also run badblocks on the hard disks hosting the partitions. > > HTH, > -- Arun Khan > _______________________________________________ > ILUGC Mailing List: > http://www.ae.iitm.ac.in/mailman/listinfo/ilugc > ILUGC Mailing List Guidelines: > http://ilugc.in/mailinglist-guidelines > -- Thanks & Regards, HariPrasadh _______________________________________________ ILUGC Mailing List: http://www.ae.iitm.ac.in/mailman/listinfo/ilugc ILUGC Mailing List Guidelines: http://ilugc.in/mailinglist-guidelines
