From: Eric Sandeen <sandeen@sandeen.net>
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 22:51:21 -0600 [thread overview]
Message-ID: <4F1E38C9.3070000@sandeen.net> (raw)
In-Reply-To: <A7348842-BA7C-474A-B2E1-04345761AB25@unixhosts.org>
On 1/21/12 4:03 AM, Christian Kildau wrote:
> 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!
did you do anything else at all besides simply boot a 3.2 kernel?
Or was this a whole distro upgrade? And who knows what the installer
did...?
> 'test disk' does find the filesystem as XFS 4 and i created a 1.5TB
> dump of it to another hdd.
>
> (I created the xfs filesystem on the entire hdd, not on a partition,
> so /dev/sdd is not a typo)
is sdd a single disk or something like lvm/md?
what does grep sdd /proc/partitions say?
And
# xfs_db -c "sb 0" -c "p" /dev/sdd
>
> $ 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
>
> $ 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
stracing those to see where it is failing to read might be useful.
It seems that your device has somehow shrunk out from under your fs.
-Eric
>
> 'testdisk' does find the filesystem as XFS 4 and i created a 1.5TB dump of it to another hdd.
>
> Is there any way I can fix this? - Except restroring from backup? Because this IS my backup!
> see ubuntuforums.org/showthread.php?t=1910962 for more details…
>
>
> Any help is appreciated!
>
> Thanks in advance
> Chris
> _______________________________________________
> 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
next prev parent reply other threads:[~2012-01-24 4:51 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-21 10:03 How to fix bad superblock or xfs_repair: error - read only 0 of 512 bytes Christian Kildau
2012-01-24 4:51 ` Eric Sandeen [this message]
-- strict thread matches above, loose matches on Subject: below --
2012-01-21 10:29 Christian Kildau
2012-01-23 4:31 ` Dave Chinner
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
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
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=4F1E38C9.3070000@sandeen.net \
--to=sandeen@sandeen.net \
--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