From: Matt McKinnon <matt@techsquare.com>
To: Chris Murphy <lists@colorremedies.com>
Cc: 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: Tue, 9 Aug 2016 20:17:05 -0400 [thread overview]
Message-ID: <1c409a92-978d-a37a-75ae-8ff2e84f5674@techsquare.com> (raw)
In-Reply-To: <CAJCQCtReDSm46LVVZaiMO3oSRgi9EBQnY9+JkH6Fia1SFH4AWg@mail.gmail.com>
-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.
>
>
>
next prev parent reply other threads:[~2016-08-10 0:17 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 [this message]
2016-08-10 7:09 ` g6094199
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=1c409a92-978d-a37a-75ae-8ff2e84f5674@techsquare.com \
--to=matt@techsquare.com \
--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