similar to: ext3_get_inode_loc: bad inode number:

Hi All, I m a novice developer of Linux applications. Recently I faced a file system corruption. (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)):

Hi, Sorry if this is an old and fixed issue but I can't really seem to find a definitive explanation/fix to this in the mail lists. Ever since I upgraded to FC2 my server randomly decides that it can no longer access the disk and "aborts" the ext3 journal leaving it read-only as expected. I've seen the same errors on other mail list, explained away as disk or disk cable

I have an apple Xserve RAID attached to a Linux Box, serving one Raided LUN of 2500Gigs, it was functional until the box crashed. When I hard booted it, even though it mounted the FS, I'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

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

Erm, sheez having alot of problems :( I have just been reading all the archives on the mailing list for the past few hours and decided to try make the journal with: tune2fs -j -J10 /dev/hdc1 [root@tkw /]# tune2fs -j -J10 /dev/hdc1 tune2fs 1.20-WIP, 17-Jan-2001 for EXT2 FS 0.5b, 95/08/09 Creating journal inode: done [root@tkw /]# cat /etc/fstab /dev/hdc1 /usr/local ext3

I had a busy mailserver fail on me the other day. Below is what was printed in dmesg. We first suspected a hardware failure (raid controller or something else), so we moved the drives to another (identical hardware) machine and ran fsck. Fsck complained ("short read while reading inode") and asked if I wanted to ignore and rewrite (which I did). After booting up again, the problem came

Hello all. I'm using RedHat 7.2 now and haven't have any problems until today. I can still boot into the system at this time, but cannot load X at all. I'm getting the following error message when I try to run fsck. /contains a file system with errors, check forced. Pass 1: Checking inodes, blocks and sizes Error reading block 1277964 (Attempt to read block from filesystem resulted

I've got a new PE2950 rack system with PERC controller and 6 drives set up contiguously as one RAID5 volume on the PERC controller. Using 64-bit CentOS 4.4, I partitioned for /boot having 100 Meg, swap having 2 gig, and / with the rest (removed LVM). After the install was complete, the system rebooted and just gave me a broken grub prompt (not the graphical Grub boot selector, but

I am running RH 7.3 with kernel 2.4.18-27.7.x. Recently I have added a new 60GB Quantum IDE hard drive to the server. I have set it up as a MASTER on a separate IDE channel. Two partitions on the /dev/hdc are /dev/hdc1, /dev/hdc2 - both using ext3. For more detailed HDD parameters, this is 'hdparm -i /dev/hdc': ----------------- /dev/hdc: Model=IC35L060AVV207-0, FwRev=V22OA66A,

Hi - We have had a raid failure, we have some what recovered but we continue to see the following ext3 message... Apr 17 14:59:14 acnlin84 kernel: EXT3-fs unexpected failure: (((jh2bh(jh))->b_state & (1UL << BH_Uptodate)) != 0); Apr 17 14:59:14 acnlin84 kernel: Possible IO failure. Since we have experienced several instances of ext3 file system corruption when we lose

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

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"

Hello, I have a server running ext3. The server is a dell poweredge 2500 with a 100G raid 0 on a Perc3/Di raid card (aacraid driver). I've asked about this on the aacraid devel list, and no one had any solutions, and I'm not the only one having this problem, because another person on there replied with nearly the same error message as I am getting. Anyway, anywhere from once every few

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:

I have my Linux 2.6 kernel with the necessary HDLC config and also recompiled zaptel accordingly. On modprobe, I get: Found a Wildcard: Digium Wildcard T100P T1/PRI Debug: sleeping function called 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>]

Big BadaBOOM Not entirely sure what went wrong BUT just after the reported load average on the box started to go up at a steady rate of about 1.0 per 40 seconds The box itself had been up for 2 weeks before this happened Phil =--= Feb 24 10:25:08 parcelfarce sshd[28545]: Received signal 15; terminating. Feb 24 10:25:09 parcelfarce kernel: Unable to handle kernel NULL pointer derefer ence at

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

I'm getting kernel crashes on a new machine since it went into production some weeks ago. How can I troubleshoot this? I suspect a hardware problem, but I know too few about the kernel and kernel debugging on Linux to know how I can nail this down with debugging software. Just for reference of what kind these oopses are I quote the last two. The symptom is that the machine stops

Hi, I use ext3 over RAID1+0 LUN. When I disconnect my fiber cable to the RAID (in order to force a migration to a failover node) I expect to see I/O errors and then a failure to write/read to the filesystem, but in addition I get an Assertion failure. The end result is of course an unusable system which needs to be rebooted. (I reboot the system via machine_restart which works okay but I guess