From: Wm <bill@boughton.org.uk>
To: xen-devel@lists.xensource.com
Subject: Re: kernel: attempt to access beyond end of device
Date: Sun, 29 May 2005 22:08:24 +0200 [thread overview]
Message-ID: <20050529200824.GA6722@yuri.org.uk> (raw)
In-Reply-To: <eda77ff805052709477891eebc@mail.gmail.com>
On Fri, May 27, 2005 at 05:47:07PM +0100, Sam Johnston wrote:
> Actually, yes - it is an LVM volume. Sorry - I should have specified
> that before. We'll have a closer look at the LVM config and see if we
> can't work out what's up.
I've seen this happen in dom0 with LVM but only with snapshots, and
the problem only seemed to manifest itself in domain0, when i
reexported the snapshot to a xenlinux instance i was able to
tar it all up.
I was also able to dd if=/dev/vg-disk/snapshot
of=/dev/vg-disk/notasnaphsotofthesamesae
Without any beyond end of device errors.
My domain0 is running 2.6.11.7, built with a snapshot from xen-2.0-testing
but with Xen 2.0.5.
Wm
next prev parent reply other threads:[~2005-05-29 20:08 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-27 16:43 kernel: attempt to access beyond end of device Ian Pratt
2005-05-27 16:47 ` Sam Johnston
2005-05-29 20:08 ` Wm [this message]
[not found] <73FE2FFB-F252-453C-BD68-E5036EC3EBF9@mosina.com.au>
2005-05-27 10:00 ` Sam Johnston
2005-05-27 11:29 ` Andrew Warfield
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=20050529200824.GA6722@yuri.org.uk \
--to=bill@boughton.org.uk \
--cc=xen-devel@lists.xensource.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.