CEPH filesystem development
 help / color / mirror / Atom feed
From: Stefan Priebe - Profihost AG <s.priebe@profihost.ag>
To: Alexandre DERUMIER <aderumier@odiso.com>
Cc: ceph-devel@vger.kernel.org
Subject: Re: rbd import from stdin
Date: Fri, 23 Nov 2012 11:43:41 +0100	[thread overview]
Message-ID: <50AF535D.5080602@profihost.ag> (raw)
In-Reply-To: <9a1238da-8eb3-4080-b331-26890d51b9aa@mailpro>

ah so right now the size parameter is needed. But i don't know the size 
;-) file is gzip compressed ;-)

Stefan
Am 23.11.2012 11:25, schrieb Alexandre DERUMIER:
>
> import for stdin already work like this:
>
> rbd import --size=xxx - image < stdin
>
> from this patch
>
> http://permalink.gmane.org/gmane.comp.file-systems.ceph.devel/6315
>
>
> (so I think you just need to specify --size)
>
>
>
> ----- Mail original -----
>
> De: "Stefan Priebe - Profihost AG" <s.priebe@profihost.ag>
> À: ceph-devel@vger.kernel.org
> Envoyé: Vendredi 23 Novembre 2012 11:15:11
> Objet: rbd import from stdin
>
> Hello,
>
> i was looking at the wip-rbd-export-stdout branch which also allows to
> import from stdin.
>
> But it doesn't seem to work:
>
> gzip -d -c vm-101-disk-1.img.gz | rbd import - kvmpool1/vm-101-disk-1
> rbd: unable to get size of file/block device: (25) Inappropriate ioctl
> for device
> rbd: import failed: (25) Inappropriate ioctl for device
>
> Greets,
> Stefan
>
--
To unsubscribe from this list: send the line "unsubscribe ceph-devel" 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:[~2012-11-23 10:43 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-11-23 10:15 rbd import from stdin Stefan Priebe - Profihost AG
2012-11-23 10:25 ` Alexandre DERUMIER
2012-11-23 10:43   ` Stefan Priebe - Profihost AG [this message]
2012-11-23 14:07     ` Stefan Priebe - Profihost AG
2012-11-23 14:15       ` Alexandre DERUMIER

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=50AF535D.5080602@profihost.ag \
    --to=s.priebe@profihost.ag \
    --cc=aderumier@odiso.com \
    --cc=ceph-devel@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