From: Andy Smith <andy@lug.org.uk>
To: linux-raid <linux-raid@vger.kernel.org>
Subject: Re: raid10_make_request bug: can't convert block across chunks or bigger [...]
Date: Sat, 7 Apr 2007 04:28:53 +0000 [thread overview]
Message-ID: <20070407042853.GV2737@bitfolk.com> (raw)
In-Reply-To: <20070407031027.GT2737@bitfolk.com>
[-- Attachment #1: Type: text/plain, Size: 1114 bytes --]
Sorry for the reply to self, but the last thing I tried has provided
some more info:
On Sat, Apr 07, 2007 at 03:10:27AM +0000, Andy Smith wrote:
> I'm now seeing the exact same problem as Ask did in:
>
> http://www.mail-archive.com/linux-raid@vger.kernel.org/msg06762.html
>
> again using md raid10 under LVM, trying to export an LV to a xen
> domain.
This LV was initially created as 512M in size. I extended it to 1G
and experienced the same thing. I then created a new LV of size 2G,
copied the contents of the first LV to the second, and used that as
the domain's root filesystem. I no longer get this problem.
I then deleted the original LV and renamed the new LV to the name of
the original and things still work. I am able to do:
dd if=/dev/sda1 of=/dev/null
in the Xen domain and not receive any errors so I have to conclude
that all blocks of this second LV are readable. So is this an issue
of the layout of the LVM extents on disk? Will I get this problem
again? Should I be pursuing this on the LVM list, here, or maybe
even with the Xen folks?
Cheers,
Andy
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2007-04-07 4:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-07 3:10 raid10_make_request bug: can't convert block across chunks or bigger [...] Andy Smith
2007-04-07 4:28 ` Andy Smith [this message]
-- strict thread matches above, loose matches on Subject: below --
2007-01-03 6:46 Ask Bjørn Hansen
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=20070407042853.GV2737@bitfolk.com \
--to=andy@lug.org.uk \
--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).