From: NeilBrown <neilb@suse.de>
To: "Wojcik, Krzysztof" <krzysztof.wojcik@intel.com>
Cc: "linux-raid@vger.kernel.org" <linux-raid@vger.kernel.org>
Subject: Re: Single-drive RAID0
Date: Thu, 17 Feb 2011 11:38:48 +1100 [thread overview]
Message-ID: <20110217113848.17673231@notabene.brown> (raw)
In-Reply-To: <BE2BFE91933D1B4089447C644860408069028F47@irsmsx503.ger.corp.intel.com>
On Wed, 16 Feb 2011 16:57:06 +0000 "Wojcik, Krzysztof"
<krzysztof.wojcik@intel.com> wrote:
> >
> > It looks like the 'bdev' passed to md_open keeps changing, which it
> > shouldn't.
> >
> > If the above doesn't help, please add:
> >
> > printk("bdev=%p, mddev=%p, disk=%p dev=%x\n", bdev, mddev, mddev-
> > >gendisk, bdev->bd_dev);
> >
> > at the top of 'md_open', and see what it produces.
>
> I tried this also but I can't see any useful information that can make me some idea.
> Could you look at logs in attachment?
>
Thanks.
That at-least confirms that the bdev is often changing while the mddev and
disk stay unchanged. Having that confirmation is useful..
I didn't think that could happen - the bdev should remain pinned while the
mddev exists. Obviously it doesn't.
I'll see what I can find out.
NeilBrown
next prev parent reply other threads:[~2011-02-17 0:38 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-08 16:15 Single-drive RAID0 Wojcik, Krzysztof
2011-02-09 2:45 ` NeilBrown
2011-02-09 14:33 ` Wojcik, Krzysztof
2011-02-14 2:11 ` NeilBrown
2011-02-14 17:04 ` Wojcik, Krzysztof
2011-02-15 0:01 ` NeilBrown
2011-02-15 16:30 ` Wojcik, Krzysztof
2011-02-16 0:42 ` NeilBrown
2011-02-16 16:57 ` Wojcik, Krzysztof
2011-02-17 0:38 ` NeilBrown [this message]
2011-02-21 2:15 ` NeilBrown
2011-02-21 14:11 ` Wojcik, Krzysztof
2011-02-22 0:50 ` NeilBrown
2011-02-22 11:50 ` Wojcik, Krzysztof
2011-02-22 16:42 ` Jan Ceuleers
2011-02-23 2:20 ` NeilBrown
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=20110217113848.17673231@notabene.brown \
--to=neilb@suse.de \
--cc=krzysztof.wojcik@intel.com \
--cc=linux-raid@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;
as well as URLs for NNTP newsgroup(s).