public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: jfannin1@columbus.rr.com
To: Alasdair G Kergon <agk@redhat.com>,
	Mathieu Segaud <matt@minas-morgul.org>,
	jfannin1@columbus.rr.com, Christophe Saout <christophe@saout.de>,
	linux-kernel@vger.kernel.org, akpm@osdl.org, axboe@suse.de,
	bzolnier@gmail.com
Subject: Re: 2.6.9-mm1: LVM stopped working (dio-handle-eof.patch)
Date: Tue, 26 Oct 2004 17:37:04 -0400	[thread overview]
Message-ID: <20041026213703.GA6174@rivenstone.net> (raw)
In-Reply-To: <20041026135955.GA9937@agk.surrey.redhat.com>

On Tue, Oct 26, 2004 at 02:59:55PM +0100, Alasdair G Kergon wrote:
> On Tue, Oct 26, 2004 at 08:36:51AM -0400, jfannin1@columbus.rr.com wrote:
> > LVM doesn't work with 2.6.9-mm1 here either, complaining that it
> > can't find all the pv's. I'm not using any sort of encryption. Here,
> > pvdisplay reports:
> 
> > I can open the device nodes for the 'missing' pv's in a hexeditor and see the
> > uuid magic; if I reboot into 2.6.9-rc4-mm1 they are found without a
> > problem, and everything works.

> [To check for repeat of old problems with related symptoms:]
>   Were both kernels compiled with the same compiler version? Which version?
>   Does it make any difference if you rebuild lvm with --disable-o_direct?

    Chris Han (BCC'ed) mailed me to let me know he'd narrowed the
problem down to the 'dio-handle-eof.patch'.  Reverting it makes things
work for me too.  Yay!

> Firstly enable lvm debugging.  lvm.conf: log { file="/tmp/lvm2.log" level=7 }
> Compare the lvm log files for the kernels to see where it's going wrong.
> Then take complete straces (incl. read/write data) of the lvm process 
> with each kernel and again compare them. [Or put files on web and send URLs.]

vgchange -a y logs that it 'Failed to read label area' for the
'missing' pv's.

I've put up some possibly useful traces, but I think I've picked out
the relevant bits just below:
http://home.columbus.rr.com/jfannin1/vgchange-trace-good.txt
http://home.columbus.rr.com/jfannin1/vgchange-trace-bad.txt

Some (but not all) partitions opened are reading alternately (the -1024 is
constant): 

read(4, 0xbfffe600, 2048)               = ? ERESTARTSYS (To be restarted)
read(4, "\300;9\230", 2048)             = -1024

    If there's anything else that wants investigating, I'm still
willing as my free time allows.  Thanks!

-- 
Joseph Fannin
jfannin1@columbus.rr.com

  reply	other threads:[~2004-10-26 21:43 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-10-23 23:06 2.6.9-mm1: LVM stopped working Mathieu Segaud
2004-10-25 19:03 ` Christophe Saout
2004-10-25 22:31   ` Mathieu Segaud
2004-10-26 11:00   ` Mathieu Segaud
2004-10-26 12:36   ` jfannin1
2004-10-26 13:55     ` Jeff Chua
2004-10-26 14:09       ` Alasdair G Kergon
2004-10-26 13:59     ` Alasdair G Kergon
2004-10-26 21:37       ` jfannin1 [this message]
2004-10-26 22:15         ` 2.6.9-mm1: LVM stopped working (dio-handle-eof.patch) Andrew Morton
2004-10-27  4:36           ` Mathieu Segaud
2004-10-27  5:26             ` Andrew Morton
2004-10-27  5:47               ` Jens Axboe
2004-10-27  6:41                 ` Jens Axboe
2004-10-27 15:03                   ` Joseph Fannin
2004-10-27 15:29                     ` Alasdair G Kergon
2004-10-27 15:36                   ` Mathieu Segaud
2004-10-27 20:24                     ` Andrew Morton
2004-10-27 20:37                       ` Mathieu Segaud
2004-10-28  4:52                       ` Jeff Chua
2004-10-28 14:56                         ` Alasdair G Kergon
2004-10-29  4:58                           ` Jeff Chua
2004-10-29  5:31                             ` Bernd Eckenfels
2004-10-28 15:49                     ` Valdis.Kletnieks
2004-11-02 14:39                     ` Jens Axboe
2004-11-02 14:55                       ` Jens Axboe
2004-11-02 15:03                         ` Mathieu Segaud
2004-11-02 17:03                         ` Mathieu Segaud
2004-11-05  6:49                         ` Valdis.Kletnieks
2004-10-27 15:42                   ` Alasdair G Kergon
2004-10-27 18:13                     ` Jeff Chua
2004-10-26 14:00 ` 2.6.9-mm1: LVM stopped working Bartlomiej Zolnierkiewicz
2004-10-26 17:07   ` Bartlomiej Zolnierkiewicz
2004-10-26 17:21     ` Mathieu Segaud
2004-10-26 17:54     ` Mathieu Segaud
2004-10-26 18:04       ` Mathieu Segaud

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=20041026213703.GA6174@rivenstone.net \
    --to=jfannin1@columbus.rr.com \
    --cc=agk@redhat.com \
    --cc=akpm@osdl.org \
    --cc=axboe@suse.de \
    --cc=bzolnier@gmail.com \
    --cc=christophe@saout.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=matt@minas-morgul.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