public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Javier Gomez <gomez@dynamicquest.com>
To: xfs@oss.sgi.com
Subject: Lost Superblock and need help recovering
Date: Sun, 25 May 2008 22:40:31 -0400	[thread overview]
Message-ID: <483A231F.2030207@dynamicquest.com> (raw)



    We are currently running a few Coraid AoE devices which we have 
formated using Raid-5 and XFS filesystem.  The devices were shutdown 
abruptly causing what looks like a some data issues.  We are running a 
Redhat 5 head unit connected to the disk array.  When the devices came 
back up we were unable to remount them.  Based on the tools to check the 
device we got the log information that the Superblock does not exist nor 
does the secondary.  We have two devices, each with 13 TB of disk space 
each and both with what seems like the same issue.  These devices were 
used as a backup storage device, so they are the backup.  But this 
historical information is very critical to us.  We attempted to run the 
"xfs_repair -nv /dev/etherd/e4.1p1"  command to see if found the 
potential issues ( xfs_repair version 2.9.8 ).  It came back with the 
comments noted below.  Does any one have any suggestions for pulling 
this information off the drive and / or correcting this issue?  What 
other tools should I run to get more information?  Thanks for any 
support or suggestions you can provide.


 > xfs_repair -nv /dev/etherd/e4.1p1
---------------------------------------------------------------
Phase 1 - find and verify superblock...
error reading superblock 4 -- seek to offset 1219003957248 failed
couldn't verify primary superblock - bad magic number !!!

attempting to find secondary superblock...
................................................................................................
......................................................
..................
..................
............Sorry, could not find valid secondary superblock
Exiting now.
---------------------------------------------------------------

             reply	other threads:[~2008-05-26  2:39 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-26  2:40 Javier Gomez [this message]
2008-05-26  3:40 ` Lost Superblock and need help recovering Eric Sandeen
2008-05-26 10:35   ` Javier Gomez
2008-05-26 14:49     ` Eric Sandeen
2008-05-26 15:13       ` Javier Gomez
2008-05-26 16:25         ` Eric Sandeen
2008-05-26 19:46           ` Javier Gomez

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=483A231F.2030207@dynamicquest.com \
    --to=gomez@dynamicquest.com \
    --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