All of lore.kernel.org
 help / color / mirror / Atom feed
From: Federico Sevilla III <jijo@fs3.ph>
To: linux-xfs@oss.sgi.com
Cc: Alec Joseph Rivera <agi@fs3.ph>
Subject: Attempt to Access Beyond End of Device
Date: Mon, 10 Sep 2007 21:59:07 +0800	[thread overview]
Message-ID: <1189432747.4385.27.camel@auctoritas.fs3.ph> (raw)

[-- Attachment #1: Type: text/plain, Size: 2349 bytes --]

Hi,

We've set up Debian GNU/Linux 4.0 "Etch" on an IBM x3400 machine with
two 73.4GB SAS hard drives in hardware RAID 1 with a battery-backed
cache. We are using the stock Debian 2.6.18-4-686 kernel.

The filesystems were created using the following optimization:

        -l size=32768b,version=2 -n 64k

The filesystems are mounted using the following optimization:

        logbufs=8,logbsize=256k

Today, we were unable to mount the "large" (not really at < 70GB) /var
(/dev/sda8), getting the following error:

        Attempt to access beyond end of device
        sda: rw=0, want=143139140, limit=143134720
        I/O error in filesystem ("sda8") meta-data dev sda8 block
        0x75cd27f
        ("xf:read_buf") errors buf count 512
        XFS: size check 2 failed
        Mount: /dev/sda8: can't read superblock

An attempted repair also fails:

        # xfs_repair /dev/sda8
        Phase 1 - find and verify superblock...
        Attempt to access beyond end of device
        Sda: rw=0, want=143139140, limit=143134720
        Xfs_repair: read failed.      Input/output error

The partition table looks okay:

        #Partition table of /dev/sda
        /dev/sda1 : start=          63,size        9637, Id=83, bootable
        /dev/sda2 : start=       96390,size   143042760, Id=5
        /dev/sda3 : start=           0,size           0, Id=0
        /dev/sda4 : start=           0,size           0, Id=0   
        /dev/sda5 : start=       96453,size     3903732, Id=82
        /dev/sda6 : start=     4000248,size     7807527, Id=83
        /dev/sda7 : start=    11807838,size     7807527, Id=83
        /dev/sda8 : start=    19615428,size   123523722, Id=83

The machine doesn't have valuable data, yet, so a simple reinstall
should help get it back up. However I'm more concerned about what could
cause this. It's the first time for me to use a version 2 log, 64k
directories (?) and 256k in-memory log buffers. Are any of these to
blame?

We're also looking for generic filesystem tweaks for a PostgreSQL +
Apache server, which this will be (with more load direct to PostgreSQL
than to/through Apache). Are the above choices for mkfs.xfs and mount
well-made?

Please advise.

Thank you very much.

-- 
Federico Sevilla III
F S 3 Consulting Inc.
http://www.fs3.ph

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

             reply	other threads:[~2007-09-10 14:24 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-09-10 13:59 Federico Sevilla III [this message]
2007-09-10 14:44 ` Attempt to Access Beyond End of Device Justin Piszcz
2007-09-10 14:59   ` Federico Sevilla III
2007-09-10 15:45     ` Justin Piszcz
2007-09-10 15:51       ` Federico Sevilla III
2007-09-10 15:47 ` Eric Sandeen
2007-09-10 15:54   ` Federico Sevilla III
2007-09-10 16:28     ` Eric Sandeen
     [not found]       ` <cc7060690709111208u3e0842f9rd6edff16539b8a28@mail.gmail.com>
2007-09-12  5:17         ` Federico Sevilla III
2010-04-26 20:20   ` willis
2010-04-26 20:54     ` Eric Sandeen
  -- strict thread matches above, loose matches on Subject: below --
2014-03-24  7:13 attempt to access beyond end of device Piotr Szymaniak
2014-03-24  7:37 ` Vyacheslav Dubeyko
2014-03-24 20:49   ` Piotr Szymaniak
2014-03-25  9:18     ` Vyacheslav Dubeyko
2014-03-27 12:39       ` Piotr Szymaniak
2014-03-29 14:49         ` Vyacheslav Dubeyko
2014-03-24 22:31   ` Piotr Szymaniak
2006-12-05 14:01 Koen Vereeken
2006-01-19 12:02 Handling of read errors in raid6 Filipe Maia
2006-01-19 20:39 ` attempt to access beyond end of device PFC
2004-04-13 10:03 Luca Ferrari
2004-04-13 10:41 ` Thomas Steudten
2004-04-13 11:08   ` Luca Ferrari
2004-04-13 11:20     ` Thomas Steudten
2004-04-13 11:45       ` Luca Ferrari
2004-04-13 12:44         ` Thomas Steudten
2004-04-13 12:53           ` Luca Ferrari
2002-12-06  5:21 Justin Pryzby
2002-12-05 18:54 Justin Pryzby
2000-12-07 15:56 Jan Niehusmann
2000-12-07 16:34 ` Andries Brouwer
2000-12-07 17:10   ` John Kennedy
2000-11-24  9:02 Janek

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=1189432747.4385.27.camel@auctoritas.fs3.ph \
    --to=jijo@fs3.ph \
    --cc=agi@fs3.ph \
    --cc=linux-xfs@oss.sgi.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.