Fs Error Device Ide0
Contents |
ext3_readdir Date: Tue, 20
Ext3-fs Error Fortigate
Nov 2001 20:02:39 +0100 Hi, yesterday I upgraded fortigate error codes my kernel to 2.4.15-pre6 (after months of using only ac-kernels) and ext3_reserve_inode_write: journal has aborted had my first ext3-error since 0.0.3 . syslog tells me : Nov 20 18:16:31 enterprise kernel: EXT3-fs error (device
Ext3-fs Error Unable To Read Inode Block
ide0(3,9)): ext3_readdir: bad entry in directory #47390: inode out of bounds - offset=0, inode=404363549, rec_len=4096, name_len=23 and the system remounted /usr to ro. I don't have any of raid, acl or anything else, just a plain ide
Ext3_reserve_inode_write: Io Failure
drive. So what should I do now ? Go to runlevel 1, umount /usr and run fsck ? Remounting rw doesn't work : root enterprise:/ #mount -o remount,rw /usr mount: block device /dev/hda9 is write-protected, mounting read-only and then in syslog: Nov 20 19:47:04 enterprise kernel: ext3_abort called. Nov 20 19:47:04 enterprise kernel: EXT3-fs abort (device ide0(3,9)): ext3_remount: Abort forced by user As I already said, the first time ever I had any problems since the very first versions. Thanks for your great work ! Cheers, Dirk Follow-Ups: Re: EXT3-fs error (device ide0(3,9)): ext3_readdir From: Andreas Dilger [Date Prev][Date Next] [Thread Prev][Thread Next] [Thread Index] [Date Index] [Author Index]
net> Subject: Re: EXT3-fs error (device ide0(3,9)): ext3_readdir Date: Wed, 21 Nov 2001 00:14:51 +0100 Hi Andreas, On Tue, Nov 20, 2001 at 12:51:48PM -0700, Andreas Dilger wrote: > That does seem to be a bad inode number, unless you actually have 400M > inodes in this fs. It seems somewhat strange in hex: 0x181a191d, so > ext3-fs error (device sd(8,17)) not just a single bit error, and name_len=23 is 0x17, so also strange, > but rec_len seems OK.
Fortigate Error 174
> > > So what should I do now ? Go to runlevel 1, umount /usr and run fsck ? > > Yes, always the best thing to fortigate format boot device do when having an ext2/ext3 problem, > unless you want to keep it around in case we need more data to try > and debug it. What you might want to do is: > Unfortunately I need this box, so I had to do the https://www.redhat.com/archives/ext3-users/2001-November/msg00379.html repair as fast as possible. > # unmount /usr > # script /tmp/e2fsck.log > # debugfs (device name) > debugfs> dump <47390> /tmp/bad_dir > debugfs> q > > # od -Ax -tx4 -a /tmp/bad_dir > (od output here) 000000 0000b91e 0201000c 0000002e 0000b91d rs 9 nul nul ff nul soh stx . nul nul nul gs 9 nul nul 000010 0202000c 00002e2e 0000c2c7 010d0018 ff nul stx stx . . nul nul G B nul nul can nul cr soh 000020 6c697562 736e6974 672e312e 0000007a b u i l t i https://www.redhat.com/archives/ext3-users/2001-November/msg00383.html n s . 1 . g z nul nul nul 000030 0000c3a8 07070010 312e6873 007a672e ( C nul nul dle nul bel bel s h . 1 . g z nul 000040 0000c2c1 010a0014 73616272 2e312e68 A B nul nul dc4 nul nl soh r b a s h . 1 . 000050 00007a67 0000c2c3 01090014 68736162 g z nul nul C B nul nul dc4 nul ht soh b a s h 000060 672e312e 0000007a 0000c2c5 010c0014 . 1 . g z nul nul nul E B nul nul dc4 nul ff soh 000070 68736162 2e677562 7a672e31 0000b88d b a s h b u g . 1 . g z cr 8 nul nul 000080 0114001c 736e6573 656c6269 6964652d fs nul dc4 soh s e n s i b l e - e d i 000090 2e726f74 7a672e31 0000b88f 010b0014 t o r . 1 . g z si 8 nul nul dc4 nul vt soh These are the first 10 lines of the od output, the whole file has ~370k. I can send it per pm or post other parts if you need it. > > # e2fsck -f (device name) > (e2fsck output here) root enterprise [/3]:/home #e2fsck -f -v /dev/hda9 e2fsck 1.25 (20-Sep-2001) Pass 1: Checking inodes, blocks, and sizes Pass 2: Checking directory structure Pass 3: Checking directory connectivity Pass 4: Checking reference counts Pass 5: Checking group summary information 55978 inodes used (1%) 3107 non-contiguous inodes (5.6%) # of inodes with ind/dind/tind blocks: 2173/11/0 244133 blocks used (86%) 0 bad blocks 0 large files 48549 regular files 3828 directories 0 character device files 0 block
Search Tutorials/Articles Search HCL Search Reviews Search ISOs Go to Page... LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware ext3-fs error ? User Name Remember Me? Password Slackware This Forum is for the discussion of Slackware Linux. Notices Welcome to LinuxQuestions.org, http://www.linuxquestions.org/questions/slackware-14/ext3-fs-error-337720/ a friendly and active Linux Community. You are currently viewing LQ as a guest. By joining http://marc.info/?l=linux-kernel&m=99115589530296&w=2 our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today! Note that registered members see fewer ads, and ContentLink is completely disabled once you log in. Are you new to LinuxQuestions.org? Visit the following links: Site Howto | fs error Site FAQ | Sitemap | Register Now If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here. Having a problem logging in? Please visit this page to clear all LQ-related cookies. Introduction to Linux - A Hands on Guide This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at fs error device the end of each chapter. For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own. Click Here to receive this Complete Guide absolutely free. Page 1 of 2 1 2 > Search this Thread 06-27-2005, 02:03 PM #1 realnerd Member Registered: Aug 2004 Distribution: Gentoo (main), FreeBSD, VoidLinux, Crux, OpenBSD, Arch Posts: 49 Blog Entries: 1 Rep: ext3-fs error ? Hi everybody, I have on my computer 3 systems: win$oft xp, Mandrake 9.2 and Slackware 10.1. When I use SLK 10.1, I am getting very soon a strange behaviour of the system: it no longer accepts a simple command like ls or df, it freezes completely; I often get the message 'IO error' and all I can do is to try to reboot using the keys CTRL+Alt+backspace. Then i have a black screen with the following message: 'EXT3-fs error (device ide0(3,9)) in start_transaction : Journal has aborted' or 'EXT3-fs error (device ide0(3,9)) in ext3_reserve_inode_write: IO failure' My Slackware system / is installed on hda9 and the home of SLK on hda10. When I use
! com> Date: 2001-05-29 14:46:04 [Download message RAW] BlankTo all the kernel people, Ok, this is probabally old news and has been fixed, but the following happened in kernel 2.4.3 (ironically when i was deleting /usr/src/linux in order to extract the latest 2.4.5 :-) Here it is: However, it has a very slight sound of a more serious problem, to do with my disk (however, since i know nothing about this error message, i will take no sides) May 29 01:36:35 toweringmeep kernel: hda: read_intr: status=0x59 { DriveReady SeekComplete DataRequest Error } May 29 01:36:35 toweringmeep kernel: hda: read_intr: error=0x40 { UncorrectableError }, LBAsect=2113616, sector=2113553 May 29 01:36:35 toweringmeep kernel: end_request: I/O error, dev 03:01 (hda), sector 2113553 May 29 01:36:35 toweringmeep kernel: EXT2-fs error (device ide0(3,1)): read_inode_bitmap: Cannot read inode bitmap - block_group = 129, inode_bitmap = 1056776 May 29 01:36:35 toweringmeep kernel: kernel BUG at inode.c:886! May 29 01:36:35 toweringmeep kernel: invalid operand: 0000 May 29 01:36:35 toweringmeep kernel: CPU: 0 May 29 01:36:35 toweringmeep kernel: EIP: 0010:[iput+218/348] May 29 01:36:35 toweringmeep kernel: EFLAGS: 00010282 May 29 01:36:35 toweringmeep kernel: eax: 0000001b ebx: c04e12a0 ecx: c1c8e000 edx: c0229808 May 29 01:36:35 toweringmeep kernel: esi: c022d440 edi: c1ca9f40 ebp: c10e1fa4 esp: c10e1f50 May 29 01:36:35 toweringmeep kernel: ds: 0018 es: 0018 ss: 0018 May 29 01:36:35 toweringmeep kernel: Process rm (pid: 5838, stackpage=c10e1000) May 29 01:36:35 toweringmeep kernel: Stack: c01f11e5 c01f1265 00000376 c1ca9f40 c04e12a0 c013b9a8 c04e12a0 00000000 May 29 01:36:35 toweringmeep kernel: c04e10c0 c0135854 c1ca9f40 c1ca9f40 c1ca9f40 c1a05000 c013592b c04e10c0 May 29 01:36:35 toweringmeep kernel: c1ca9f40 c10e0000 08097753 00000000 bffff83