From: linux-xfs@oss.sgi.com
To: christian gattermair <christian.gattermair@mci.edu>
Cc: xfs@oss.sgi.com
Subject: Re: xfs_check - out of memory | xfs_repair - superblock error reading
Date: Mon, 18 Sep 2006 09:41:41 -0500 [thread overview]
Message-ID: <450EB025.5020007@oss.sgi.com> (raw)
In-Reply-To: <200609181519.18448.christian.gattermair@mci.edu>
christian gattermair wrote:
> xfs_repair works but can not find any superblock. any hints?
>
> xfs_repair /dev/sdb1
> Phase 1 - find and verify superblock...
> error reading superblock 11 -- seek to offset 1134332153856 failed
> couldn't verify primary superblock - bad magic number !!!
>
> attempting to find secondary superblock...
> ...
> ...
> ..............found candidate secondary superblock...
> error reading superblock 11 -- seek to offset 1134332153856 failed
That's about a terabyte into your 3t fs, but you can't seek to it? Any kernel
messages when this happens? What does /proc/partitions and/or parted say about
the size of /dev/sdb1? Seems like maybe your device itself is not as expected.
-Eric
next prev parent reply other threads:[~2006-09-18 14:42 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-18 13:19 xfs_check - out of memory | xfs_repair - superblock error reading christian gattermair
2006-09-18 14:41 ` linux-xfs [this message]
2006-09-19 10:03 ` christian gattermair
2006-09-19 15:02 ` Eric Sandeen
2006-09-20 15:35 ` christian gattermair
2006-09-18 22:23 ` David Chinner
2006-09-18 22:56 ` Stephan Jansen
2006-09-19 0:33 ` Barry Naujok
2006-09-19 7:56 ` Frank Hellmann
-- strict thread matches above, loose matches on Subject: below --
2006-09-19 13:19 christian gattermair
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=450EB025.5020007@oss.sgi.com \
--to=linux-xfs@oss.sgi.com \
--cc=christian.gattermair@mci.edu \
--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