From: Georges Giralt <georges.giralt@free.fr>
To: LVM general discussion and development <linux-lvm@redhat.com>
Subject: Re: [linux-lvm] Large LVM leading to e2fsck segfault
Date: Wed, 25 Apr 2007 06:22:32 +0200 [thread overview]
Message-ID: <462ED788.8080804@free.fr> (raw)
In-Reply-To: <20070424232330.GA29984@esri.com>
Hi Ray !
Ray Van Dolson a �crit :
> Hello everyone -- got a CentOS 4.4 (x86_64) machine running a ~9TB LVM.
> We initially had problems with the LVM under 32-bit CentOS 4 so we
> upgraded to 64-bit CentOS. The LVM was originally created under the
> 32-bit environment however.
>
> # uname -a
> Linux rmanbackup 2.6.9-42.0.10.ELsmp #1 SMP Tue Feb 27 09:40:21 EST 2007 x86_64 x86_64 x86_64 GNU/Linux
>
> It worked fine for a few days, but we began seeing errors such as the
> following:
>
> Apr 23 12:19:59 rmanbackup kernel: attempt to access beyond end of device
> Apr 23 12:19:59 rmanbackup kernel: dm-0: rw=0, want=34359738368, limit=20507254784
> Apr 23 12:19:59 rmanbackup kernel: attempt to access beyond end of device
> Apr 23 12:19:59 rmanbackup kernel: dm-0: rw=0, want=34359738368, limit=20507254784
>
> Sure enough:
>
> # blockdev --getsize /dev/backup0/backup
> 20507254784
Some time ago, we had similar messages on a plain (no LVM) 1 TB Raid 5
array plugged to a Redhat derivative box.
It was due to the raid controler going south.
Try to check the array using the tools the card manufacturer give. You
may be surprised.
This is just my 2�
--
Ce message est constitu� d'au moins 50 % d'�lectrons recycl�s.
S'il vous pla�t, aidez nous � conserver nos ressources,
recyclez vos �lectrons !
prev parent reply other threads:[~2007-04-25 4:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-24 23:23 [linux-lvm] Large LVM leading to e2fsck segfault Ray Van Dolson
2007-04-25 4:22 ` Georges Giralt [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=462ED788.8080804@free.fr \
--to=georges.giralt@free.fr \
--cc=linux-lvm@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.