kernel: attempt to access beyond end of device

kernel: attempt to access beyond end of device

[Sam Johnston]

Morning all,

I received this mail this morning from an admin regarding a xen guest
(newlists). It would seem that the filesystem is larger than its
container?

Before I spend too long looking at it, does anyone have any ideas as
to how this may have occurred and how it could be fixed?

Kind regards,

Sam

=========================================
---------- Forwarded message ----------
From: <snip>
Date: May 26, 2005 10:14 PM
Subject: problems with newlists
To: Sam Johnston <samjie@gmail.com>


Hi Sam,

I'm getting the following errors on newlists:

May 26 21:08:41 newlists kernel: attempt to access beyond end of device
May 26 21:08:41 newlists kernel: sda1: rw=0, want=4294875368,
limit=5120000
May 26 21:08:41 newlists kernel: attempt to access beyond end of device
May 26 21:08:41 newlists kernel: sda1: rw=0, want=1516641296,
limit=5120000
May 26 21:08:41 newlists kernel: attempt to access beyond end of device
May 26 21:08:41 newlists kernel: sda1: rw=0, want=2890399776,
limit=5120000
May 26 21:08:41 newlists kernel: attempt to access beyond end of device
May 26 21:08:41 newlists kernel: sda1: rw=0, want=133959624,
limit=5120000
May 26 21:08:58 newlists kernel: attempt to access beyond end of device
May 26 21:08:58 newlists kernel: sda1: rw=0, want=4294875368,
limit=5120000
May 26 21:08:58 newlists kernel: attempt to access beyond end of device
May 26 21:08:58 newlists kernel: sda1: rw=0, want=1516641296,
limit=5120000
May 26 21:08:58 newlists kernel: attempt to access beyond end of device
May 26 21:08:58 newlists kernel: sda1: rw=0, want=2890399776,
limit=5120000
May 26 21:08:58 newlists kernel: attempt to access beyond end of device
May 26 21:08:58 newlists kernel: sda1: rw=0, want=133959624,
limit=5120000

