From: Alexander Fougner <fougner89@gmail.com>
To: Duncan <1i5t5.duncan@cox.net>
Cc: linux-btrfs <linux-btrfs@vger.kernel.org>
Subject: Re: receive snapshot, complains about missing file
Date: Sat, 30 Apr 2016 12:55:06 +0200 [thread overview]
Message-ID: <CAGGqMYQH7h4-atS+ecBzngBMLu7iRe4-CehjavUAcJMje+v=wA@mail.gmail.com> (raw)
In-Reply-To: <pan$e4ba4$a250943d$4b67b01a$4a6c9e1c@cox.net>
2016-04-30 12:49 GMT+02:00 Duncan <1i5t5.duncan@cox.net>:
> Alexander Fougner posted on Sat, 30 Apr 2016 12:28:34 +0200 as excerpted:
>
>>>>> Do scrub and btrfs check (no repair) complete without errors?
>>
>> Send side
>>
>> sudo btrfs check /dev/sda1
>> Checking filesystem on /dev/sda1
>
> [... but no errors]
>
>> Receive side only outputs this:
>> sudo btrfs check -p /dev/sdc
>> Couldn't open file system
>
> It wasn't mounted at the time, right?
Nope
>
> Cuz btrfs check won't work with a mounted filesystem.
>
> Of course you'll need to be root to access the device as well,
> but that's pretty much a given.
I think sudo should do that, right?
>
>
>> Scrub completes without errors on both FS.
>
> That's good. =:^)
>
> --
> Duncan - List replies preferred. No HTML msgs.
> "Every nonfree program has a lord, a master --
> and if you use the program, he is your master." Richard Stallman
>
> --
> 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
next prev parent reply other threads:[~2016-04-30 10:55 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-29 20:01 receive snapshot, complains about missing file Alexander Fougner
2016-04-29 20:17 ` Chris Murphy
2016-04-29 20:20 ` Alexander Fougner
2016-04-29 20:28 ` Chris Murphy
2016-04-30 10:27 ` Alexander Fougner
2016-04-30 10:28 ` Alexander Fougner
2016-04-30 10:49 ` Duncan
2016-04-30 10:55 ` Alexander Fougner [this message]
2016-04-30 11:28 ` Duncan
2016-05-03 19:00 ` Alexander Fougner
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='CAGGqMYQH7h4-atS+ecBzngBMLu7iRe4-CehjavUAcJMje+v=wA@mail.gmail.com' \
--to=fougner89@gmail.com \
--cc=1i5t5.duncan@cox.net \
--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 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).