Linux Btrfs filesystem development
 help / color / mirror / Atom feed
From: g6094199@freenet.de
To: Matt McKinnon <matt@techsquare.com>,
	Btrfs BTRFS <linux-btrfs@vger.kernel.org>
Subject: Re: BTRFS: error (device sda1) in btrfs_run_delayed_refs:2963: errno=-17 Object already exists
Date: Wed, 10 Aug 2016 09:09:30 +0200	[thread overview]
Message-ID: <cf494b45-6d2e-18a8-b579-17f14b586598@chefmail.de> (raw)
In-Reply-To: <1c409a92-978d-a37a-75ae-8ff2e84f5674@techsquare.com>

Hi,

from what i see you have a non finished balance ongoing, since you have
system and metadata DUP and single information on disk.

so you should (re)run a balance for this data.


sash


Am 10.08.2016 um 02:17 schrieb Matt McKinnon:
> -o usebackuproot worked well.
>
> after the file system settled, performing a sync and a clean umount, a
> normal mount works now as well.
>
> Anything I should be doing going forward?
>
> Thanks,
> Matt
>
> On 08/09/2016 08:01 PM, Chris Murphy wrote:
>> On Tue, Aug 9, 2016 at 5:15 PM, Matt McKinnon <matt@techsquare.com>
>> wrote:
>>> Hello,
>>>
>>> Our server recently crashed and was rebooted.  When it returned our
>>> BTRFS
>>> volume is mounting read-only:
>>
>> What happens when you try mounting with -o usebackuproot ?
>>
>> If that fails, what output do you get for 'btrfs check' (without
>> --repair)? If you only get some "errors 400, nbytes wrong" then
>> --repair should fix the problem.
>>
>>
>>
> -- 
> To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html



  reply	other threads:[~2016-08-10 19:14 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-09 23:15 BTRFS: error (device sda1) in btrfs_run_delayed_refs:2963: errno=-17 Object already exists Matt McKinnon
2016-08-10  0:01 ` Chris Murphy
2016-08-10  0:06   ` Chris Murphy
2016-08-10  0:29     ` Matt McKinnon
2016-08-10  2:25       ` Chris Murphy
2016-08-10  6:41         ` Duncan
2016-08-11  1:51         ` Matt McKinnon
2016-08-10  0:56     ` Matt McKinnon
2016-08-10  0:17   ` Matt McKinnon
2016-08-10  7:09     ` g6094199 [this message]
2016-08-10 11:16       ` Matt McKinnon
2016-08-10 20:43         ` g6094199

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=cf494b45-6d2e-18a8-b579-17f14b586598@chefmail.de \
    --to=g6094199@freenet.de \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=matt@techsquare.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