search for: ext3_get_inode_loc

I've got an approximately 100GB ext3 FS which we recently sized down from 300GB using e2fsadm (with the disc offline obviously). I noticed the following in dmesg the other day: EXT3-fs error (device lvm(58,8)): ext3_get_inode_loc: bad inode number: 14827639 EXT3-fs error (device lvm(58,8)): ext3_get_inode_loc: bad inode number: 14041793 EXT3-fs error (device lvm(58,8)): ext3_get_inode_loc: bad inode number: 14827672 EXT3-fs error (device lvm(58,8)): ext3_get_inode_loc: bad inode number: 14827754 EXT3-fs error (device lvm(58...

...on. (I guess) I have a Kernel 2.4.7-10 with ext3 file system in compact flash. The system was up for 3 months and was running with average load conditions. One fine day, it just started sending kernel messages on the serial console. The message was like this. EXT3-fs error (device ide0(3,2)): ext3_get_inode_loc: unab le to read inode block - inode=20089, block=81926 EXT3-fs error (device ide0(3,2)): ext3_get_inode_loc: unable to read inode block - inode=20090, block=81926 EXT3-fs error (device ide0(3,2)): ext3_get_inode_loc: unable to read inode block - inode=20091, block=81926 EXT3-fs error (devi...

...after the attempted kernel boot: Decompressing Linux...done. Booting the kernel. Red Hat nash version 4.2.1.8 starting sda: asking for cache data failed sda: assuming drive cache: write through sda: asking for cache data failed sda: assumint drive cache: write through EXT3-fs error (device sda3): ext3_get_inode_loc: unable to read inode block - inode=2132343, block=1231234 mount: error 5 mounting none EXT3-fs error (device sda3): ext3_get_inode_loc: unable to read inode block - inode=123123, block=124324123 EXT3-fs error (device sda3): ext3_get_inode_loc: unable to read inode block - inode=6353565, block=3...

...omplete Error } Jul 20 04:09:13 server kernel: hdc: dma_intr: error=0x40 { UncorrectableError }, LBAsect=526647391, high=31, low=6553695, sector=526647391 Jul 20 04:09:13 server kernel: end_request: I/O error, dev hdc, sector 526647391 Jul 20 04:09:13 server kernel: EXT3-fs error (device hdc1): ext3_get_inode_loc: unable to read inode block - inode=32915539, block=65830916 Jul 20 04:09:13 server kernel: Aborting journal on device hdc1. Jul 20 04:09:13 server kernel: ext3_abort called. Jul 20 04:09:13 server kernel: EXT3-fs abort (device hdc1): ext3_journal_start: Detected aborted journal Jul 20 04:09:13 s...

...'ve been unable to access it. Cd-ing to any of its directories gives "Input/Output error". The ls ?la on the FS shows "?" for every field with no permission information. The /var/log/messages is flooded with: Feb 1 10:12:21 *HOSTNAME* kernel: EXT3-fs error (device sda1): ext3_get_inode_loc: unable to read inod e block - inode=178356225, block=356712450 An e2fsck gives e2fsck 1.35 (28-Feb-2004) /xraid: recovering journal The filesystem size (according to the superblock) is 610476016 blocks The physical size of the device is 73605104 blocks Either the superblock or the parti...

...he I was able to see only aprox 30GB out of the available 60GB in 'fdisk' for RH7.3. So I started using the partitionted 30GB. The hard drive worked fine for about 2 weeks. Then the following errors occurred: ----------------- Oct 26 04:02:37 lynx kernel: EXT3-fs error (device ide1(22,2)): ext3_get_inode_loc: unable to read inode block - inode=32769 , block=65541 Oct 26 04:02:37 lynx kernel: end_request: I/O error, dev 16:02 (hdc), sector 0 Oct 26 04:02:37 lynx kernel: end_request: I/O error, dev 16:02 (hdc), sector 1048616 Oct 26 04:02:37 lynx kernel: EXT3-fs error (device ide1(22,2)): ext3_get_inode_...

...and rewrite (which I did). After booting up again, the problem came back immediately and root was remounted read only. We moved the data from the read only drive to a new machine. While copying the data, we got this message from time to time (on various files): "EXT3-fs error (device dm-0): ext3_get_inode_loc: unable to read inode block - inode=22561891, block=90243144. I need to find the cause(s) of the problems. So far I have these questions/concerns: - Kernel bug? (This is Ubuntu 8.10 with 2.6.27-7-server) - Filesystem bug/failure? - Did the RAID controller fail to detect a failing drive? This is a...

