similar to: Debugging I/O Errors that abort the journal

Dear All Problem with ext3 fs on 3ware 9500S controller: Dec 7 05:59:50 stams kernel: EXT3-fs error (device sda1): ext3_add_entry: bad entry in directory #145998372: rec_len is smaller than minim al - offset=0, inode=0, rec_len=0, name_len=0 Dec 7 05:59:50 stams kernel: Aborting journal on device sda1. Dec 7 05:59:50 stams kernel: ext3_abort called. Dec 7 05:59:50 stams kernel: EXT3-fs

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

Am 24.07.2018 um 21:07 schrieb TE Dukes: > Output from tail: > > > > Jul 24 10:05:02 ts130 clamd[3226]: SelfCheck: Database status OK. > Jul 24 10:15:02 ts130 clamd[3226]: SelfCheck: Database status OK. > Jul 24 10:25:02 ts130 clamd[3226]: SelfCheck: Database status OK. > Jul 24 10:35:02 ts130 clamd[3226]: SelfCheck: Database status OK. > Jul 24 10:35:59 ts130

TE Dukes wrote: >> -----Original Message----- >> From: CentOS [mailto:centos-bounces at centos.org] On Behalf Of Alexander >> Dalloz >> Sent: Tuesday, July 24, 2018 4:19 PM >> To: centos at centos.org >> Subject: Re: [CentOS] Mail has quit working >> >> >> Am 24.07.2018 um 21:07 schrieb TE Dukes: >> >>> Output from tail:

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

Third time trying respond! -------- Original Message -------- Subject: Re: [CentOS] Mail has quit working From: Gordon Messmer < <mailto:gordon.messmer at gmail.com> gordon.messmer at gmail.com> Date: Tue, July 24, 2018 10:31 am To: <mailto:centos at centos.org> centos at centos.org On 07/23/2018 03:39 PM, TE Dukes wrote: > Mail has come to an abrupt stop. Running C7,

> -----Original Message----- > From: CentOS [mailto:centos-bounces at centos.org] On Behalf Of Alexander > Dalloz > Sent: Tuesday, July 24, 2018 4:19 PM > To: centos at centos.org > Subject: Re: [CentOS] Mail has quit working > > Am 24.07.2018 um 21:07 schrieb TE Dukes: > > Output from tail: > > > > > > > > Jul 24 10:05:02 ts130 clamd[3226]:

Hi, I'm running a production server (Debian Sarge install) whose root filesystem (a software raid 1 array of 2 partitions of IDE drive) exhibited the following problem: Oct 28 06:00:06 server2 kernel: attempt to access beyond end of device Oct 28 06:00:06 server2 kernel: md2: rw=1, want=3050401328, limit=16353920 [...] a few of the above line snipped, want is different each time Oct 28

> -----Original Message----- > From: CentOS [mailto:centos-bounces at centos.org] On Behalf Of mark > Sent: Tuesday, July 24, 2018 5:21 PM > To: CentOS mailing list > Subject: Re: [CentOS] Mail has quit working > > TE Dukes wrote: > >> -----Original Message----- > >> From: CentOS [mailto:centos-bounces at centos.org] On Behalf Of > Alexander > >>

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 was creating some directories (mkdir xxxx) while cd'ed to a mounted LV. The first couple of directories were created but subsequent attempts give the following error: #mkdir: cannot create directory `xxxxx': Input/output error The contents of /var/log/messages shows this: Aug 5 10:48:57 inet05 kernel: hda: dma_intr: status=0x51 { DriveReady SeekComplete Error } Aug 5 10:48:57

Hi All, I''m currently running Xen stable (3.0.2-2) with Linux kernel 2.6.16.29. I have a strange problem with *one* of my domU''s, it seems like as soon as I do some heavy disk I/O, the filesystem goes read-only with this on the console: -- end_request: I/O error, dev hda1, sector 8822 Aborting journal on device hda1. ext3_abort called. EXT3-fs error (device hda1):

I have several CentOS5 hosts in a VMware ESX 3.5.0 226117 environment using iSCSI storage. Recently we've begun to experience journal aborts resulting in remounted-read-only filesystems as well as other filesystem issues - I can unmount a filesystem and force a check with "fsck -f" and occasionally find errors. I've found -

I recently came across an enormous cluster of x86 clone machines running fedora core 1 (2.4.24) which have typically all intel or amd have VIA IDE chipsets. They frequently experience corrupted journals rendering the ext3 partition in read-only mode. More important than recovering the filesystem, I am interested in finding the root of the problem. The common hardware that all of these

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

The system stopped responding to ssh but still responded to ping. The logs showed this error: (its long) Feb 4 00:08:08 server1 kernel: gdmgreeter: page allocation failure. order:0, mode:0x50 Feb 4 00:08:08 server1 kernel: [<c014f863>] __alloc_pages+0x28b/0x29d Feb 4 00:08:08 server1 kernel: [<c014b70f>] find_or_create_page+0x39/0x72 Feb 4 00:08:08 server1 kernel:

I ran into a problem when using grub-install experimentally in what is obviously a foolish way, since I was unable to boot the machine afterwards. I got round the problem, as I shall explain, but I'm still interested to know why the problem arose. Having added a second hard disk to my CentOS-6.5 server, as an experiment I gave the command grub-install /dev/sdb after checking (with fdisk)

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! 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

Hi all. I have two hosts with drbd: kmod-drbd83-8.3.8-1.el5.centos drbd83-8.3.8-1.el5.centos and kernel (CentOS 5.7): 2.6.18-308.4.1.el5 After a recent upgrade of kernel I have had two sitiuations when my ext3 filesystem on /dev/drbd0 became read-only. I've checked disks with smartctl -t long, they are ok. There are no messages with disks problems in /var/log/messages | dmesg. I've made