linux-lvm.redhat.com archive mirror
 help / color / mirror / Atom feed
From: "Brian J. Murrell" <brian@interlinx.bc.ca>
To: LVM general discussion and development <linux-lvm@redhat.com>
Subject: [linux-lvm] snapshots filling and hanging up processes
Date: Tue, 21 Mar 2006 13:33:24 -0500	[thread overview]
Message-ID: <1142966004.18275.35.camel@pc> (raw)

[-- Attachment #1: Type: text/plain, Size: 1833 bytes --]

I am using LVM2 on FC4 (2.6.15-1.1831_FC4smp) and snapshots.  The
problem seems to be that when a snapshot fills up it craps out.  Trying
to extend it ends up hanging the lvextend process and a reboot is
needed.  After which though the snapshot is corrupted beyond repair.

While hung, lvextend's stack trace looks like:

lvextend      D ffff8100d1b00050     0 14786   7501               18185 (NOTLB)
ffff810105b7fc68 0000000000000086 ffff8101115afc00 ffffffff8016594c
       0000000000000000 0000000000000000 ffff81011748cbe8 0000000000000000
       0000000000000000 000000000001facf
Call Trace:<ffffffff8016594c>{wait_on_page_writeback_range+203}
       <ffffffff8806b694>{:dm_mod:dev_suspend+0} <ffffffff801650c7>{__filemap_fdatawrite_range+87}
       <ffffffff8806b694>{:dm_mod:dev_suspend+0} <ffffffff80357567>{__down_write+137}
       <ffffffff88067c0f>{:dm_mod:dm_suspend+368} <ffffffff80137e56>{default_wake_function+0}
       <ffffffff8035746c>{__down_read+50} <ffffffff8806b694>{:dm_mod:dev_suspend+0}
       <ffffffff8806b7b0>{:dm_mod:dev_suspend+284} <ffffffff8806a68c>{:dm_mod:ctl_ioctl+536}
       <ffffffff8019c84e>{do_ioctl+94} <ffffffff8019caf2>{vfs_ioctl+649}
       <ffffffff8019cb66>{sys_ioctl+91} <ffffffff8010fc60>{tracesys+209}

Trying to look at the volume in this state yields:

    # /usr/sbin/lvdisplay /dev/vg0/centos4.2-i386-boulder
[ I have to hit INTR here]
      CTRL-c detected: giving up waiting for lock
      /var/lock/lvm/V_vg0: flock failed: Interrupted system call
      Can't lock vg0: skipping

Is this a known issue (in this kernel or otherwise)?  Is it fixed in a
later FC kernel like kernel-2.6.15-1.1833_FC4.x86_64.rpm  or
kernel-2.6.15-1.2054_FC5.x86_64.rpm?

Thots?

b.

-- 
My other computer is your Microsoft Windows server.

Brian J. Murrell

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 191 bytes --]

             reply	other threads:[~2006-03-21 18:33 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-03-21 18:33 Brian J. Murrell [this message]
2006-03-21 19:24 ` [linux-lvm] snapshots filling and hanging up processes Alasdair G Kergon
2006-03-23 16:29   ` Mike Snitzer

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=1142966004.18275.35.camel@pc \
    --to=brian@interlinx.bc.ca \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).