From: Tomasz Chmielewski <tch@virtall.com>
To: Btrfs BTRFS <linux-btrfs@vger.kernel.org>
Subject: Re: filesystem read only after power outage
Date: Sun, 10 Jul 2016 12:39:58 +0900 [thread overview]
Message-ID: <f7c66413aea9dfe6a5f608df105a8490@admin.virtall.com> (raw)
In-Reply-To: <f98c7bca36bd8d075fcde4aff0c1fbed@admin.virtall.com>
On 2016-07-05 15:55, Tomasz Chmielewski wrote:
> 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.
I've tried running btrfs check --repair -p, but after some 2 days it
ended with:
reset nbytes for ino 2418526 root 12989
reset nbytes for ino 2634616 root 12989
reset nbytes for ino 2746243 root 12989
reset nbytes for ino 2824005 root 12989
ctree.c:195: update_ref_for_cow: Assertion `ret` failed.
btrfs(__btrfs_cow_block+0x399)[0x43a719]
btrfs(btrfs_cow_block+0x102)[0x43afac]
btrfs(btrfs_search_slot+0x1cc)[0x43da5d]
btrfs[0x423daa]
btrfs(cmd_check+0x29bf)[0x42c68c]
btrfs(main+0x155)[0x409f63]
/lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf0)[0x7f96b3271830]
btrfs(_start+0x29)[0x409b59]
reset nbytes for ino 3217513 root 12989
Failed to find [90569834496, 168, 16384]
Tomasz Chmielewski
https://wpkg.org
prev parent reply other threads:[~2016-07-10 3:40 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
2016-07-10 3:39 ` Tomasz Chmielewski [this message]
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=f7c66413aea9dfe6a5f608df105a8490@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 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.