From: Marc MERLIN <marc@merlins.org>
To: Chris Murphy <lists@colorremedies.com>
Cc: Btrfs BTRFS <linux-btrfs@vger.kernel.org>
Subject: Re: BTRFS: error (device dm-2) in btrfs_run_delayed_refs:2960: errno=-17 Object already exists
Date: Wed, 12 Jul 2017 18:10:56 -0700 [thread overview]
Message-ID: <20170713011056.GW30689@merlins.org> (raw)
In-Reply-To: <20170711164812.sj64s3nc2oe3ai3n@merlins.org>
On Tue, Jul 11, 2017 at 09:48:12AM -0700, Marc MERLIN wrote:
> On Tue, Jul 11, 2017 at 10:00:40AM -0600, Chris Murphy wrote:
> > > ---[ end trace feb4b95c83ac065f ]---
> > > BTRFS: error (device dm-2) in btrfs_run_delayed_refs:2960: errno=-17 Object already exists
> > > BTRFS info (device dm-2): forced readonly
> >
> > You've already had this same traceback, not sure whether it's the same
> > file system or not, but it was 4.7.2 kernel.
>
> You have better memory than me. I'll admit that I'm kind of overwhelmed
> by all the time I'm currently spending/wasting on btrfs recovery and
> that came almost out of nowwhere and hit me in 3 different places :-/
Ok, I'm on 4.9.36 and same problem :(
This is on an otherwise ok working filesystem that comes back clean
on btrfs check (although I haven't done lowmem but last time I tried lowmem it
reported problems that apparently weren't really problems)
Dear devs, what does this error mean exactly and what should I do about it besides
ignoring it and remounting my FS read-write?
On the plus side thanks for both
1) showing which device the error is on
2) not crashing the system :)
WARNING: CPU: 6 PID: 3730 at fs/btrfs/extent-tree.c:2967 btrfs_run_delayed_refs+0xbd/0x1be
BTRFS: Transaction aborted (error -17)
CPU: 0 PID: 3730 Comm: btrfs-cleaner Tainted: G U W 4.9.36-amd64-preempt-sysrq-20170
Hardware name: System manufacturer System Product Name/P8H67-M PRO, BIOS 3904 04/27/2013
ffffb55c679bfc88 ffffffff8239b00b ffffb55c679bfcd8 0000000000000000
ffffb55c679bfcc8 ffffffff82066769 00000b97679bfd48 ffffa07f61a5eaa0
ffffa086f217c800 00000000ffffffef ffffa086ad8b5a90 00000000000003a0
Call Trace:
[<ffffffff8239b00b>] dump_stack+0x61/0x7d
[<ffffffff82066769>] __warn+0xc2/0xdd
[<ffffffff820667de>] warn_slowpath_fmt+0x5a/0x76
[<ffffffff8228dd5f>] btrfs_run_delayed_refs+0xbd/0x1be
[<ffffffff8228b358>] ? walk_up_tree+0x87/0x10f
[<ffffffff8229fd8f>] btrfs_should_end_transaction+0x54/0x5d
[<ffffffff8228c8b5>] btrfs_drop_snapshot+0x380/0x65c
[<ffffffff822edf7c>] ? btrfs_kill_all_delayed_nodes+0x5f/0xd7
[<ffffffff826ecf8a>] ? _raw_spin_lock+0x15/0x17
[<ffffffff82292130>] ? btrfs_delete_unused_bgs+0x326/0x369
[<ffffffff822a0e29>] btrfs_clean_one_deleted_snapshot+0xce/0xdc
[<ffffffff82298c1e>] cleaner_kthread+0xaf/0x17c
[<ffffffff82298b6f>] ? btrfs_need_cleaner_sleep.isra.25+0x2c/0x2c
[<ffffffff82081e94>] kthread+0xd1/0xd9
[<ffffffff82081dc3>] ? init_completion+0x24/0x24
[<ffffffff82003add>] ? do_fast_syscall_32+0xb7/0xfe
[<ffffffff826ed4b5>] ret_from_fork+0x25/0x30
---[ end trace 59fd1c9a379f73bc ]---
BTRFS: error (device dm-2) in btrfs_run_delayed_refs:2967: errno=-17 Object already exists
BTRFS info (device dm-2): forced readonly
--
"A mouse is a device used to point at the xterm you want to type in" - A.S.R.
Microsoft is to operating systems ....
.... what McDonalds is to gourmet cooking
Home page: http://marc.merlins.org/
next prev parent reply other threads:[~2017-07-13 1:10 UTC|newest]
Thread overview: 48+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-11 6:21 BTRFS: error (device dm-2) in btrfs_run_delayed_refs:2960: errno=-17 Object already exists Marc MERLIN
2017-07-11 16:00 ` Chris Murphy
2017-07-11 16:48 ` Marc MERLIN
2017-07-11 22:43 ` Chris Murphy
2017-07-11 23:04 ` Marc MERLIN
2017-07-13 1:10 ` Marc MERLIN [this message]
2017-07-13 18:17 ` Chris Murphy
2017-07-15 0:48 ` Marc MERLIN
2017-07-15 1:22 ` BTRFS: error (device dm-2) in btrfs_run_delayed_refs:2960: errno=-17 Object already exists (since 3.4 / 2012) Marc MERLIN
2017-07-15 23:12 ` Marc MERLIN
2017-07-16 14:01 ` Giuseppe Della Bianca
2017-07-16 16:06 ` Marc MERLIN
2017-07-17 11:05 ` gius db
2017-08-29 3:16 ` Marc MERLIN
2017-08-29 14:30 ` Josef Bacik
2017-08-29 14:39 ` Marc MERLIN
2017-08-29 14:43 ` Josef Bacik
2017-08-29 18:22 ` Josef Bacik
2017-08-30 3:40 ` Marc MERLIN
2017-08-31 14:52 ` Josef Bacik
2017-08-31 17:36 ` Marc MERLIN
2017-08-31 17:48 ` Josef Bacik
2017-09-01 20:43 ` Marc MERLIN
2017-09-01 23:01 ` Josef Bacik
2017-09-02 16:09 ` Marc MERLIN
2017-09-02 16:52 ` Josef Bacik
[not found] ` <CAHKv19A=OVgCpQpDL2454T+f8QgLm9iynA8xZ4w4Kg8JjYS=UA@mail.gmail.com>
2017-09-02 18:55 ` Fwd: " George Joseph
2017-09-02 23:53 ` Marc MERLIN
2017-09-03 0:30 ` Josef Bacik
2017-09-03 1:01 ` Marc MERLIN
2017-09-03 3:26 ` Josef Bacik
2017-09-03 14:31 ` Marc MERLIN
2017-09-03 14:38 ` Josef Bacik
2017-09-03 14:42 ` Marc MERLIN
2017-09-03 14:55 ` Josef Bacik
2017-09-03 17:33 ` Josef Bacik
2017-09-03 20:20 ` Marc MERLIN
2017-09-04 0:55 ` Josef Bacik
2017-09-05 18:19 ` Josef Bacik
2017-09-09 18:39 ` Marc MERLIN
2017-09-09 22:56 ` Josef Bacik
2017-09-10 2:36 ` Marc MERLIN
2017-09-10 3:12 ` Josef Bacik
2017-09-10 13:14 ` Marc MERLIN
2017-09-10 13:16 ` Josef Bacik
2017-09-11 0:22 ` Marc MERLIN
2017-09-27 18:01 ` Marc MERLIN
-- strict thread matches above, loose matches on Subject: below --
2017-08-31 11:14 BTRFS: error (device dm-2) in btrfs_run_delayed_refs:2960: errno=-17 Object already exists George Joseph
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=20170713011056.GW30689@merlins.org \
--to=marc@merlins.org \
--cc=linux-btrfs@vger.kernel.org \
--cc=lists@colorremedies.com \
/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).