From: "Stefan G. Weichinger" <lists@xunil.at>
To: linux-btrfs@vger.kernel.org
Subject: Re: "corrupt leaf" on kernel 3.17.2, w/ btrfs-progs 3.17
Date: Thu, 06 Nov 2014 17:16:11 +0100 [thread overview]
Message-ID: <545B9ECB.1040903@xunil.at> (raw)
In-Reply-To: <545B9D97.3040206@xunil.at>
Am 06.11.2014 um 17:11 schrieb Stefan G. Weichinger:
> Am 06.11.2014 um 15:45 schrieb Stefan G. Weichinger:
>
>> Pls advise how to proceed.
>>
>> Should I do some repair or btrfsck from a live-medium?
>
> ... had some hefty kernel crashes ...
>
> Now I am on latest sysresccd.
>
> btrfsck v 3.16 ... fails as well
>
> Backing up.
While I am rsyncing I get this again in dmesg:
btrfs: corrupt leaf, slot offset bad: block ...
btrfs no csum found for inode ...
Can I determine which subvol this relates to?
As far as I understand it is likely the one currently synced?
Maybe I could only recreate that one subvolume and restore?
Or do I have to recreate the whole btrfs?
S
next prev parent reply other threads:[~2014-11-06 16:16 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-06 14:45 "corrupt leaf" on kernel 3.17.2, w/ btrfs-progs 3.17 Stefan G. Weichinger
2014-11-06 16:11 ` Stefan G. Weichinger
2014-11-06 16:16 ` Stefan G. Weichinger [this message]
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=545B9ECB.1040903@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox