linux-lvm.redhat.com archive mirror
 help / color / mirror / Atom feed
From: "James G. Sack (jim)" <jsack@tandbergdatacorp.com>
To: "LVM LIST linux-lvm@redhat.com" <linux-lvm@redhat.com>
Cc: Alasdair G Kergon <agk@redhat.com>
Subject: Re: [linux-lvm] Sorry, dm:1.02, lvm2:2.02 did not work for me
Date: Tue, 15 Nov 2005 14:23:16 -0800	[thread overview]
Message-ID: <1132093397.4968.41.camel@jgs4.ino.pvt> (raw)
In-Reply-To: <1132073680.4968.3.camel@jgs4.ino.pvt>

On Tue, 2005-11-15 at 08:54 -0800, James G. Sack (jim) wrote: 
> On Sat, 2005-11-12 at 22:49 +0000, Alasdair G Kergon wrote: 
> > On Sat, Nov 12, 2005 at 10:03:21PM +0000, Alasdair G Kergon wrote:
> > > I've reproduced this if the LV is activated with an old release but
> > > the snapshot is created with the new code.  Should be easy to fix.
> >  
> > Try the current CVS versions.
... 
> Ok, I've grabbed the cvs images, done the configure/make/make install on
> dm and then lvm, and I now see:
> 
> lvm version
>   LVM version:     2.02.01-cvs (2005-11-10)
>   Library version: 1.02.01-cvs (2005-11-10)
>   Driver version:  4.4.0
> 
> I rebooted and reran my test procedure which 
> 1) loops on {lvcreate, sleep 10, lvremove, sleep 2}
> and simultaneously
> 2) loops on {cp abcd wxyz;cp wxyz abcd) 
> operating on a 1GB file on the origin filesystem
> 
> 
> The kcopyd.c BUG at line 145 is triggered by the first lvremove
> following start of the i/o (copy loop).
.. 
> ==> I will go rerun my test scenario on a new origin volume, to see if
> there's any differences.

Result with origin volume on new pv/vg/lv was same, namely: kcopyd.c BUG
at line 145 & oops.

Is there something else I can provide to assist in diagnostics?

hmmm- I thought I might simplify my test environment by removing all
older lvm devices, so I pulled disks containing 3 other pv's. Then I was
getting another scsi read error so I pulled that disk (<heh> I have a 9-
disk NAS I'm playing on, in case anyone's wondering)

Then after reboot, and rerun of my test procedure, I still get the same
behavior --except that it now seems to lockup hard -- no ssh, no ping,
no console scrollback, no keyboard (although sysrq works), no
dmesg/syslog output. There *is* console screen output, ending with what
looks like the trailing part of the oops calltrace. Is it worth
configuring a serial console in order to capture this? (Or can someone
tell me how to capture it otherwise?)

Regards.
..jim

  parent reply	other threads:[~2005-11-15 22:23 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20051111163525.18AE1734B1@hormel.redhat.com>
2005-11-12  1:13 ` [linux-lvm] Sorry, dm:1.02, lvm2:2.02 did not work for me James G. Sack (jim)
2005-11-12  2:07   ` Alasdair G Kergon
2005-11-12 22:03     ` Alasdair G Kergon
2005-11-12 22:49       ` Alasdair G Kergon
2005-11-14 22:32         ` James G. Sack (jim)
     [not found]         ` <1132073680.4968.3.camel@jgs4.ino.pvt>
2005-11-15 22:23           ` James G. Sack (jim) [this message]
2005-11-15 22:33             ` Alasdair G Kergon
2005-11-15 23:46             ` Alasdair G Kergon
2005-11-15 23:50             ` Alasdair G Kergon

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=1132093397.4968.41.camel@jgs4.ino.pvt \
    --to=jsack@tandbergdatacorp.com \
    --cc=agk@redhat.com \
    --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).