I tried to convert / to ext3, so I went ahead and entered rootflags=noload,journal=355 on the LILO prompt. The kernel failed to mount /: EXT3-fs error (device ramdisk(1,0)): ext3_get_inode_loc: bad inode number: 355 The boot device is a scsi hard disk, so initrd is used to load the scsi driver, before mounting /. So, it looks like the kernel rootflags= arg gets applied to the ramdisk, not the real root. Blah. -- Sam

...001 for EXT2 FS 0.5b, 95/08/09 Creating journal inode: done [root@tkw /]# cat /etc/fstab /dev/hdc1 /usr/local ext3 defaults 0 0 [root@tkw /]# mount /dev/hdc1 mount: wrong fs type, bad option, bad superblock on /dev/hdc1, or too many mounted file systems EXT3-fs error (device ide1(22,1)): ext3_get_inode_loc: bad inode number: 8 EXT3-fs: invalid journal inode. EXT3-fs: get root inode failed debugfs shows 2133571369 --- error --- .journal not having much luck here.. is there anywhere i can find some up to date docs?

...: error=0x10 { SectorIdNotFound }, LBAsect=81423, sector=81360 hdb: dma_intr: status=0x51 { DriveReady SeekComplete Error } hdb: dma_intr: error=0x40 { UncorrectableError }, LBAsect=10223775, sector=10223712 end_request: I/O error, dev 03:41 (hdb), sector 10223712 EXT3-fs error (device ide0(3,65)): ext3_get_inode_loc: unable to read inode block - inode=636706, block=1277964 EXT3-fs error (device ide0(3,65)) in ext3_reserve_inode_write: IO failure EXT3-fs error (device ide0(3,65)) in ext3_new_inode: IO failure hdb: dma_intr: status=0x51 { DriveReady SeekComplete Error } hdb: dma_intr: error=0x10 { SectorIdNotFou...

Hi all, I've been working with the ext3-fs for several months (since 0.0.2c), and it works pretty fine for me, but I haven't found out, how I works to migrate my root-partition from ext2 to ext3. I tried it with the commands at the lilo-prompt, but it didn't work. I only received a kernel panic. Any ideas, how I can migrate to ext3 on my root-partition? tnx, Joachim -- Joachim

...ed from invalid context at mm/slab.c:2000 in_atomic():0[expected: 0], irqs_disabled():1 [<0211e605>] __might_sleep+0x82/0x8c [<02144643>] kmem_cache_alloc+0x1d/0x57 [<42ad7a2c>] zt_ctl_ioctl+0x112c/0x16b0 [zaptel] [<022d6c00>] __cond_resched+0x14/0x39 [<428a315a>] ext3_get_inode_loc+0x4f/0x210 [ext3] [<0217269c>] d_instantiate+0xa3/0xa9 [<021729ea>] d_splice_alias+0x145/0x14e [<428a4ec9>] ext3_lookup+0x70/0x89 [ext3] [<0216802f>] real_lookup+0x6e/0xd2 [<02171457>] dput+0x1b/0x287 [<0216901d>] link_path_walk+0xd3c/0xdf7 [<02163ffc&g...

...l print errors like these on tty1: EXT3-fs error (device sd(8,4)) in ext3_reserve_inode_write: IO Failure I/O error: dev 08:04, sector 0 EXT3-fs error (device sd(8,4)) in ext3_new_inode: IO failure I/O error: dev 08:04 secotor 0 I/O error: dev 08:04 secotor 1050528 EXT3-fs error (device sd(8,4)): ext3_get_inode_loc: unable to read inode block - inode=73040, block=131316 I/O dev 08:04 sector 0 EXT3-fs error (device sd(8,4)) in ext3_reserve_inode_write: IO Failure I am running a hand compiled 2.4.20 from ftp.kernel.org with no patches applied. The server is a dual p3 1.2ghz with 2gb of ram. The I/O error alw...

Hi, folks A black out corrupted my file system (ext3, RH7.1). When I boot, the following message shows up: hdb: Quantum Fireball CR4.3A, ATA Disk Drive EXT3-fs error (device ide0 (3,66)): ext3_get_inode_loc: group >= groups count EXT3-fs: invalid journal inode EXT2-fs error (devide ide0 (3,66)): ext2_read_inode: group >= groups count EXT2-fs: corrupt root inode, run e2fsck Kernel Panic: VFS: Unable to mount root fs on 03:42 I moved the HD to another computer (RH7.1 too) to try to recovery it,...

...l address 00000000 Feb 24 10:25:09 parcelfarce kernel: current->tss.cr3 = 00101000, %%cr3 = 0010100 0 Feb 24 10:25:09 parcelfarce kernel: *pde = 00000000 Feb 24 10:25:09 parcelfarce kernel: Oops: 0000 Feb 24 10:25:09 parcelfarce kernel: CPU: 1 Feb 24 10:25:09 parcelfarce kernel: EIP: 0010:[ext3_get_inode_loc+49/340] Feb 24 10:25:09 parcelfarce kernel: EFLAGS: 00010206 Feb 24 10:25:09 parcelfarce kernel: eax: 00000000 ebx: d7b7b000 ecx: d7b7b00 0 edx: c15c2e9c Feb 24 10:25:09 parcelfarce kernel: esi: 39000003 edi: c1078aa0 ebp: c2a9de6 8 esp: c2a9de34 Feb 24 10:25:09 parcelfarce kernel: ds:...

...2 acnlin84 kernel: EXT3-fs error (device sd(8,33)): ext3_free_blocks: bit already cleared for block 14943160 Apr 17 13:40:42 acnlin84 kernel: EXT3-fs error (device sd(8,33)): ext3_free_blocks: bit already cleared for block 3703794 Apr 17 13:40:43 acnlin84 kernel: EXT3-fs error (device sd(8,65)): ext3_get_inode_loc: unable to read inode block - inode=50931914, block=101843272 -- Sev Binello Brookhaven National Laboratory Upton, New York 631-344-5647 sev at bnl.gov

Oh gurus of ext3... We have an application (it's essentially a watchdog) that monitors i/o on the root partition of our Linux system. What we would like to have happen is in the event that the root file system "goes away" (e.g. the SCSI cable is pulled from the storage device containing the root drive), we want to panic the kernel. We have tried using the "-e panic"

i too am an idiot.. and request help here's the sccop i originally formatted the drive with 3 partitions and installed rh8 /boot / swap everything worked. my plan was to have this drive only be a data drive so i inatlled rh8 on another drive and mounted this one on /share so /share looked like /share /bin /sbin /mp3 /usr /etc /dev and so on so i deleted all the

...x05 kernel: Call Trace: Apr 29 15:05:07 nx05 kernel: [<c016a705>] __find_get_block_slow+0x4b/0x1c6 Apr 29 15:05:07 nx05 kernel: [<c016bdb7>] __find_get_block+0x89/0xa5 Apr 29 15:05:07 nx05 kernel: [<c016bde6>] __getblk+0x13/0x49 Apr 29 15:05:07 nx05 kernel: [<e09298e3>] ext3_get_inode_loc+0x4f/0x223 [ext3] Apr 29 15:05:07 nx05 kernel: [<e0929b45>] ext3_read_inode+0x38/0x309 [ext3] Apr 29 15:05:07 nx05 kernel: [<c030fbf0>] __cond_resched+0x14/0x3b Apr 29 15:05:07 nx05 kernel: [<e092e1b7>] ext3_alloc_inode+0xf/0x46 [ext3] Apr 29 15:05:07 nx05 kernel: [<c018...

...:34 10.17.0.2 kernel: I/O error: dev 08:33, sector 847008 Dec 24 13:48:34 10.17.0.2 kernel: SCSI disk error : host 3 channel 0 id 0 lun 1 return code = 10000 Dec 24 13:48:34 10.17.0.2 kernel: I/O error: dev 08:33, sector 846984 Dec 24 13:48:34 10.17.0.2 kernel: EXT3-fs error (device sd(8,51)): ext3_get_inode_loc: unable to read inode block Dec 24 13:48:35 10.17.0.2 kernel: SCSI disk error : host 3 channel 0 id 0 lun 1 return code = 10000 Dec 24 13:48:35 10.17.0.2 kernel: I/O error: dev 08:33, sector 148376 Dec 24 13:48:35 10.17.0.2 kernel: SCSI disk error : host 3 channel 0 id 0 lun 1 return code = 1000...