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:date:from:to:subject:message-id:reply-to :references:mime-version:content-type:in-reply-to; q=dns; s= default; b=CADM+WL+d2DxnTlKCHsAzHQ/Lg7jJ9JVLvGXor/emVAR4JQ/Z9V3z GqDrRblL7C87BXQbKR5mZa9I506phdYyTop0qyTdLnAuokzczH0ZpbNTYDMMo2lI 3qpX6HUyLbQ2uYX5satRvwJEawMqfXozYtgZWujXhUGU6PIS2XYnR0= 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:date:from:to:subject:message-id:reply-to :references:mime-version:content-type:in-reply-to; s=default; bh=6pGd1loKP0vax4Rt1O+IQ5/tfRU=; b=kgajoTKL+6r1yvMYJSoa1SZh8TJ7 vNTe+j5m9A4jrKjFyzmHjhRBMQB6hC2NfkKqNP66qH/DaM9v1ARNKY8IlcvC4jqO 3ElruGnd9sIxfAYq9Aar3QYn7OQhnCOSP0TSX/x/wYt7WuR/QYL6OM+ajiYGINHI LcWZYOiTlo4RtSs= 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=-1.8 required=5.0 tests=AWL,BAYES_00 autolearn=ham version=3.3.1 Date: Wed, 29 May 2013 10:47:03 +0200 From: Corinna Vinschen To: cygwin AT cygwin DOT com Subject: Re: Shadowcopy volume block devices Message-ID: <20130529084703.GE31309@calimero.vinschen.de> Reply-To: cygwin AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com References: <20130528133514 DOT GJ5264 AT calimero DOT vinschen DOT de> <20130528153302 DOT GL5264 AT calimero DOT vinschen DOT de> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.21 (2010-09-15) On May 29 11:14, Micky wrote: > > That's not what you wrote in your OP. You wrote "but it doesn't let you > > access the volumes as block devices", which is pretty misleading as far > > as bug reports go. > > Sorry for not being clear enough. > > > The endless loop problem accessing the device via /proc/sys/... should > > be fixed in CVS now. > > > > Thanks for such an instant fix. > > > I created a new developer snapshot. Please give the 2012-05-28 Cygwin > > DLL from http://cygwin.com/snapshots/ a try. I also created a new 64 > > bit test release Cygwin package 1.7.19-8 with this patch included. > > I am gonna test it out soon and will report back. I'm looking forward to your feedback. Btw., as a sidenote, are you aware that you can access the filesystem underneath the volume shadow copy as well? Try this (note the trailing backslash!): $ cd /proc/sys/Device/HarddiskVolumeShadowCopy1/ $ ls The only downside is that you can't cd into the root dir of the shadowcopy by using a ".." expression: $ cd /proc/sys/Device/HarddiskVolumeShadowCopy1/Users $ cd .. /proc/sys/Device/HarddiskVolumeShadowCopy1: Not a directory. $ cd ../ /proc/sys/Device/HarddiskVolumeShadowCopy1: Not a directory. Here the path handling strips off the trailing backslash and what's left is a block device called /proc/sys/Device/HarddiskVolumeShadowCopy1. With that in mind, it's quite usable, though. Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Maintainer cygwin AT cygwin DOT com Red Hat -- 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