Ext3-fs Error Device Sda2 Ext3_find_entry Reading Directory
Contents |
I/O Error Installing, Configuring, Troubleshooting server daemons such as Web and Mail Locked Print view Search Advanced ext3 fs error ext3_find_entry reading directory offset 0 search 2 posts • Page 1 of 1 mashkoorqadir Posts:
Ext3 Fs Error Ext3_get_inode_loc Unable To Read Inode Block
50 Joined: 2012/06/27 07:55:01 Centos server giving I/O Error Postby mashkoorqadir » 2014/06/05 08:22:24 Hi guys,My linux ext3_get_inode_loc unable to read inode block CentOS 5.4 server is running since 2009 working fine since yesterday. it suddenly stop responding. its very critical server for the company. I saw repeated following line and was unable to stop that./etc/rc.d/rc.sysinit: line 947: /bin/usleep: Input/Output errorThis line just repeats over and over and I cant stop it with control-c it.when i reboot the machine it failed mount local partitions and stuck. one more time i rebooted the message on the screen was,setting host name xyzsetting up logical volume mangment:/1: superblock has an invalid ext3 journal (inode 8)clear*** ext3 journal has been deleted - file system in ext2 only ***Error reading block 2056 (attempt to read block from filesystem resulted in short read). Remounting root file system inread-write mode. okMounting local filesystems FailedEnabling local filesystem quotas: FailedEnabling /etc/fstab swaps: Failedand hang at this stage. Again i rebooted this time server started and loaded most of the process at login stage it gave following messages.end_request: I/O error, dev sdb, sector 247392428EXT3-fs error (device sda3): ext3_find_entry: reading directory 528278814 offset 0end_request: I/O error, dev sdb, sector 247392428EXT3-fs error (device sda3): ext3_find_entry: reading directory 528278814 offset 0end_request: I/O error, dev sdb, sector 247392428EXT3-fs error (device sda3): ext3_find_entry: reading directory 528278814 offset 0end_request: I/O error, dev sdb, sector 71end_request: I/O error, dev sdb, sector 63end_request: I/O error, dev sdb, sector 17414208end_request: I/O error, dev sdb, sector 17414440end_request: I/O error, dev sdb, sector 1028160end_request: I/O error, dev sdb, sector
redhat com> Subject: Re: EXT3 errors and / filesystem readonly. Date: Mon, 31 Aug 2009 15:27:00 -0400 Hello, I have a production RHEL ES 4U6 server encountered EXT3 filesystem errors. Subsequently local / Root (/dev/cciss/c0d0p2) and one emcpower device went readonly. I had to reboot the server and FSCK and then remount both the filesystems back to normal. I have both Linux running in local hdd and other filesystems mounted from EMC clariion. I see the below errors in the /var/log/messages. Aug 26 20:45:41 zmcs kernel: Error:Mpx:Path Bus 0 Tgt 1 Lun 6 to APM00083500788 is dead. Aug 26 20:45:41 http://www.centos.org/forums/viewtopic.php?t=46551 zmcs kernel: Error:Mpx:Path Bus 0 Tgt 1 Lun 6 to 600601607D0122005484F535FE81DE11 is marked as dead; volume ID has changed. Aug 26 20:45:43 zmcs kernel: Error:Mpx:Path Bus 0 Tgt 0 Lun 6 to APM00083500788 is dead. Aug 26 20:45:43 zmcs kernel: Error:Mpx:Path Bus 0 Tgt 0 Lun 6 to 600601607D0122005484F535FE81DE11 is marked as dead; volume ID has changed. Aug 26 20:46:43 zmcs kernel: Error:Mpx:All paths to 600601607D0122005484F535FE81DE11 are https://www.redhat.com/archives/redhat-list/2009-August/msg00211.html dead. Aug 26 20:46:43 zmcs kernel: Error:Mpx:600601607D0122005484F535FE81DE11 is dead. .... ....... ......... Aug 27 02:12:04 zmcs kernel: EXT3-fs error (device dm-2): ext3_find_entry: reading directory #55511780 offset 1 Aug 27 02:12:04 zmcs kernel: Aborting journal on device dm-2. Aug 27 02:12:04 zmcs kernel: EXT3-fs error (device dm-2): ext3_find_entry: reading directory #55511780 offset 2 Aug 27 02:12:04 zmcs kernel: EXT3-fs error (device dm-2): ext3_find_entry: reading directory #55511780 offset 3 Aug 27 02:13:06 zmcs kernel: EXT3-fs error (device dm-2): ext3_get_inode_loc: unable to read inode block - inode=130155080, block=260309012 Aug 27 02:13:42 zmcs kernel: EXT3-fs error (device dm-2): ext3_readdir: directory #123682826 contains a hole at offset 4096 ...... ......... ............ Aug 27 02:16:47 zmcs kernel: ext3_abort called. Aug 27 02:16:47 zmcs kernel: EXT3-fs error (device dm-2): ext3_journal_start_sb: Detected aborted journal Aug 27 02:16:47 zmcs kernel: Remounting filesystem read-only My questions are, 1. Why does the above behaviour happen suddenly? I believe there is a problem with the SAN, please confirm this. 2. Although the above messages seems to be related only to EMC power device, why did the / (local harddisk) filesystem became readonly? Thanks in advance! Thanks KK [Date Prev][Date Next] [Thread Prev][Thread Next] [Thread Index] [Date Index] [Author Index]
external USB harddrive. I havn't had any problems with the previous Ubuntu version but I don't know if it's related to that. When I leave my PC on at night I usually find the OS have forgotten about https://ubuntuforums.org/archive/index.php/t-1502877.html the device. It's not in Gparted. I have mounted the harddrive to a folder but when I click on it it shows an empty folder. The mount is done via /etc/fstab If I reboot it says the device is not yet ready and asks if I want to wait, continue or do something manually. I've found out that I turn off the harddrive and on again it becomes available (under a new device name, fs error /sdd instead og /sdc). And I can access the files and folders on the drive. If I reboot and turn off the device and on again before the boot is complete everything is back to normal. Any idea on what's going on? dileepmJune 6th, 2010, 12:53 PMHi, I am not sure if your problem is for any specific reason. But try this procedure in general http://starksolutions.blogspot.com/2010/05/linux-auto-mount-partitions.html I assume that external hard drives are ext3_find_entry reading directory considered removable drives (like flash/pen drives) tbressonJune 10th, 2010, 10:48 AMI'm not sure that's the issue. But thanks for the reply and the link :) It's there some kind of system log that explains why the connection to the harddrive was dropped or something like that? tbressonJune 15th, 2010, 08:34 AMLet's say I loose the connection to the drive. Is there any commands or anything like that I can write to check out some sort of logs that'll help find out what happend? tbressonJune 22nd, 2010, 06:23 AMdmesg said this: (added to main topic) [32243.112055] usb 1-1: reset high speed USB device using ehci_hcd and address 2 [32258.224041] usb 1-1: device descriptor read/64, error -110 [32273.440026] usb 1-1: device descriptor read/64, error -110 [32273.656030] usb 1-1: reset high speed USB device using ehci_hcd and address 2 [32288.768027] usb 1-1: device descriptor read/64, error -110 [32303.984042] usb 1-1: device descriptor read/64, error -110 [32304.200049] usb 1-1: reset high speed USB device using ehci_hcd and address 2 [32309.220081] usb 1-1: device descriptor read/8, error -110 [32314.340096] usb 1-1: device descriptor read/8, error -110 [32314.556032] usb 1-1: reset high speed USB device using ehci_hcd and address 2 [32319.576086] usb 1-1: device descriptor read/8, error -110 [32324.696102] usb 1-1: device descriptor read/8, error -110 [32324.800054] usb 1-1: USB disconnect, address 2 [32324.800381]