From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail.virtall.com ([178.63.195.102]:39618 "EHLO mail.virtall.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752790AbaLLWqN (ORCPT ); Fri, 12 Dec 2014 17:46:13 -0500 MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII; format=flowed Date: Fri, 12 Dec 2014 23:46:10 +0100 From: Tomasz Chmielewski To: Robert White Cc: Josef Bacik , linux-btrfs Subject: Re: 3.18.0: kernel BUG at fs/btrfs/relocation.c:242! In-Reply-To: <548B6D58.6080804@pobox.com> References: <542EE83D.8050701@fb.com> <999a300ed462a1e1388aee4d6f03a30e@admin.virtall.com> <438e043f73392614d1453892b7fe225c@admin.virtall.com> <0f30c49c7d208903ef84e31a928e4051@admin.virtall.com> <548B5FD6.5080306@pobox.com> <548B6D58.6080804@pobox.com> Message-ID: Sender: linux-btrfs-owner@vger.kernel.org List-ID: On 2014-12-12 23:34, Robert White wrote: > On 12/12/2014 01:46 PM, Tomasz Chmielewski wrote: >> On 2014-12-12 22:36, Robert White wrote: >> >>> In another thread [that was discussing SMART] you talked about >>> replacing a drive and then needing to do some patching-up of the >>> result because of drive failures. Is this the same filesystem where >>> that happened? >> >> Nope, it was on a different server. >> > > okay, so how did the btrfsck turn out? # time btrfsck /dev/sdc1 &>/root/btrfsck.log real 22m0.140s user 0m3.090s sys 0m6.120s root@bkp010 /usr/src/btrfs-progs # echo $? 1 # cat /root/btrfsck.log root item for root 8681, current bytenr 5568935395328, current gen 70315, current level 2, new bytenr 5569014104064, new gen 70316, new level 2 Found 1 roots with an outdated root item. Please run a filesystem check with the option --repair to fix them. Now, I'm a bit afraid to run --repair - as far as I remember, some time ago, it used to do all weird things except the actual repair. Is it better nowadays? I'm using latest clone from git://git.kernel.org/pub/scm/linux/kernel/git/mason/btrfs-progs.git -- Tomasz Chmielewski http://www.sslrack.com