From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mx0b-00082601.pphosted.com ([67.231.153.30]:27443 "EHLO mx0a-00082601.pphosted.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1750775AbaJOUUm (ORCPT ); Wed, 15 Oct 2014 16:20:42 -0400 Message-ID: <543ED6FF.1080501@fb.com> Date: Wed, 15 Oct 2014 16:20:15 -0400 From: Josef Bacik MIME-Version: 1.0 To: Rich Freeman CC: Juan Orti Alcaine , Btrfs BTRFS Subject: Re: Random file system corruption in 3.17 (not BTRFS related...?) References: <543D555B.50708@pobox.com> <543E7ACC.8080001@fb.com> <543E8510.8020000@fb.com> In-Reply-To: Content-Type: text/plain; charset="utf-8"; format=flowed Sender: linux-btrfs-owner@vger.kernel.org List-ID: On 10/15/2014 03:30 PM, Rich Freeman wrote: > On Wed, Oct 15, 2014 at 10:30 AM, Josef Bacik wrote: >> We've found it, the Fedora guys are reverting the bad patch now, we'll get >> the fix sent back to stable shortly. Sorry about that. > > After reverting this commit, can the bad snapshots be > deleted/repaired/etc without wiping and restoring the entire > filesystem? Copying 2.3TB of data isn't a particularly fast > operation... > I would certainly like to make fsck repair this sort of problem, let me reproduce the corruption locally and then make fsck fix it and then you can use that. Thanks, Josef