From: Alasdair G Kergon <agk@redhat.com>
To: foo@porto.bmb.uga.edu
Cc: Andrew Morton <akpm@osdl.org>, linux-kernel@vger.kernel.org
Subject: Re: processes hung in D (raid5/dm/ext3)
Date: Wed, 16 Jun 2004 13:57:54 +0100 [thread overview]
Message-ID: <20040616125754.GF6627@agk.surrey.redhat.com> (raw)
In-Reply-To: <20040616021633.GB13672@porto.bmb.uga.edu>
On Tue, Jun 15, 2004 at 10:16:33PM -0400, foo@porto.bmb.uga.edu wrote:
> # pvdisplay /dev/md0
> # vgdisplay vg0
> # lvdisplay
LVM2/device-mapper diagnostics
==============================
If you use the 'lvs' reporting tool, we'll get fuller information more
concisely, so we can check for any anomalies.
[Unlikely to be any based on what you've posted so far, but worth
eliminating the possibility.]
Run:
vgs -v
lvs -v
pvs -v
Can you confirm that you're not running *any* LVM or device-mapper
commands during your backup sequence?
Confirm the versions by running:
lvm version
dmsetup targets
And dump the static device-mapper state, by running:
dmsetup -v table
dmsetup status
[I'll get that fixed to provide a column-based output too.]
And finally mount sysfs and run
ls -ld .../block/dm-*
[This lot ought to get scripted.]
Alasdair
--
agk@redhat.com
next prev parent reply other threads:[~2004-06-16 13:04 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-15 6:22 foo
2004-06-15 10:09 ` Andrew Morton
2004-06-15 15:00 ` foo
2004-06-15 23:26 ` Andrew Morton
2004-06-15 23:44 ` Evaldo Gardenali
2004-06-16 2:03 ` foo
2004-06-16 2:16 ` foo
2004-06-16 12:57 ` Alasdair G Kergon [this message]
2004-06-16 19:00 ` foo
2004-06-16 19:15 ` Alasdair G Kergon
2004-06-17 2:28 ` foo
2004-06-16 2:48 ` foo
2004-06-16 2:58 ` Andrew Morton
2004-06-16 3:55 ` foo
2004-06-16 4:13 ` foo
2004-06-16 4:25 ` Andrew Morton
2004-06-16 4:41 ` foo
2004-06-16 4:53 ` linux-kernel-owner
2004-06-16 7:22 ` tg3 wrong speed foo
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=20040616125754.GF6627@agk.surrey.redhat.com \
--to=agk@redhat.com \
--cc=akpm@osdl.org \
--cc=foo@porto.bmb.uga.edu \
--cc=linux-kernel@vger.kernel.org \
/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
all inboxes | Powered by JetHome®