[Top] [All Lists]


To: xfs@xxxxxxxxxxx
From: Michael Monnerie <michael.monnerie@xxxxxxxxxxxxxxxxxxx>
Date: Mon, 06 Aug 2012 12:33:24 +0200
Cc: Adam Huffman <adam.huffman@xxxxxxxxx>
In-reply-to: <CAP5prOivS=0PowpcEkmOWPRVo0V8HJQdDV+ZamM5bP5B_nZ5ew@xxxxxxxxxxxxxx>
Organization: it-management http://it-management.at
References: <CAP5prOivS=0PowpcEkmOWPRVo0V8HJQdDV+ZamM5bP5B_nZ5ew@xxxxxxxxxxxxxx>
User-agent: KMail/4.7.2 (Linux/3.5.0-zmi; KDE/4.7.2; x86_64; ; )
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: signature.asc
Description: This is a digitally signed message part.

<Prev in Thread] Current Thread [Next in Thread>