From: "Stefan G. Weichinger" <lists@xunil.at>
To: linux-btrfs@vger.kernel.org
Subject: "corrupt leaf" on kernel 3.17.2, w/ btrfs-progs 3.17
Date: Thu, 06 Nov 2014 15:45:21 +0100 [thread overview]
Message-ID: <545B8981.2010603@xunil.at> (raw)
My rootfs on /dev/sda2 (an SSD) shows this:
Nov 06 15:37:26 hiro.oops.intern kernel: BTRFS critical (device sda2):
corrupt leaf, slot offset bad: block=100235100160,root=1, slot=142
Scrub runs through fine:
# btrfs scr stat /dev/sda2
scrub status for ea95dbd1-ef4e-48a4-9732-54e6c80b31df
scrub started at Thu Nov 6 15:35:00 2014, running for 172 seconds
total bytes scrubbed: 68.46GiB with 0 errors
Do I have to panic? ;-)
Pls advise how to proceed.
Should I do some repair or btrfsck from a live-medium?
I found this:
http://comments.gmane.org/gmane.comp.file-systems.btrfs/34407
but haven't yet figured out what that means to me.
# btrfs version
Btrfs v3.17
# cat /proc/version
Linux version 3.17.2-gentoo (root@hiro.oops.intern) (gcc version 4.8.3
(Gentoo 4.8.3 p1.1, pie-0.5.9) ) #1 SMP Thu Nov 6 00:53:58 CET 2014
Stefan
next reply other threads:[~2014-11-06 14:55 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-06 14:45 Stefan G. Weichinger [this message]
2014-11-06 16:11 ` "corrupt leaf" on kernel 3.17.2, w/ btrfs-progs 3.17 Stefan G. Weichinger
2014-11-06 16:16 ` Stefan G. Weichinger
2014-11-06 18:03 ` Stefan G. Weichinger
2014-11-06 18:17 ` Stefan G. Weichinger
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=545B8981.2010603@xunil.at \
--to=lists@xunil.at \
--cc=linux-btrfs@vger.kernel.org \
/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.