Re: attempt to access beyond end of device

From: Andries Brouwer (aeb@veritas.com)
Date: Sat Sep 16 2000 - 12:08:01 EDT

  • Next message: Trond Myklebust: "Re: NFS locking bug -- limited mtime resolution means nfs_lock() does not provide coherency guarantee"

    On Sat, Sep 16, 2000 at 09:35:46AM -0400, Stephen E. Clark wrote:

    > How do I relate dev 08:02 to my actual physical devices. I have 2 ide
    > drives and 3 scsi drives.

    dev 08:02 is /dev/sda2, your swap device.

    > Sep 15 19:01:55 joker kernel: Adding Swap: 66020k swap-space (priority
    > -1)
    > Sep 15 19:01:55 joker kernel: Adding Swap: 52412k swap-space (priority
    > -2)
    > Sep 15 23:24:34 joker inetd[419]: pid 1458: exit status 1
    > Sep 15 23:53:48 joker kernel: attempt to access beyond end of device
    > Sep 15 23:53:48 joker kernel: 08:02: rw=1, want=40164, limit=40162
    > Sep 15 23:53:48 joker kernel: dev 08:02 blksize=4096 blocknr=10040
    > sector=80320 size=4096 count=1

    > /dev/hda3 swap swap defaults
    > /dev/sda2 swap swap defaults

    > /dev/hda3 251 381 66024 82 Linux swap
    > /dev/sda2 61 65 40162+ 82 Linux swap

    You see what happened:
    You added /dev/sda2, a device that has 40162 blocks,
    and told the kernel that it was good for 52412k swap space.

    I seem to recall that I once fixed this, in the sense that
    the kernel noticed a mismatch between the size of the swap device
    and what the swap header says - but maybe that was only for 2.4
    or perhaps it never got in - will check.
    In the meantime it seems that your problems will be fixed
    if you redo mkswap.

    Andries
    -
    To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
    the body of a message to majordomo@vger.kernel.org
    Please read the FAQ at http://www.tux.org/lkml/



    This archive was generated by hypermail 2b29 : Sat Sep 16 2000 - 12:09:51 EDT