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: Mon, 14 Feb 2011 13:11:49 +1100 [thread overview]
Message-ID: <20110214131149.7f0655a3@notabene.brown> (raw)
In-Reply-To: <BE2BFE91933D1B4089447C644860408068C4429D@irsmsx503.ger.corp.intel.com>
On Wed, 9 Feb 2011 14:33:01 +0000 "Wojcik, Krzysztof"
<krzysztof.wojcik@intel.com> wrote:
>
> Steps to reproduce:
> 1. Create partition on disk (for example: 1 partition, size=half of /dev/sda disk)
> 2. Create filesystem on partition (ext3)
> 3. Mount partition and create some control data on partition
> 4. Unmount partition
> 5. Create RAID0 on disk (mdadm -C /dev/md/vol_1 -amd -e 0.9 -c 64 -l 0 -n 1 /dev/sda --force)
> 6. md127 and md127p1 appears in /dev as expected
> 7. Try to mount md127p1 and verify control data on them
I couldn't get this to fail for me.
It is possible that there is something subtle about the precise device
geometry.
Could you send me
sfdisk -l /dev/sda
(or whatever device you are using)
However when I ran the script without requesting native metadata I did
get some results somewhat similar to yours - and they were not consistent
which is an important similarity.
This patch should fix that particular problem. Let me know if you
can still produce any of these errors with the patch applied.
Thanks,
NeilBrown
diff --git a/drivers/md/md.c b/drivers/md/md.c
index 0cc30ec..6818ff4 100644
--- a/drivers/md/md.c
+++ b/drivers/md/md.c
@@ -4138,10 +4138,10 @@ array_size_store(mddev_t *mddev, const char *buf, size_t len)
}
mddev->array_sectors = sectors;
- set_capacity(mddev->gendisk, mddev->array_sectors);
- if (mddev->pers)
+ if (mddev->pers) {
+ set_capacity(mddev->gendisk, mddev->array_sectors);
revalidate_disk(mddev->gendisk);
-
+ }
return len;
}
next prev parent reply other threads:[~2011-02-14 2:11 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 [this message]
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
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=20110214131149.7f0655a3@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).