X-Recipient: archive-cygwin AT delorie DOT com DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id :list-unsubscribe:list-subscribe:list-archive:list-post :list-help:sender:mime-version:in-reply-to:references:date :message-id:subject:from:to:content-type; q=dns; s=default; b=j4 4Gj3FtMYQQbnuSagohX4tEj/VtyKZurQBFrKeLqPGDKBBXsEIWTeeC+ae+s7KKuq 4SWmqh0XZ0uWJczsLY8jA+oI3pi3cBHq8o8thNVPgz6+eNVJTbwIhx0CvPUlj2eS qKep10vI9/xrMxCPBHQCnvil/vF8ootKX0LxgIIII= DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=sourceware.org; h=list-id :list-unsubscribe:list-subscribe:list-archive:list-post :list-help:sender:mime-version:in-reply-to:references:date :message-id:subject:from:to:content-type; s=default; bh=2ILb0F/O RAlltPgP1lWqyyD7A28=; b=FgkSzNKidyXKdp+ngQaq6DPsOcSeDA/yEu7JqxFB xF65tkaeDiIPjUCBmPbJuf0aMJkdaig2wIISmGAa7Fp2FJNCRBGFLkSuwzlV4bGj Crd1Jb5auU5HquicdAOj2nNMd1VWnw4ClTmlQmaiFCV5UpPLZ9oDwf6h+UPE83S5 uNc= Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com X-Spam-SWARE-Status: No, score=0.4 required=5.0 tests=AWL,BAYES_00,FREEMAIL_FROM,KHOP_THREADED,RCVD_IN_DNSWL_LOW,RCVD_IN_HOSTKARMA_YE,SPF_PASS autolearn=ham version=3.3.1 MIME-Version: 1.0 X-Received: by 10.229.195.2 with SMTP id ea2mr9166849qcb.120.1369749208905; Tue, 28 May 2013 06:53:28 -0700 (PDT) In-Reply-To: <20130528133514.GJ5264@calimero.vinschen.de> References: <20130528133514 DOT GJ5264 AT calimero DOT vinschen DOT de> Date: Tue, 28 May 2013 18:53:28 +0500 Message-ID: Subject: Re: Shadowcopy volume block devices From: Micky To: cygwin AT cygwin DOT com Content-Type: text/plain; charset=ISO-8859-1 >On Tue, May 28, 2013 at 6:35 PM, Corinna Vinschen wrote: > If you knew that you could access > HarddiskVolumeShadowCopy using the POSIX path > why didn't you try to use the POSIX path as device name in a call to the > POSIX tool dd, rather than translating it into a Win32 path? It's clearly > marked as block device in the directory listing: Because if I do that, the dd goes into a loop dumping an endless amount of data. When I tried c:\cygwin\dd.exe directly at the CMD with "\\.\" win32 path, I got correct size of dump so that's why I knew something is up with the block devices presented inside Cygwin (at least for dd). -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple