similar to: ext3 errors

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

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

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

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:

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)):

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

Hello, i posted a question about a possible ext3fs bug a few month ago. I see this kernel-msg in the messages: Oct 8 18:30:00 o5s kernel: EXT3-fs error (device sd(8,10)) in ext3_new_inode: error 28 Oct 8 18:35:00 o5s kernel: EXT3-fs error (device sd(8,10)) in ext3_new_inode: error 28 Oct 8 18:40:00 o5s kernel: EXT3-fs error (device sd(8,10)) in ext3_new_inode: error 28 they repead

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

A mysql database file was copied over to a new box running Fedora Core 1. The kernel was updated to the latest Fedora release. However mysqld complains about corrupted tables. The kernel was then updated to 2.6.5 mysqld still complains about corrupted tables. Hardware: Dual PIII 800. 3ware RAID dmesg: ... ... ... EXT3-fs error (device sdb1): ext3_free_blocks: Freeing blocks not in

hi all, I installed v3.2 from source and now dom0 is booting well. But when I tried to start domU it shows the following error message and seems hanging. EXT3-fs: mounted filesystem with ordered data mode. EXT3-fs warning: mounting unchecked fs, running e2fsck is recommended EXT3 FS on hda1, internal journal device-mapper: ioctl: 4.7.0-ioctl (2006-06-24) initialised: dm-devel@redhat.com

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,

Hello, I''m using Xen 4.0.0 compiled from source with the 2.6.31.13 kernel that it pulls down on its own. I added support for the aacraid driver to the kernel using ''make menuconfig'' from the build-linux-2.6-pvops_x86_64 subdirectory, and then built and installed the whole thing using ''make install'' from the xen-4.0.0 directory. I compiled this

Hi, Subject line says it all. When one of the linux.org.uk machines got rebooted, it performed a full fs check of the main 160GB ext3 partition claiming it contained errors. During the check it found: Deleted inode 142279 has zero dtime. FIXED. The kernel message log contained lots of: EXT3-fs error (device md(9,1)) in ext3_new_inode: error 28 We had used up all the available inodes.

Hi, Upon upgrading xen-kernel I see the following error/warnings at the end , though the upgrade process went fine. Installing : kernel-xen 1/1 /etc/sysconfig/kernel: line 7: alias: scsi_hostadapter0: not found /etc/sysconfig/kernel: line 7: alias: aacraid: not found Detailed logs : #################################################### --> Running transaction check

We have several large ext3 file system partitions. One of them sets itself to read-only after getting journel problems. I understand that's a good thing, but obviously I need to correct the problem so that it will stop locking itself. Here are some details; OS is Redhat EL4 x86_64 running on a SunFire v40z, kernel is 2.6.9-42.0.2.ELsmp. The disk storage in question is external, via

Would the following be symptoms of hardware problems or just a corrupt fs? Will fsck tonight when a new power supply is going into the machine. Kernel: 2.4.17 Drive: Maxtor D740X-6L 80GB connected via HPT366 Feb 25 21:26:33 viper kernel: hde: dma_intr: status=0x51 { DriveReady SeekComplete Error } Feb 25 21:26:33 viper kernel: hde: dma_intr: error=0x40 { UncorrectableError },

Hi! I noticed yet another dying IBM drive in one of my servers, producing IDE + "standard" ext3 error messages (happened during the start of a new journal methinks): ext3_reserve_inode_write: aborting transaction: Journal has aborted in __ext3_journal_get_write_access<2>EXT3-fs error (device ide5(57,1)) in ext3_reserve_inode_write: Journal has aborted which clearly shows that

I got a I/O error on one of my disks that caused the journal to abort (error below) and be mounted in read only mode. I rebooted and the file system check ran automatically and resolved the error. I did some searching around and couldn't find a likely cause (the disk is a virtual disk, shared from a SAN for VMWare ESXi5.0). An hour after bringing the system back up, we got another one.

Hello, does anyone run xen on an dell poweredge 750 ? I am getting the following scsi errors on the raid driver on hight I/O load. aacraid: Host adapter reset request. SCSI hang ? aacraid: SCSI bus appears hung with kernel 2.6.8 the whole maschine hang on this error. now I am using xen 2.0.6 with kernel 2.6.11.10 and the latest aacraid driver from adaptect. so the device only hang ca 1:30

> > I''ve given this change a go on my PE1650 (aacraid driver). > > Unfortunately this seems to be one of the SCSI drivers that doesn''t > > correctly handle the error condition. > > > > Running my usual test (''compare'' in dom0, compiles in other domains), I > > don''t see any differences in the compares, but after a