From: Phil Dier <phil@icglink.com>
To: Neil Brown <neilb@cse.unsw.edu.au>
Cc: linux-kernel@vger.kernel.org, ziggy@icglink.com,
scott@icglink.com, jack@icglink.com
Subject: Re: 2.6.13-rc6 Oops with Software RAID, LVM, JFS, NFS
Date: Thu, 11 Aug 2005 23:17:20 -0500 [thread overview]
Message-ID: <20050811231720.3ecedcd9.phil@icglink.com> (raw)
In-Reply-To: <17148.1113.664829.360594@cse.unsw.edu.au>
On Fri, 12 Aug 2005 12:07:21 +1000
Neil Brown <neilb@cse.unsw.edu.au> wrote:
> On Thursday August 11, phil@icglink.com wrote:
> > Hi,
> >
> > I posted an oops a few days ago from 2.6.12.3 [1]. Here are the results
> > of my tests on 2.6.13-rc6. The kernel oopses, but it the box isn't completely
> > hosed; I can still log in and move around. It appears that the only things that are
> > locked are the apps that were doing i/o to the test partition. More detailed info
> > about my configuration can be found here:
> >
> > <http://www.icglink.com/debug-2.6.13-rc6.html>
>
> You don't seem to give details on how lvm is used to combine the md
> arrays, though I'm not sure that would help particularly.
>
FYI:
vgdisplay -v vg1
Using volume group(s) on command line
Finding volume group "vg1"
--- Volume group ---
VG Name vg1
System ID
Format lvm2
Metadata Areas 2
Metadata Sequence No 8
VG Access read/write
VG Status resizable
MAX LV 255
Cur LV 1
Open LV 0
Max PV 255
Cur PV 2
Act PV 2
VG Size 410.00 GB
PE Size 128.00 MB
Total PE 3280
Alloc PE / Size 1093 / 136.62 GB
Free PE / Size 2187 / 273.38 GB
VG UUID XuRomW-O6Uw-oQGq-vdwD-YwMT-Dltj-NExFmV
--- Logical volume ---
LV Name /dev/vg1/home
VG Name vg1
LV UUID K7Gq9l-Vjte-ksFt-s0vn-ejqT-RGYc-5Aibtx
LV Write Access read/write
LV Status available
# open 0
LV Size 136.62 GB
Current LE 1093
Segments 1
Allocation inherit
Read ahead sectors 0
Block device 253:3
--- Physical volumes ---
PV Name /dev/md4
PV UUID VgHU6k-lZmE-j686-dvfX-OSsM-yh28-Jyfidn
PV Status allocatable
Total PE / Free PE 1093 / 0
PV Name /dev/md7
PV UUID n4rVmy-rARO-a5mY-Iiqo-GvOx-2nbG-HluaTa
PV Status allocatable
Total PE / Free PE 2187 / 2187
md7 is in there to test live migration from smaller disks to larger ones.
>
> struct bio_vec *from;
> int i;
> bio_for_each_segment(from, bio, i)
> BUG_ON(page_zone(from->bv_page)==NULL);
>
> in generic_make_requst in drivers/block/ll_rw_blk.c, just before
> the call to q->make_request_fn.
> This might trigger the bug early enough to see what is happening.
I'll try this and report the results.
--
Phil Dier <phil@dier.us>
/* vim:set ts=8 sw=8 nocindent noai: */
next prev parent reply other threads:[~2005-08-12 4:17 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-11 15:59 2.6.13-rc6 Oops with Software RAID, LVM, JFS, NFS Phil Dier
2005-08-12 2:07 ` Neil Brown
2005-08-12 4:17 ` Phil Dier [this message]
2005-08-12 17:35 ` Phil Dier
2005-08-12 18:35 ` Sonny Rao
2005-08-15 2:03 ` Phil Dier
2005-08-15 2:40 ` Zwane Mwaikambo
2005-08-15 3:08 ` Robert Love
2005-08-15 3:20 ` Zwane Mwaikambo
2005-08-15 17:44 ` Phil Dier
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=20050811231720.3ecedcd9.phil@icglink.com \
--to=phil@icglink.com \
--cc=jack@icglink.com \
--cc=linux-kernel@vger.kernel.org \
--cc=neilb@cse.unsw.edu.au \
--cc=scott@icglink.com \
--cc=ziggy@icglink.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