Ext3-fs Error Device Sda2 Ext3_get_inode_loc
Contents |
Posts: 13 EXT3-fs error « on: 04 July 2012, 06:16:35 pm » After a power outage, I am not able to get my DreamPlug to work normally again.When booting with the JTag moule connected, the terminal
Linux Ext3_get_inode_loc Unable To Read Inode Block
printout ends with the lines in the quote below.Does this mean that the filesystem is corupted?Is
Ext3-fs Error (device Dm-0) Ext3_journal_start_sb Detected Aborted Journal
there some easy (or hard) way to fix this?Quote ext3-fs error ext3_find_entry reading directory [ OK ]* Loading kernel modules... http://kb.fortinet.com/kb/documentLink.do?externalID=FD37499 [ OK ] * Loading manual drivers...* Setting kernel variables (/etc/sysctl.conf)... [ OK ]* Setting kernel variables (/etc/sysctl.d/10-console-messages.conf)... [ OK ]* Setting kernel variables (/etc/sysctl.d/10-network-security.conf)... [ OK ]* Activating swap... https://newit.co.uk/forum/index.php?topic=3393.0 [ OK ]* Starting early crypto disks... [ OK ]* Starting remaining crypto disks... [ OK ]* Checking file systems... fsck 1.41.4 (27-Jan-2009) [ OK ]* Mounting local filesystems... [ OK ]* Activating swapfile swap... [ OK ]end_request: I/O error, dev sda, sector 879738Aborting journal on device sda2.Segmentation fauEXT3-fs (sda2): error: ext3_journal_start_sb: ltDetected aborted journalEXT3-fs (sda2): error: remounting filesystem read-only/etc/init.d/rc: 390: /etc/rcS.d/S37mountoverflowtmp: Input/output error/etc/init.d/rc: 390: /etc/rcS.d/S37udev-finish: Input/output error/etc/init.d/rc: 390: /etc/rcS.d/S40networking: Input/output error/etc/init.d/rc: 390: /etc/rcS.d/S49console-setup: Input/output error/etc/init.d/rc: 390: /etc/rcS.d/S55urandom: Input/output error/etc/init.d/rc: 390: /etc/rcS.d/S70x11-common: Input/output errorinit: rc-default main process (1647) terminated with status 2EXT3-fs err
Issues Roadmap View Issue Details[Jump to Notes] [Issue History] [Print] IDProjectCategoryView StatusDate SubmittedLast Update0005879CentOS-5kernelpublic2012-08-06 10:422013-04-18 07:44Reporteranand_happsPriorityhighSeveritymajorReproducibilityhave not triedStatusassignedResolutionopenProduct VersionTarget VersionFixed in https://bugs.centos.org/view.php?id=5879 VersionSummary0005879: Linux based file systems become read-onlyDescriptionofflately we have been facing a problem with disks going readonly on our systems installed 5.4 64 bit. This is normally observed on a server handling a traffic of more than 2K QPS. This is my personal experience. Some system with similar config with lesser traffic has never fs error come up with the same issue. A similar issue was earlier highlighted by VMWARE. http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=51306 Need to know if there is any patch that fixes the problem or we would require to upgrade. Additional InformationEXT3-fs error (device sda3): ext3_get_inode_loc: unable to read inode block - inode=2408772, block=2424850 sd 1:0:0:0: SCSI error: return code = 0x00040000 ext3-fs error (device end_request: I/O error, dev sda, sector 52685560 EXT3-fs error (device sda3): ext3_get_inode_loc: unable to read inode block - inode=2409093, block=2424860 sd 1:0:0:0: SCSI error: return code = 0x00040000 end_request: I/O error, dev sda, sector 52685400 EXT3-fs error (device sda3): ext3_get_inode_loc: unable to read inode block - inode=2408470, block=2424840 sd 1:0:0:0: SCSI error: return code = 0x00040000 end_request: I/O error, dev sda, sector 52685504 EXT3-fs error (device sda3): ext3_get_inode_loc: unable to read inode block - inode=2408882, block=2424853 sd 1:0:0:0: SCSI error: return code = 0x00040000 end_request: I/O error, dev sda, sector 52685600 EXT3-fs error (device sda3): ext3_get_inode_loc: unable to read inode block - inode=2409280, block=2424865 sd 1:0:0:0: SCSI error: return code = 0x00040000 end_request: I/O error, dev sda, sector 52685592 TagsNo tags attached.Attached Files Relationships Relationships Notes ~0015588 range (administrator) 2012-08-06 12:08 If you can reproduce that with CentOS 5.8, please say so. Nobody is going to look into issues with CentOS 5.4. ~0015711 Spacedust (reporter) 2012-08-28 16:56 Please show smartctl -a /dev/