From: Marc Joliet <marcec@gmx.de>
To: linux-btrfs@vger.kernel.org
Subject: Re: [4.7.2] btrfs_run_delayed_refs:2963: errno=-17 Object already exists
Date: Wed, 01 Mar 2017 19:27:54 +0100 [thread overview]
Message-ID: <14042548.TX92NSv1AZ@thetick> (raw)
In-Reply-To: <14737660.8idzxVKBRv@thetick>
[-- Attachment #1: Type: text/plain, Size: 698 bytes --]
On Wednesday 01 March 2017 19:14:07 Marc Joliet wrote:
> > And btrfs check --mode=lowmem is also recommended as in some rare case,
> > low mem mode can detect bug which original mode doesn't.
>
> I did see differences in output the last time around (again, see my
> previous messages in this thread), so I'll run with lowmem.
OK, just to prevent confusion: it turns out I never posted the output of
btrfs-check with --mode=lowmem from the first time I was seeing these errors,
but I remember the output being (slightly) different from the original mode.
--
Marc Joliet
--
"People who think they know everything really annoy those of us who know we
don't" - Bjarne Stroustrup
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 801 bytes --]
next prev parent reply other threads:[~2017-03-01 18:35 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-28 13:29 [4.7.2] btrfs_run_delayed_refs:2963: errno=-17 Object already exists Kai Krakow
2017-02-02 12:01 ` Marc Joliet
2017-02-03 22:44 ` Kai Krakow
2017-02-10 22:15 ` Marc Joliet
2017-02-11 2:01 ` Kai Krakow
2017-02-11 10:18 ` Marc Joliet
2017-02-14 12:52 ` Marc Joliet
2017-02-17 8:19 ` Kai Krakow
2017-02-28 22:14 ` Marc Joliet
2017-03-01 8:23 ` Marc Joliet
2017-03-01 9:32 ` Qu Wenruo
2017-03-01 18:14 ` Marc Joliet
2017-03-01 18:27 ` Marc Joliet [this message]
2017-03-01 18:43 ` Marc Joliet
2017-03-02 9:44 ` Marc Joliet
2017-03-03 1:09 ` Qu Wenruo
2017-03-03 11:26 ` Marc Joliet
2017-03-05 23:53 ` Marc Joliet
2017-03-06 11:18 ` Marc Joliet
2017-03-02 0:43 ` Qu Wenruo
2017-03-02 9:43 ` Marc Joliet
2017-03-03 1:00 ` Qu Wenruo
2017-03-03 11:54 ` Marc Joliet
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=14042548.TX92NSv1AZ@thetick \
--to=marcec@gmx.de \
--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.