All of lore.kernel.org
 help / color / mirror / Atom feed
From: Eric Sandeen <sandeen@sandeen.net>
To: Nicolas STRANSKY <Nico@stransky.cx>
Cc: linux-xfs@oss.sgi.com
Subject: Re: Filesystem corrupted: "Sorry,	could not find valid secondary superblock"
Date: Fri, 29 Jan 2010 09:38:53 -0600	[thread overview]
Message-ID: <4B63010D.1080608@sandeen.net> (raw)
In-Reply-To: <hjus58$6oi$1@ger.gmane.org>

Nicolas STRANSKY wrote:
> Hi,
> 
> I'm using Debian Lenny with xfsprogs 2.9.8-1lenny1 and a kernel
> 2.6.26-2-amd64. Recently I had some disk failures on a 1.5TB RAID 5
> array, which is now running in a degraded mode but the xfs filesystem on
> this array is inconsistent. I can mount it with -o ro,norecovery and
> read some files, but I can't read most of them.
> Using xfs_repair, I tried to repair the filesystem. It went for 12
> hours, displaying these messages:
> "found candidate secondary superblock...
> unable to verify superblock, continuing..."
> and finally:
> "Sorry, could not find valid secondary superblock
> Exiting now."
> 
> Is there anything else I could do to repair the filesystem? Upgrade to a
> newer version of xfsprogs? Is it possible that there is no valid
> secondary superblock on the whole disk or are they just not found?
> 
> Thanks a lot for any help,
> NS.

xfs_repair needs to be smarter about this; I at least wish it'd say
-why- the candidate was not valid.

Can you include the whole repair output?  Then maybe we can direct
you to some xfs_db jujitsu to examine the fs.

Trying newer xfsprogs would not be a -bad- idea...

-Eric

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

  reply	other threads:[~2010-01-29 15:37 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-01-29 14:42 Filesystem corrupted: "Sorry, could not find valid secondary superblock" Nicolas STRANSKY
2010-01-29 15:38 ` Eric Sandeen [this message]
2010-01-29 16:06   ` Nicolas Stransky
2010-01-29 17:12     ` Eric Sandeen
2010-01-29 17:41       ` Nicolas Stransky
2010-01-29 18:16         ` Eric Sandeen
2010-01-29 19:58           ` Nicolas Stransky
2010-02-01 17:29           ` Nicolas Stransky

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=4B63010D.1080608@sandeen.net \
    --to=sandeen@sandeen.net \
    --cc=Nico@stransky.cx \
    --cc=linux-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 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.