Could you please have a look and let me know what you think... I'm
not hoping for much :-(
=========================================

Re: kernel: attempt to access beyond end of device

[Andrew Warfield]

The filesystem on the disk thinks that the disk is bigger than the
backend domain does.  Can you provide some details on the disk that
they are trying to mount, like the disk line out of the config file? 
How was the image that they are trying to mount created?

a.

On 5/27/05, Sam Johnston <samjie@gmail.com> wrote:
> Morning all,
> 
> I received this mail this morning from an admin regarding a xen guest
> (newlists). It would seem that the filesystem is larger than its
> container?
> 
> Before I spend too long looking at it, does anyone have any ideas as
> to how this may have occurred and how it could be fixed?
> 
> Kind regards,
> 
> Sam
> 
> =========================================
> ---------- Forwarded message ----------
> From: <snip>
> Date: May 26, 2005 10:14 PM
> Subject: problems with newlists
> To: Sam Johnston <samjie@gmail.com>
> 
> 
> Hi Sam,
> 
> I'm getting the following errors on newlists:
> 
> May 26 21:08:41 newlists kernel: attempt to access beyond end of device
> May 26 21:08:41 newlists kernel: sda1: rw=0, want=4294875368,
> limit=5120000
> May 26 21:08:41 newlists kernel: attempt to access beyond end of device
> May 26 21:08:41 newlists kernel: sda1: rw=0, want=1516641296,
> limit=5120000
> May 26 21:08:41 newlists kernel: attempt to access beyond end of device
> May 26 21:08:41 newlists kernel: sda1: rw=0, want=2890399776,
> limit=5120000
> May 26 21:08:41 newlists kernel: attempt to access beyond end of device
> May 26 21:08:41 newlists kernel: sda1: rw=0, want=133959624,
> limit=5120000
> May 26 21:08:58 newlists kernel: attempt to access beyond end of device
> May 26 21:08:58 newlists kernel: sda1: rw=0, want=4294875368,
> limit=5120000
> May 26 21:08:58 newlists kernel: attempt to access beyond end of device
> May 26 21:08:58 newlists kernel: sda1: rw=0, want=1516641296,
> limit=5120000
> May 26 21:08:58 newlists kernel: attempt to access beyond end of device
> May 26 21:08:58 newlists kernel: sda1: rw=0, want=2890399776,
> limit=5120000
> May 26 21:08:58 newlists kernel: attempt to access beyond end of device
> May 26 21:08:58 newlists kernel: sda1: rw=0, want=133959624,
> limit=5120000
> 
> Could you please have a look and let me know what you think... I'm
> not hoping for much :-(
> =========================================
> 
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel
>

RE: kernel: attempt to access beyond end of device

[Ian Pratt]

 
> I received this mail this morning from an admin regarding a 
> xen guest (newlists). It would seem that the filesystem is 
> larger than its container?
> 
> Before I spend too long looking at it, does anyone have any 
> ideas as to how this may have occurred and how it could be fixed?

The accesses seem to be way, way, beyond the end of the device e.g.
want=4294875368, limit=5120000.

I forget what the units are, but this doesn't look good.

Is this an LVM volume? has it been resized? What does blockdev --getsize
show for the volume? Does it agree with the lvm tools?

Ian


 
> Kind regards,
> 
> Sam
> 
> =========================================
> ---------- Forwarded message ----------
> From: <snip>
> Date: May 26, 2005 10:14 PM
> Subject: problems with newlists
> To: Sam Johnston <samjie@gmail.com>
> 
> 
> Hi Sam,
> 
> I'm getting the following errors on newlists:
> 
> May 26 21:08:41 newlists kernel: attempt to access beyond end 
> of device May 26 21:08:41 newlists kernel: sda1: rw=0, 
> want=4294875368, limit=5120000 May 26 21:08:41 newlists 
> kernel: attempt to access beyond end of device May 26 
> 21:08:41 newlists kernel: sda1: rw=0, want=1516641296, 
> limit=5120000 May 26 21:08:41 newlists kernel: attempt to 
> access beyond end of device May 26 21:08:41 newlists kernel: 
> sda1: rw=0, want=2890399776, limit=5120000 May 26 21:08:41 
> newlists kernel: attempt to access beyond end of device May 
> 26 21:08:41 newlists kernel: sda1: rw=0, want=133959624, 
> limit=5120000 May 26 21:08:58 newlists kernel: attempt to 
> access beyond end of device May 26 21:08:58 newlists kernel: 
> sda1: rw=0, want=4294875368, limit=5120000 May 26 21:08:58 
> newlists kernel: attempt to access beyond end of device May 
> 26 21:08:58 newlists kernel: sda1: rw=0, want=1516641296, 
> limit=5120000 May 26 21:08:58 newlists kernel: attempt to 
> access beyond end of device May 26 21:08:58 newlists kernel: 
> sda1: rw=0, want=2890399776, limit=5120000 May 26 21:08:58 
> newlists kernel: attempt to access beyond end of device May 
> 26 21:08:58 newlists kernel: sda1: rw=0, want=133959624, limit=5120000
> 
> Could you please have a look and let me know what you 
> think... I'm not hoping for much :-( 
> =========================================
> 
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel
> 

Re: kernel: attempt to access beyond end of device

[Sam Johnston]

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.

sj

On 5/27/05, Ian Pratt <m+Ian.Pratt@cl.cam.ac.uk> wrote:
> 
> > I received this mail this morning from an admin regarding a
> > xen guest (newlists). It would seem that the filesystem is
> > larger than its container?
> >
> > Before I spend too long looking at it, does anyone have any
> > ideas as to how this may have occurred and how it could be fixed?
> 
> The accesses seem to be way, way, beyond the end of the device e.g.
> want=4294875368, limit=5120000.
> 
> I forget what the units are, but this doesn't look good.
> 
> Is this an LVM volume? has it been resized? What does blockdev --getsize
> show for the volume? Does it agree with the lvm tools?
> 
> Ian
> 
> 
> 
> > Kind regards,
> >
> > Sam
> >
> > =========================================
> > ---------- Forwarded message ----------
> > From: <snip>
> > Date: May 26, 2005 10:14 PM
> > Subject: problems with newlists
> > To: Sam Johnston <samjie@gmail.com>
> >
> >
> > Hi Sam,
> >
> > I'm getting the following errors on newlists:
> >
> > May 26 21:08:41 newlists kernel: attempt to access beyond end
> > of device May 26 21:08:41 newlists kernel: sda1: rw=0,
> > want=4294875368, limit=5120000 May 26 21:08:41 newlists
> > kernel: attempt to access beyond end of device May 26
> > 21:08:41 newlists kernel: sda1: rw=0, want=1516641296,
> > limit=5120000 May 26 21:08:41 newlists kernel: attempt to
> > access beyond end of device May 26 21:08:41 newlists kernel:
> > sda1: rw=0, want=2890399776, limit=5120000 May 26 21:08:41
> > newlists kernel: attempt to access beyond end of device May
> > 26 21:08:41 newlists kernel: sda1: rw=0, want=133959624,
> > limit=5120000 May 26 21:08:58 newlists kernel: attempt to
> > access beyond end of device May 26 21:08:58 newlists kernel:
> > sda1: rw=0, want=4294875368, limit=5120000 May 26 21:08:58
> > newlists kernel: attempt to access beyond end of device May
> > 26 21:08:58 newlists kernel: sda1: rw=0, want=1516641296,
> > limit=5120000 May 26 21:08:58 newlists kernel: attempt to
> > access beyond end of device May 26 21:08:58 newlists kernel:
> > sda1: rw=0, want=2890399776, limit=5120000 May 26 21:08:58
> > newlists kernel: attempt to access beyond end of device May
> > 26 21:08:58 newlists kernel: sda1: rw=0, want=133959624, limit=5120000
> >
> > Could you please have a look and let me know what you
> > think... I'm not hoping for much :-(
> > =========================================
> >
> > _______________________________________________
> > Xen-devel mailing list
> > Xen-devel@lists.xensource.com
> > http://lists.xensource.com/xen-devel
> >
>

Re: kernel: attempt to access beyond end of device

[Wm]

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