From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <linux-xfs-owner@vger.kernel.org>
Received: from mr003msb.fastweb.it ([85.18.95.87]:34019 "EHLO
        mr003msb.fastweb.it" rhost-flags-OK-OK-OK-OK) by vger.kernel.org
        with ESMTP id S1752136AbdHTFHZ (ORCPT
        <rfc822;linux-xfs@vger.kernel.org>); Sun, 20 Aug 2017 01:07:25 -0400
Subject: Re: Estimate =?UTF-8?Q?xfs=5Frepair=20run=20time?=
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII;
 format=flowed
Content-Transfer-Encoding: 7bit
Date: Sun, 20 Aug 2017 07:07:20 +0200
From: Gionatan Danti <g.danti@assyoma.it>
In-Reply-To: <a6bffbd0-a87f-86e2-2245-2d5da40c800a@sandeen.net>
References: <22ed5cf73260ae39bf59779b302d8ad3@assyoma.it>
 <a6bffbd0-a87f-86e2-2245-2d5da40c800a@sandeen.net>
Message-ID: <56cbd20ae819fd30897fc65fd81e7249@assyoma.it>
Sender: linux-xfs-owner@vger.kernel.org
List-ID: <linux-xfs.vger.kernel.org>
List-Id: xfs
To: Eric Sandeen <sandeen@sandeen.net>
Cc: linux-xfs@vger.kernel.org, g.danti@assyoma.it

Hi Eric,

Il 20-08-2017 04:10 Eric Sandeen ha scritto:
> It's pretty rare to have large-scale, filesystem-wide corruption.  The
> only times I've ever seen filesystems really get wiped out by
> corruption was when the underlying storage went haywire; a scrambled
> raid, etc.  The sort of thing no filesystem could cope with ...

this is reassuring! ;)

Thank you for reporting.

-- 
Danti Gionatan
Supporto Tecnico
Assyoma S.r.l. - www.assyoma.it
email: g.danti@assyoma.it - info@assyoma.it
GPG public key ID: FF5F32A8