public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Michael Monnerie <michael.monnerie@is.it-management.at>
To: xfs@oss.sgi.com
Cc: Adam Huffman <adam.huffman@gmail.com>
Subject: Re: XFS_WANT_CORRUPTED_GOTO error
Date: Mon, 06 Aug 2012 12:33:24 +0200	[thread overview]
Message-ID: <1929929.ZGsW6LLNXR@saturn> (raw)
In-Reply-To: <CAP5prOivS=0PowpcEkmOWPRVo0V8HJQdDV+ZamM5bP5B_nZ5ew@mail.gmail.com>


[-- Attachment #1.1: Type: text/plain, Size: 861 bytes --]

Am Montag, 6. August 2012, 10:50:43 schrieb Adam Huffman:
> Is there any way I can find out where this error is occurring i.e. on
> which LVM logical volume?

By trying a manual mount on each fs this server has?

> Can it be fixed or is the filesystem irretrievably corrupted?

Try "xfs_repair -n" to see what it would fix. Try to get the newest 
version of xfs_repair first.

If there was "only" a power outage chances are high you'll get it fixed, 
but of course if your storage doesn't have BBWC or has disk write caches 
on or you mis-used the nobarrier option you might have lost a whole lot 
of important in-flight data.
See http://xfs.org/index.php/XFS_FAQ

-- 
mit freundlichen Grüssen,
Michael Monnerie, Ing. BSc

it-management Internet Services: Protéger
http://proteger.at [gesprochen: Prot-e-schee]
Tel: +43 660 / 415 6531

[-- Attachment #1.2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

[-- Attachment #2: Type: text/plain, Size: 121 bytes --]

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

      reply	other threads:[~2012-08-06 10:41 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-06  9:50 XFS_WANT_CORRUPTED_GOTO error Adam Huffman
2012-08-06 10:33 ` Michael Monnerie [this message]

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=1929929.ZGsW6LLNXR@saturn \
    --to=michael.monnerie@is.it-management.at \
    --cc=adam.huffman@gmail.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