xfs
[Top] [All Lists]

Re: Help with XFS

To: Thomas Førde <thomas.forde@xxxxxxxxxxxx>
Subject: Re: Help with XFS
From: Andi Kleen <andi@xxxxxxxxxxxxxx>
Date: Fri, 18 Jun 2010 14:47:52 +0200
Cc: Emmanuel Florac <eflorac@xxxxxxxxxxxxxx>, xfs@xxxxxxxxxxx
In-reply-to: <OF0E234D8E.F048FF4D-ONC1257746.003FC10E-C1257746.00407333@xxxxxxxxxxxx> ("Thomas Førde"'s message of "Fri\, 18 Jun 2010 13\:43\:57 +0200")
References: <OF4967B99D.609CC213-ONC1257745.0048E646-C1257745.004919A3@xxxxxxxxxxxx> <20100618132108.790921cf@xxxxxxxxxxxxxxxxxxxx> <OF450B8187.BD5256B0-ONC1257746.003E79FF-C1257746.003EE62C@xxxxxxxxxxxx> <20100618133458.6640ce96@xxxxxxxxxxxxxxxxxxxx> <OF0E234D8E.F048FF4D-ONC1257746.003FC10E-C1257746.00407333@xxxxxxxxxxxx>
User-agent: Gnus/5.11 (Gnus v5.11) Emacs/22.3 (gnu/linux)
Thomas Førde <thomas.forde@xxxxxxxxxxxx> writes:

> the raid array is a FC SAN array consisting of DS4700 unit with EXP810
> expansion system
>
> xfs_check first, xfs_repair -n, and xfs_repair
>
> xfs_Repair -L has not been used.
>
> its seismisc processed data, large text files.

I've seen people get text files (source files) back with strings
/dev/...

If you're lucky it's mostly continous and large 
and not too hard to sort out.

But definitely backups are a good idea next time. RAID is no replacement
for backups.

-Andi

-- 
ak@xxxxxxxxxxxxxxx -- Speaking for myself only.

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