All of lore.kernel.org
 help / color / mirror / Atom feed
From: Rolf Eike Beer <eike-kernel@sf-tec.de>
To: linux-lvm@redhat.com
Cc: linux-kernel@vger.kernel.org
Subject: Re: [linux-lvm] 2.6.37.2: LVM pvmove hangs system
Date: Tue, 8 Mar 2011 14:49:44 +0100	[thread overview]
Message-ID: <201103081449.44783.eike-kernel@sf-tec.de> (raw)
In-Reply-To: <201103081038.38338.eike-kernel@sf-tec.de>

Am Dienstag 08 M�rz 2011, 10:38:38 schrieb Rolf Eike Beer:
> Hi all,
> 
> I'm experiencing a very annoying system lockup for some days. The setup is
> as follows:
> 
> -two pairs of SATA disks that are bundled into a software raid 1 each
> -each of the raid devices is a physical volume
> -a volume group that includes both pv's
> -all mounted volumes (including root and swap) are in that vg
> 
> The machine is a Xeon E5520 with 16G RAM that is otherwise idle, so swap
> shouldn't matter. And from what I read out of the documentation this all
> looks perfectly sane, but:
> 
> Now I try to move the data from one pv to the other using pv. This prints
> out the current state (currently 10.9%) and then starts doing something.
> Two minutes later the kernel will complain:

After some further testing I _think_ I have an idea what's going on: this is a 
deadlock somewhere in the I/O stack. I have recompiled the kernel with all the 
lock debugging enabled and will probably test this but this is a production 
machine that should better get online again better sooner than later so my 
amount of what I can test is pretty limited. Since the machine is currently 
doing the move and actually working I have not yet booted into the debug 
kernel.

What I did was basically stopping everything on the machine. The only 
userspace programs currently running are init, my sshd, my screen, shell, and 
of course pvmove. And now it works. Whenever I try to do anything that causes 
I/O in parallel the machine will stop working. So this box is basically at 
runlevel 1 now moving all the stuff around instead of doing some useful work 
while moving in the background :(

Eike

WARNING: multiple messages have this Message-ID (diff)
From: Rolf Eike Beer <eike-kernel@sf-tec.de>
To: linux-lvm@redhat.com
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.6.37.2: LVM pvmove hangs system
Date: Tue, 8 Mar 2011 14:49:44 +0100	[thread overview]
Message-ID: <201103081449.44783.eike-kernel@sf-tec.de> (raw)
In-Reply-To: <201103081038.38338.eike-kernel@sf-tec.de>

Am Dienstag 08 März 2011, 10:38:38 schrieb Rolf Eike Beer:
> Hi all,
> 
> I'm experiencing a very annoying system lockup for some days. The setup is
> as follows:
> 
> -two pairs of SATA disks that are bundled into a software raid 1 each
> -each of the raid devices is a physical volume
> -a volume group that includes both pv's
> -all mounted volumes (including root and swap) are in that vg
> 
> The machine is a Xeon E5520 with 16G RAM that is otherwise idle, so swap
> shouldn't matter. And from what I read out of the documentation this all
> looks perfectly sane, but:
> 
> Now I try to move the data from one pv to the other using pv. This prints
> out the current state (currently 10.9%) and then starts doing something.
> Two minutes later the kernel will complain:

After some further testing I _think_ I have an idea what's going on: this is a 
deadlock somewhere in the I/O stack. I have recompiled the kernel with all the 
lock debugging enabled and will probably test this but this is a production 
machine that should better get online again better sooner than later so my 
amount of what I can test is pretty limited. Since the machine is currently 
doing the move and actually working I have not yet booted into the debug 
kernel.

What I did was basically stopping everything on the machine. The only 
userspace programs currently running are init, my sshd, my screen, shell, and 
of course pvmove. And now it works. Whenever I try to do anything that causes 
I/O in parallel the machine will stop working. So this box is basically at 
runlevel 1 now moving all the stuff around instead of doing some useful work 
while moving in the background :(

Eike

  reply	other threads:[~2011-03-08 13:50 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-08  9:38 [linux-lvm] 2.6.37.2: LVM pvmove hangs system Rolf Eike Beer
2011-03-08  9:38 ` Rolf Eike Beer
2011-03-08 13:49 ` Rolf Eike Beer [this message]
2011-03-08 13:49   ` Rolf Eike Beer
2011-03-08 17:20 ` [linux-lvm] " Ray Morris

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=201103081449.44783.eike-kernel@sf-tec.de \
    --to=eike-kernel@sf-tec.de \
    --cc=linux-kernel@vger.kernel.org \
    --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.