linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: gius db <giusdbg@gmail.com>
To: Marc MERLIN <marc@merlins.org>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: BTRFS: error (device dm-2) in btrfs_run_delayed_refs:2960: errno=-17 Object already exists (since 3.4 / 2012)
Date: Mon, 17 Jul 2017 13:05:12 +0200	[thread overview]
Message-ID: <CAO6aweN16fR9xE955UwCy_nsWUOtYEy_nt=ujHEqwz-i+zrCXQ@mail.gmail.com> (raw)
In-Reply-To: <20170716160658.r4uxuqlfe24hgi5n@merlins.org>

2017-07-16 18:06 GMT+02:00 Marc MERLIN <marc@merlins.org>:
> On Sun, Jul 16, 2017 at 04:01:53PM +0200, Giuseppe Della Bianca wrote:
>> > On Fri, Jul 14, 2017 at 06:22:16PM -0700, Marc MERLIN wrote:
>> > > Dear Chris and other developers,
>> ]zac[
>> > Others on this thread with the same error: did anyone recover from this
>> > without wiping the filesystem?
>> >
>> > Is there a chance a balance might work around the bug so that whatever
>> > layout I have, changes, and stops the bug from occuring?
>> ]zac[
>>
>> Any attempt, even just delete files, has worsened the situation.
>> I advise not to waste time in repairs, and directly recreate the filesystem.
>
> I see. So, this is a condition where the filesystem is clear as far as:
> - check
> - check lowmem
> - scrub
> are all concerned (at least in my case), but it's in a state where
> touching something around a sensitive area causes the bug.
> If so, this blows, and I'm not really wanting to recreate a clean 12TB
> filesystem "just because", especially since this could just happen
> again after I've rebuilt it.
>

IMHO, rebuild from scratch, 1-2 times a year, the snapshot receive
filesystem is inevitable.

For this reason, my snapshot receive filesystems have only this
purpose and are not bigger than 1-2 TB.


>>  while read proc; do
>>        if [ $progResult == 0 ]; then
>>                echo -e \nbtrfs tools already running
>>
>>                progResult=222
>>        fi
>>
>>        echo $proc"
>>  done < <(ps -ef | grep -e "btrfs \{1,\}\(subvolume\|send\|receive\|delete\)")
>
> Yeah, I probably hit that. I think you can also add scrub to that list.
>

Yes.

I did not add scrubs because my scrub are always read-only.
And I think that race condition is between snapshot receive and
subvolume delete.

I also suggest:
- Use btrfs subvolume delete with -c
- Try to add a sleep after subvolume delete and receive.

> Marc


Gdb

  reply	other threads:[~2017-07-17 11:05 UTC|newest]

Thread overview: 47+ 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
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 [this message]
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

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='CAO6aweN16fR9xE955UwCy_nsWUOtYEy_nt=ujHEqwz-i+zrCXQ@mail.gmail.com' \
    --to=giusdbg@gmail.com \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=marc@merlins.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).