All of lore.kernel.org
 help / color / mirror / Atom feed
From: Eric Sandeen <sandeen@sandeen.net>
To: willis@arlut.utexas.edu
Cc: linux-xfs@oss.sgi.com
Subject: Re: Attempt to Access Beyond End of Device
Date: Mon, 26 Apr 2010 15:54:10 -0500	[thread overview]
Message-ID: <4BD5FD72.2070106@sandeen.net> (raw)
In-Reply-To: <26132521.11272313223159.JavaMail.root@wombat>

On 04/26/2010 03:20 PM, willis@arlut.utexas.edu wrote:
> Federico Sevilla III wrote: "It wasn't an XFS-centric problem, after
> all"
> 
> Adding Federico's comment... Some Adadptec Controller firmware
> versions will pass incorrect device parameters to the linux kernel.
> The kernel log output misled me to believe is was a corrupt
> filesystem or partition map, however it was just an adaptec bug.
> 
> Adaptac has a fix procedure for this at:
> http://ask.adaptec.com/scripts/adaptec_tic.cfg/php.exe/enduser/std_adp.php?p_faqid=16914

Thanks for the followup; we've seen this a couple times, and it
has always stumped me.

-Eric

>  Below is the my kernel's dmesg output. After following Adaptec's
> procedure, the errors went away and I was able to mount the
> filesystem and see all of my existing data. ----- mount: /dev/sda:
> can't read superblock Mount Error at /dev/sdj. Is filesystem
> realtime? Need a File System? attempt to access beyond end of device 
> sda: rw=0, want=YYYY, limit=XXXX I/O error in filesystem ("sda")
> meta-data dev sdj block 0xZZZZ ("xfs_read_buf") error 5 buf count
> 512 XFS: size check 2 failed -----
> 
> Regards,
> 
> Michael Willis
> 
> 
> 
> 
> 
> -- Eric Sandeen wrote : Federico Sevilla III wrote:
>> 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.
> 
> can you send along the results of:
> 
> # xfs_db -r -c "sb 0" -c "print" /dev/sda8?
> 
> and # cat /proc/partitions
> 
> ... and does the hardware raid have a funky sector size?
> 
> -Eric
> 
> 
> 
> -- This message was sent on behalf of willis@arlut.utexas.edu at
> openSubscriber.com 
> http://www.opensubscriber.com/message/linux-xfs@oss.sgi.com/7550412.html
>
>  _______________________________________________ xfs mailing list 
> xfs@oss.sgi.com http://oss.sgi.com/mailman/listinfo/xfs
> 

_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs

  reply	other threads:[~2010-04-26 20:52 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-09-10 13:59 Attempt to Access Beyond End of Device Federico Sevilla III
2007-09-10 14:44 ` 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 [this message]
  -- 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=4BD5FD72.2070106@sandeen.net \
    --to=sandeen@sandeen.net \
    --cc=linux-xfs@oss.sgi.com \
    --cc=willis@arlut.utexas.edu \
    /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.