All of lore.kernel.org
 help / color / mirror / Atom feed
From: Nicolas Porcel <nicolasporcel06@gmail.com>
To: Noah Massey <noah.massey@gmail.com>
Cc: linux-btrfs <linux-btrfs@vger.kernel.org>
Subject: Re: send ioctl failed with -2
Date: Tue, 8 May 2018 21:40:34 +0200	[thread overview]
Message-ID: <20180508194034.GA8537@nicolas-desktop> (raw)
In-Reply-To: <CADfjVrh5zD5Gu2_gDfDtcVW_PfEnEsCCuoCF-h8Mm+h1N-DWww@mail.gmail.com>

On Tue, May 08, 2018 at 02:16:06PM -0400, Noah Massey wrote:
> Silly question, but is 'mysnapshot' actually accessible at './mysnapshot' ?
> Because the output from btrfs send should immediately output
> 'At subvol mysnapshot'

Inded. This is not even the right command considering I only kept the
error when writing this email. It takes 5-10 minutes to run for 40GB of
data so I did not want to do it again.

> 
> If 'btrfs send' is actually generating output, 'btrfs receive -vv' may
> help "parse" the send stream enough to figure out where it is
> terminating.

I tried it and I did not find anything related to the error. The output
is basically the list of files received and their chmod but nothing
more. Unless I can find which file is causing problem with that.

> 
> ~ Noah
> 
> ps - I was going to suggest 'btrfs send -v'. According the the
> manpage, that would "enable verbose output, print generated commands
> in a readable form". But it does not seem to be working for me, and
> after a quick glance at the code I'm not seeing how the ioctl call is
> setting up any kind of verbose feedback. So that may be out-of-date
> documentation.

I also tried it with 5 'v' and nothing happened.

-- 
Nicolas

      reply	other threads:[~2018-05-08 19:40 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-08 17:44 send ioctl failed with -2 Nicolas Porcel
2018-05-08 18:16 ` Noah Massey
2018-05-08 19:40   ` Nicolas Porcel [this message]

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=20180508194034.GA8537@nicolas-desktop \
    --to=nicolasporcel06@gmail.com \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=noah.massey@gmail.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 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.