From: Tomasz Chmielewski <tch@virtall.com>
To: Btrfs BTRFS <linux-btrfs@vger.kernel.org>
Subject: Re: filesystem read only after power outage
Date: Tue, 05 Jul 2016 15:55:06 +0900 [thread overview]
Message-ID: <f98c7bca36bd8d075fcde4aff0c1fbed@admin.virtall.com> (raw)
In-Reply-To: <7db11e52ffdd949a917036bc38f4b0f1@admin.virtall.com>
On 2016-07-05 14:56, Tomasz Chmielewski wrote:
> Getting this lengthy output logged, and the fs mounter read-only after
> a power outage.
>
>
> Tried also 4.6.3, but it ends just alike.
>
> Jul 5 02:04:20 bkp011 kernel: [ 799.298303] ------------[ cut here
> ]------------
> Jul 5 02:04:20 bkp011 kernel: [ 799.298335] WARNING: CPU: 0 PID:
> 1896 at /home/kernel/COD/linux/fs/btrfs/extent-tree.c:6599
> __btrfs_free_extent.isra.70+0x877/0xd50 [btrfs]
FYI, 4.7-rc6 breaks just like 4.6.0 and 4.6.3.
Tomasz Chmielewski
https://wpkg.org
next prev parent reply other threads:[~2016-07-05 6:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-05 5:56 filesystem read only after power outage Tomasz Chmielewski
2016-07-05 6:55 ` Tomasz Chmielewski [this message]
2016-07-10 3:39 ` Tomasz Chmielewski
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=f98c7bca36bd8d075fcde4aff0c1fbed@admin.virtall.com \
--to=tch@virtall.com \
--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;
as well as URLs for NNTP newsgroup(s).