From: Tomasz Chmielewski <tch@virtall.com>
To: Robert White <rwhite@pobox.com>
Cc: Josef Bacik <jbacik@fb.com>, linux-btrfs <linux-btrfs@vger.kernel.org>
Subject: Re: 3.18.0: kernel BUG at fs/btrfs/relocation.c:242!
Date: Fri, 12 Dec 2014 23:46:10 +0100 [thread overview]
Message-ID: <a3dfa2330fae3ef52d19f9f2a951e7b9@admin.virtall.com> (raw)
In-Reply-To: <548B6D58.6080804@pobox.com>
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
next prev parent reply other threads:[~2014-12-12 22:46 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-02 7:27 3.17.0-rc7: kernel BUG at fs/btrfs/relocation.c:931! Tomasz Chmielewski
2014-10-03 18:17 ` Josef Bacik
2014-10-03 22:06 ` Tomasz Chmielewski
2014-10-03 22:09 ` Josef Bacik
2014-10-04 21:47 ` Tomasz Chmielewski
2014-10-04 22:07 ` Josef Bacik
2014-11-25 22:33 ` Tomasz Chmielewski
2014-12-12 14:37 ` 3.18.0: kernel BUG at fs/btrfs/relocation.c:242! Tomasz Chmielewski
2014-12-12 21:36 ` Robert White
2014-12-12 21:46 ` Tomasz Chmielewski
2014-12-12 22:34 ` Robert White
2014-12-12 22:46 ` Tomasz Chmielewski [this message]
2014-12-12 22:58 ` Robert White
2014-12-13 8:16 ` Tomasz Chmielewski
2014-12-13 9:39 ` Robert White
2014-12-13 13:53 ` Tomasz Chmielewski
2014-12-13 20:54 ` Robert White
2014-12-13 21:52 ` Tomasz Chmielewski
2014-12-13 23:56 ` Robert White
2014-12-14 8:45 ` Robert White
2014-12-15 20:07 ` Josef Bacik
2014-12-15 23:27 ` Tomasz Chmielewski
2014-12-19 21:47 ` Josef Bacik
2014-12-19 23:18 ` Tomasz Chmielewski
2014-10-13 15:15 ` 3.17.0-rc7: kernel BUG at fs/btrfs/relocation.c:931! Rich Freeman
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=a3dfa2330fae3ef52d19f9f2a951e7b9@admin.virtall.com \
--to=tch@virtall.com \
--cc=jbacik@fb.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=rwhite@pobox.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.