similar to: Xen and EVMS/Raid5 - Null pointer dereference

CentOS Community, Would someone who is familiar with reading boot messages and kernel errors be able to assist with advising me on what the following errors might mean in dmesg. It seems to come up randomly towards the end of the logfile. ------------[ cut here ]------------ WARNING: at arch/x86/kernel/cpu/mtrr/generic.c:467 generic_get_mtrr+0x11e/0x140() (Not tainted) Hardware name: empty

Hello, yesterday night I had a problem with my server located at a hoster (strato.de). I couldn't ssh to it and over the remote serial console I saw "out of memory" errors (sorry, don't have the text). Then I had reinstall CentOS 5.5/64 bit + all my setup (2h work), because I have a contract with a social network and they will shut down my little card game if it is not

Hello, I''m running into some trouble with what appear on the surface to be OOM issues in Dom0, but I''m not seeing any other evidence. This typically happens during periods of high I/O, and has occurred during RAID initial sync, and mkfs.ext4ing (as a test, no intention to keep ext4 on this array). I''ve found some older posts citing very similar circumstances, however

I've been experiencing delays access data off my file server since I upgraded to 5.3... either I hosed something, have bad hardware or very unlikely, found a bug. When reading or writing data, the stream to the hdd's stops every 5-10 min and %iowait goes through the roof. I checked the logs and they are filled with this diagnostic data that I can't readily decipher. my setup

We are in the process of migrating XFS filesystems from one storage array to another. Both are arrays are mounted locally on the same CentOS 4.4 system (x86_64). We are running kernel 2.6.9-42.0.2.ELsmp along with kernel-module-xfs-2.6.9-42.0.2.ELsmp-0.1-3. The issue we are having is that while the copy is running (using rsync) the system will log these message periodically: kernel: XFS:

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I'm experiencing frequent kernel panics when using the X100P card under the 2.6.6 Fedora kernel. I've attached the kernel output to this message - - it looks like the IRQ stack is overflowing and trashing some memory, causing a series of oopses followed by a complete crash. I have just hacked the kernel to reenable 8k stacks and will see

On 2016-06-01 20:07, Kelly Lesperance wrote: > Software RAID 10. Servers are HP DL380 Gen 8s, with 12x4 TB 7200 RPM drives. > > On 2016-06-01, 3:52 PM, "centos-bounces at centos.org on behalf of m.roth at 5-cent.us" <centos-bounces at centos.org on behalf of m.roth at 5-cent.us> wrote: > > >Kelly Lesperance wrote: > >> I did some additional testing - I

Hello CentOS Xen Heroes, Yesterday, I have installed testing kernel 4.9.23-26.el6.x86_64 from virt-xen-testing repo. It crashed today morning. Hardware is a pretty ancient, testing machine (CO6 PV guests only), but had no problems yet. It was stable on 4.9*, including testing 4.9.15-22.el6.x86_64 Console output: [59826.069427] general protection fault: 0000 [#1] SMP [59826.069463] Modules

Red Hat 2.2.19-6.2.12 + 0.0.7a + https://listman.redhat.com/pipermail/ext3-users/2001-November/002258.html (not tuned in /proc yet) + journal 4MB on each fs + 6 ext3 fs on raid1 (hda+hdc) + 1 ext3 fs on another disk not on raid1 (hdd) While untarring (tar zxf) a file that was on a ext3/raid1 onto hdd I got: ksymoops 2.3.4 on i686 2.2.19-6.2.12.g1. Options used -V (default) -k

EVMS Enterprise Volume Management System sounds interesting, looks like it supported CentOS4, but not CentOS5. But maybe I'm not looking in the right places. -- Drew Einhorn -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.centos.org/pipermail/centos/attachments/20080607/a5de7c79/attachment-0002.html>

Hi all Sombedody can points me to a good tutorial about using high availabilty clusters with xen using heratbeat2, ocfs2 and evms under rhel/centos, debian or sles?? I am doing various searches without a result ... (google shows me a lot of references, mailing lists, etc but not a good doc) Many thanks. -- CL Martinez carlopmart {at} gmail {d0t} com

The tools for raidN (mdadm and friends) don't seem to compile with klibc. Has anyone tackled that, lvm or evms yet in a klibc-based initramfs, or do you usually include uclibc or something when it comes time to get fancy (also, looking ahead to crypto-root and such) Tks, Jeff Bailey

I started with two 160GB drives in RAID1 using EVMS on Centos 4.4. Both drives have now been replaced with 320GB drives but naturally are only offering 160GB (they were replaced individually at different times and self-recovered as they were RAID1. I cannot work out how to increase the size of the array to use all the available space on the disk. If I understand correctly, I should unmount the

Hi, I have seen a few posts on the list from people who were working on this. If anyone has succeeded can you please drop me a line with some notes on your boot process and the initrd creation process please? I seem to have the bits all working individually, but I can''t quite figure out how to get Xen kernel to boot up and start my EVMS stuff under Gentoo. At the moment I have been

Hi list, After a lot of testing + troubleshooting, I guess I'm observing what I am now calling a regression with zaptel 1.4.10 (is it?) As such I call for peer feedback, before either asking Digium install support or filing a bug. Thanks in advance! System: HP Proliant DL380 G5 with 2x PCI-X + 1x PCIe riser card OS: Centos 5 Kernel: 2.6.18-53.1.14.el5 (also tested under

Hello, I have experienced a dom0 crash where the system became unreachable via the network and the console was unresponsive. I would appreciate help interpretting the logs and any configuration change suggestions. It is a stock Debian Lenny dom0 running xen 3.2.1 with kernel 2.6.26-2-xen-amd64 and an AMD Athlon IIx4 with 4 GB of RAM. It is running 4 VMs. One VM has two PCI NICs being

Hi Jens, this series removes the revalidate_disk() function, which has been a really odd duck in the last years. The prime reason why most people use it is because it propagates a size change from the gendisk to the block_device structure. But it also calls into the rather ill defined ->revalidate_disk method which is rather useless for the callers. So this adds a new helper to just

Kelly Lesperance wrote: > I did some additional testing - I stopped Kafka on the host, and kicked > off a disk check, and it ran at the expected speed overnight. I started > kafka this morning, and the raid check's speed immediately dropped down to > ~2000K/Sec. > > I then enabled the write-back cache on the drives (hdparm -W1 /dev/sd*). > The raid check is now running

Hi all. Every few days I am getting a message that looks like the one I have cut and pasted below. It is accompanied by a severe slowdown of the system. In fact, it's practically locked. The machine runs gnome-desktops for 40 users plus about a hundred sessions of a curses based point of sale software, plus a few other functions, so it's a busy machine. Dual Xeon 3.2GHz processors.

Introduce NOKPROBE_SYMBOL() macro which builds a kprobe blacklist in build time. The usage of this macro is similar to the EXPORT_SYMBOL, put the NOKPROBE_SYMBOL(function); just after the function definition. If CONFIG_KPROBES=y, the macro is expanded to the definition of a static data structure of kprobe_blackpoint which is initialized for the function and put the address of the data structure