From: Mark Ridley <mark@backupsystems.co.uk>
To: "dsterba@suse.cz" <dsterba@suse.cz>
Cc: "linux-btrfs@vger.kernel.org" <linux-btrfs@vger.kernel.org>
Subject: Re: BTRFS 3.8.7 Kernel Crash Report
Date: Mon, 22 Apr 2013 15:01:14 +0100 [thread overview]
Message-ID: <CD9B00AC.385FF%mark@backupsystems.co.uk> (raw)
In-Reply-To: <20130422134249.GN16427@twin.jikos.cz>
Thanks, David.
What causes this corruption and how can I fix it?
I'm very worried about running btrfs.fsck as last time it made a slight
corruption like this worse and the whole volume had to be trashed.
After fsck the "available space" on df ended up being negative so nothing
could be written to the volume.
Mark
On 22/04/2013 14:42, "David Sterba" <dsterba@suse.cz> wrote:
>On Mon, Apr 22, 2013 at 01:19:41PM +0000, Mark Ridley wrote:
>> If I then use rsync --inplace to update the images, I get a btrfs stack
>>trace
>> and btrfs hangs:
>>
>> This happens every night.
>
>> [<ffffffffa00bd5c1>] btrfs_set_item_key_safe+0x141/0x150 [btrfs]
>
>The check fails because it finds keys in reverted order. Given the
>conditions under which it happens I think it's an on-disk corruption and
>fsck should be able to at least detect it.
>
>david
next prev parent reply other threads:[~2013-04-22 14:01 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-22 13:19 BTRFS 3.8.7 Kernel Crash Report Mark Ridley
2013-04-22 13:42 ` David Sterba
2013-04-22 14:01 ` Mark Ridley [this message]
2013-04-22 14:02 ` BTRFS 3.8.7 Kernel Crash Report Harald Glatt
2013-04-22 14:04 ` Mark Ridley
2013-04-22 14:13 ` Harald Glatt
2013-04-22 14:16 ` Mark Ridley
2013-04-22 14:18 ` Harald Glatt
2013-04-22 14:24 ` Mark Ridley
2013-04-22 14:28 ` Harald Glatt
2013-04-22 14:40 ` Mark Ridley
2013-04-22 14:41 ` Hugo Mills
2013-04-22 14:41 ` Harald Glatt
2013-04-22 14:44 ` Mark Ridley
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=CD9B00AC.385FF%mark@backupsystems.co.uk \
--to=mark@backupsystems.co.uk \
--cc=dsterba@suse.cz \
--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