From: Emmanuel Florac <eflorac@intellique.com>
To: "Thomas Førde" <thomas.forde@bergenofs.no>
Cc: xfs@oss.sgi.com
Subject: Re: Help with XFS
Date: Fri, 18 Jun 2010 14:00:28 +0200 [thread overview]
Message-ID: <20100618140028.05650928@harpe.intellique.com> (raw)
In-Reply-To: <OF0E234D8E.F048FF4D-ONC1257746.003FC10E-C1257746.00407333@bergenofs.no>
Le Fri, 18 Jun 2010 13:43:57 +0200
Thomas Førde <thomas.forde@bergenofs.no> écrivait:
> 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.
That's fortunate, maybe something can be saved from that.
> its seismisc processed data, large text files.
I see. Extremely expensive to reproduce...
If you know the file structure and the metadata isn't much ineresting,
a simple perl or python script can scrap the raw device for the data.
I've done it before. I can send you code snippets if you want.
Did you have any success compiling xfs_irecover?
It's a side note but one of my customers is specialised in seismic data
acquisition, and record every data twice on two different RAID-1
systems and always keep at least two copies of everything, plus an
on-tape copy... A commodity 16TB NAS costs much less (10000 € or less)
than the data it holds and makes a nice backup system. NOTHING replaces
a backup. Your system WILL fail someday (well it has now apparently).
--
------------------------------------------------------------------------
Emmanuel Florac | Direction technique
| Intellique
| <eflorac@intellique.com>
| +33 1 78 94 84 02
------------------------------------------------------------------------
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2010-06-18 11:57 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-17 13:18 Help with XFS Thomas Førde
2010-06-17 15:15 ` Michael Monnerie
2010-06-18 11:21 ` Emmanuel Florac
2010-06-18 11:27 ` Thomas Førde
2010-06-18 11:34 ` Emmanuel Florac
2010-06-18 11:43 ` Thomas Førde
2010-06-18 12:00 ` Emmanuel Florac [this message]
2010-06-18 12:17 ` Thomas Førde
2010-06-18 13:08 ` Emmanuel Florac
2010-06-18 13:35 ` Thomas Førde
2010-06-18 14:01 ` Emmanuel Florac
2010-06-18 18:50 ` Thomas Førde
2010-06-18 20:57 ` Emmanuel Florac
2010-06-18 12:30 ` Thomas Førde
2010-06-18 12:48 ` Emmanuel Florac
2010-06-19 15:14 ` Robert Brockway
2010-06-18 13:00 ` Stan Hoeppner
2010-06-18 12:55 ` Stan Hoeppner
2010-06-18 14:04 ` Emmanuel Florac
2010-06-18 15:38 ` Help with XFS -- use DS4700 Volume Copy feature for backing up the seismic date LUN Stan Hoeppner
2010-06-18 12:47 ` Help with XFS Andi Kleen
2010-06-18 16:43 ` Michael Monnerie
2010-06-18 16:52 ` Emmanuel Florac
2010-06-19 8:29 ` Michael Monnerie
2010-06-18 17:21 ` Stan Hoeppner
2010-06-19 13:13 ` Emmanuel Florac
[not found] <d4c731da0807251224m2632838bme52760a8a29c8871@mail.gmail.com>
2008-07-25 19:29 ` Eric Sandeen
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=20100618140028.05650928@harpe.intellique.com \
--to=eflorac@intellique.com \
--cc=thomas.forde@bergenofs.no \
--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