| To: | Eric Sandeen <sandeen@xxxxxxxxxxx>, Sean Caron <scaron@xxxxxxxxx> |
|---|---|
| Subject: | Re: Corrupted files |
| From: | Sean Caron <scaron@xxxxxxxxx> |
| Date: | Tue, 9 Sep 2014 18:57:06 -0400 |
| Cc: | Leslie Rhorer <lrhorer@xxxxxxxxxxxx>, "xfs@xxxxxxxxxxx" <xfs@xxxxxxxxxxx> |
| Delivered-to: | xfs@xxxxxxxxxxx |
| In-reply-to: | <540F7E37.7020500@xxxxxxxxxxx> |
| References: | <540F1B01.3020700@xxxxxxxxxxxx> <CAA43vkXwHF9RHW-cbTZ91_vF6wiQ6o_+TQDL3=7kD9P4tErCNQ@xxxxxxxxxxxxxx> <CAA43vkWgh8-EjDXjkySUn+y18W1O+v_W5j+fQankRTgDCmc8tw@xxxxxxxxxxxxxx> <540F7E37.7020500@xxxxxxxxxxx> |
|
Hey, just sharing some hard-won (believe me) professional experience. I have seen xfs_repair take a bad situation and make it worse many times. I don't know that a filesystem fuzzer or any other simulation can ever provide true simulation of users absolutely pounding the tar out of a system. There seems to be a real disconnect between what developers are able to test and observe directly, and what happens in the production environment in a very high-throughput environment. Best, Sean On Tue, Sep 9, 2014 at 6:24 PM, Eric Sandeen <sandeen@xxxxxxxxxxx> wrote: On 9/9/14 11:03 AM, Sean Caron wrote: |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: [PATCH 1/5] xfs_repair: clear bad flgs in process_dinode_int, Eric Sandeen |
|---|---|
| Next by Date: | Re: [PATCH 1/5] xfs_repair: clear bad flgs in process_dinode_int, Dave Chinner |
| Previous by Thread: | Re: Corrupted files, Eric Sandeen |
| Next by Thread: | Re: Corrupted files, Roger Willcocks |
| Indexes: | [Date] [Thread] [Top] [All Lists] |