| To: | Sean Caron <scaron@xxxxxxxxx>, Leslie Rhorer <lrhorer@xxxxxxxxxxxx> |
|---|---|
| Subject: | Re: Corrupted files |
| From: | Eric Sandeen <sandeen@xxxxxxxxxxx> |
| Date: | Tue, 09 Sep 2014 17:24:55 -0500 |
| Cc: | "xfs@xxxxxxxxxxx" <xfs@xxxxxxxxxxx> |
| Delivered-to: | xfs@xxxxxxxxxxx |
| In-reply-to: | <CAA43vkWgh8-EjDXjkySUn+y18W1O+v_W5j+fQankRTgDCmc8tw@xxxxxxxxxxxxxx> |
| References: | <540F1B01.3020700@xxxxxxxxxxxx> <CAA43vkXwHF9RHW-cbTZ91_vF6wiQ6o_+TQDL3=7kD9P4tErCNQ@xxxxxxxxxxxxxx> <CAA43vkWgh8-EjDXjkySUn+y18W1O+v_W5j+fQankRTgDCmc8tw@xxxxxxxxxxxxxx> |
On 9/9/14 11:03 AM, Sean Caron wrote: Barring rare cases, xfs_repair is bad juju. No, it's not. It is the appropriate tool to use for filesystem repair. But it is not the appropriate tool for recovery from mangled storage. I've actually been running a filesystem fuzzer over xfs images, randomly corrupting data and testing repair, 1000s of times over. It does remarkably well. If you scramble your raid, which means your block device is no longer an xfs filesystem, but is instead a random tangle of bits and pieces of other things, of course xfs_repair won't do well, but it's not the right tool for the job at that stage. -Eric |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: Corrupted files, Dave Chinner |
|---|---|
| Next by Date: | Re: [PATCH 1/5] xfs_repair: clear bad flgs in process_dinode_int, Christoph Hellwig |
| Previous by Thread: | Re: Corrupted files, Sean Caron |
| Next by Thread: | Re: Corrupted files, Sean Caron |
| Indexes: | [Date] [Thread] [Top] [All Lists] |