From: Dave Chinner <david@fromorbit.com>
To: Christian Kildau <lists@unixhosts.org>
Cc: xfs@oss.sgi.com
Subject: Re: How to fix bad superblock or xfs_repair: error - read only 0 of 512 bytes
Date: Mon, 23 Jan 2012 15:31:17 +1100 [thread overview]
Message-ID: <20120123043117.GH15102@dastard> (raw)
In-Reply-To: <CALx8gnT9tdPRGfVR0puoSVYz_MDDs4FtWtodST5x29GDnL3A_w@mail.gmail.com>
On Sat, Jan 21, 2012 at 11:29:15AM +0100, Christian Kildau wrote:
> Sorry if this message appears twice!
>
>
>
> Hello,
>
> I'm having some very serious issues with XFS after upgrading from a
> Linux Distro running Ubuntu 2.6.32 to 3.2.
>
> It seems like my filesystems are damaged after attaching them to a
> Linux 3.2 server. I am also no longer able to mount the hdd on the old
> server that is still running 2.6.32!
I take it that you are using external storage of some kind? Can you
describe it?
> (I created the xfs filesystem on the entire hdd, not on a partition,
> so /dev/sdd is not a typo)
>
> $ sudo mount -t xfs /dev/sdd /media/
> mount: /dev/sdd: can't read superblock
> (dmesg)
> [236659.912663] attempt to access beyond end of device
> [236659.912667] sdd: rw=32, want=2930277168, limit=2930275055
> [236659.912670] XFS (sdd): last sector read failed
So XFS has asked to read 2113 sectors beyond the size of the device
that the kernel is reporting. What is the output of
/proc/partitions?
> $ sudo xfs_check /dev/sdd
> xfs_check: error - read only 0 of 512 bytes
>
> $ sudo xfs_repair /dev/sdd
> Phase 1 - find and verify superblock...
> xfs_repair: error - read only 0 of 512 bytes
So both buffered and direct IO to the first block in the block
device are failing. I'd say your problems have nothing to do with
XFS. However, can you strace them and find out what the error that
is occuring actually is?
Cheers,
Dave.
--
Dave Chinner
david@fromorbit.com
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2012-01-23 4:31 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-21 10:29 How to fix bad superblock or xfs_repair: error - read only 0 of 512 bytes Christian Kildau
2012-01-23 4:31 ` Dave Chinner [this message]
2012-01-23 9:23 ` Christian Kildau
2012-01-24 5:04 ` Eric Sandeen
2012-01-24 7:08 ` Christian Kildau
2012-01-24 10:13 ` Christian Kildau
2012-01-24 14:12 ` Roger Willcocks
2012-01-24 15:46 ` Christian Kildau
2012-01-24 15:50 ` Eric Sandeen
2012-01-24 15:52 ` Christian Kildau
2012-01-24 15:57 ` Eric Sandeen
2012-01-24 17:25 ` Roger Willcocks
2012-01-24 18:10 ` Christian Kildau
2012-01-23 10:43 ` Christian Kildau
-- strict thread matches above, loose matches on Subject: below --
2019-12-28 11:11 Utpal Bora
2019-12-29 3:15 ` Chris Murphy
2019-12-29 5:58 ` Utpal Bora
2019-12-29 4:43 ` Eric Sandeen
2019-12-29 5:58 ` Utpal Bora
2012-01-21 10:03 Christian Kildau
2012-01-24 4:51 ` Eric Sandeen
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=20120123043117.GH15102@dastard \
--to=david@fromorbit.com \
--cc=lists@unixhosts.org \
--cc=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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox