> /proc/partitions is populated, but only with actual disks. The device
> mapping for disks is a mapping from the internal NT namespace objects
> \Device\HarddiskX\PartitionY to the POSIX-like /dev/sdXY. Since shadow copies
> of a disk don't match this mapping, you're out of luck. Maybe we can ad
The issue appears to be with ntfsclone in that it must point to something in
/proc/partitions. It will not work with any /cygdrive/X (used dosdev.c from
Corinna and typical vshadow to expose as a drive with no luck). I found this
out by commenting out the read-only check and rebuilding ntfsclo
I was able to get ntfsprogs to compile under cygwin 1.7 after some
troubleshooting. I tried to get ntfsclone to point to the //?/GLOBALROOT for a
shadow copy. I know dd can do this. ntfsclone doesn't appear to be aware of
these devices and there are no /dev/sd?? associated with them either.
Does anyone know of an ntfsclone package that works under 1.7? I tried
compiling 2.0 from sourceforge. I didn't get any errors from ./configure,
make, or make install but the executable doesn't return anything when I run
it. ntfsclone --help doesn't return anything either.
I've been using dd wi
> Rob, many thanks for your reply.
> So it's not just me having massive problems with the NT permissions which
are
> being messed up by Cygwin tools like rsync. Actually most Cygwin users
should
> see these problems, I guess, because Windows 2000 and XP use NTFS.
> I can't use rsync anymore, becaus
On Nov 14 10:38, Corinna Vinschen wrote:
> It shouldn't be hard to replicate if you modify the rsync statement to
> rsync only one such file. The strace would be interesting in the first
> place. You should get an error code from a function called
> fhandler_disk_file::ftruncate.
I can't replica
On 11/15/2008, Richard Ivarson wrote:
> Corinna, thanks to your post I did that now, but unfortunately RSYNC >
still resets my NT permissions.
> Like Rob I use cygdrive paths.
>
> Rob, how did you manage to keep the NT permissions with your RSYNC? > >
For me it always sets own permissions, which th
We still get these issues when preallocating large file on our SAN. It only
occurs when preallocating (posix_fallocate) files that are 20GB+ in size.
I'll try to get a trace but this will be difficult to replicating I think.
Is there any other information I can try to capture?
Rob
Original
Is there a way to specify noacl for any cygdrive referenced path? I have
used rsync quite a bit in the past and rather than specifying mount point
such as /var, I have just referenced the path to the directory to store
(e.g. /cygdrive/e/data/backup01). This allows me to put the data anywhere
on a
Sorry I didn't get back sooner...was occupied with another issue. I double
checked and the array had a drive that was having a few media issues at the
time I was getting this issue. I think this is what was causing the issue
although I don't have any hard evidence. I replaced that drive and have
I've been testing out the 1.7.0-28 build of cygwin using rsync 3.0.3 with
the preallocate patch. My destination server setup is a Windows Server 2003
R2 machine with a fibre array (10TB). The client is also running the same
version of cygwin and rsync on a Server 2003 box.
I've noticed that wh
I'm not really using pipes since rsync and ssh spawn separate processes for
each connection. I am using pipes in some other places with cygwin so I'll
see if I notice the same performance improvements there. It could be the
rewrite you did is having an impact somewhere beneath the covers that I'm
I've been testing cygwin 1.7 on Server 2008 with rsync. First, the install
went flawlessly. I'm just using a standard path of E:\cygwin...no fstab
issues.
Compiling rsync worked without a hitch. The rsync version is 3.02 with the
preallocate patch applied. The patch takes advantage of the posi
Are extended attributes supported under cygwin? My development environment
keeps returning a failure when attempting to use extended attributes in
rsync when running configure.
Rob
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/prob
I recreated a new development environment and recompiled the rsync code. The
posix_fallocate call worked exactly as expected, immediately creating a file of
the size passed to the function. I tested up to 300GB without issue. I must
have had something set up incorrectly in my development envi
Is posix_fallocate in any released version of cygwin? Or is it only in CVS?
I've seen it in snapshots since August of last year but cannot successfully
determine if it is in a released version or not so I'd thought I'd just ask.
Rob
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-
> I can't reproduce this behaviour. I created a 40 Gigs file (haven't 77
> Gigs left) on my XP box using the posix_fallocate function (which, btw.,
> is basically just a single native NT call under the hood) and it takes
> roughly a few milliseconds.
I checked the dodgy app lists.none of those ar
cated than
that but thought it may provide a way to quickly preallocate the file.
Rob
-Original Message-
From: Rob Bosch [mailto:[EMAIL PROTECTED]
Sent: Thursday, November 01, 2007 5:27 PM
To: 'cygwin@cygwin.com'
Subject: High CPU usage on posix_fallocate call - CVS version
W
When my compiled version of rsync is using the posix_fallocate function Im
getting significant CPU usage. The machine is a dual-core processor and Im
getting 20%-25% CPU utilization during the posix_fallocate call. Machine
stats Windows Server 2003 x64 R2, 4GB RAM (over 2.0GB free), fiber
con
You were right on the mark...forgot to copy the header files into my cygwin
environment. I was a little too anxious there. Copied over the header
files and build worked for rsync. Thanks!
Yeah, aware of the caveat on production stuff. I'm just working on testing
some rsync patches to deal with
I've been trying to compile rsync using the cygwin CVS from yesterday. When
I do the configure it is reporting the posix_fallocate function is not
supported. The version of cygwin1.dll is 1007.0.0 with an API version of
0.177. I thought posix_fallocate was still supported?
--
Unsubscribe
There is also some information about this at the following forum link. It
works well for files in use!
http://www.itefix.no/phpws/index.php?module=faq&FAQ_op=view&FAQ_id=81
Rob
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/proble
Looks like you posted with the answer too. Thanks for the effort and help,
I'm building it now.
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html
Documentation: http://cygwin.com/docs.html
FAQ: http
It seems to have solved the problem. Our volume testing is going well now.
Thanks for your help Christopher!
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html
Documentation: http://cygwin.com/docs.html
FAQ:
Found the debugging in winsup.h. Dave Korn had told me where it was from a
previous post but I missed it.
-Original Message-
From: Rob Bosch [mailto:[EMAIL PROTECTED]
Sent: Wednesday, September 13, 2006 12:02 AM
To: 'cygwin@cygwin.com'
Subject: RE: Services stopping - CLA
Where do I make that change? I'm new to compiling the cygwin...sorry. I
looked in the src/winsup/cygwin/config.h.in which should override the other
config.h values, right? It has #undef DEBUGGING which should turn it off.
Again, sorry for the inexperienced questions!
--
Unsubscribe info:
machine however. How can I increase the number
of threads available? Does this have to be done at compile time or is it
something I can "configure" in the package?
-Original Message-
From: Rob Bosch [mailto:[EMAIL PROTECTED]
Sent: Tuesday, September 12, 2006 7:53 AM
To: &#
a lot of threads when the processes fail. There is plenty of
memory and resources on the machine however. How can I increase the number
of threads available? Does this have to be done at compile time or is it
something I can "configure" in the package?
-Original Message-
Sorry, I thought it was a different thread but that whole copy/pasting
thing, I've always struggled with it! :)
Rob
On 12 September 2006 16:58, Rob Bosch wrote:
> Dave is cross-referencing
> http://cygwin.com/ml/cygwin/2006-09/msg00194.html
:) That's a slightly roundabo
out the hacking attempts.
The error is beyond my knowledge...sorry.
-Original Message-
From: Michael Sowka [mailto:[EMAIL PROTECTED]
Sent: Tuesday, September 12, 2006 8:42 AM
To: Rob Bosch
Subject: Re: Potential bug in sshd
Thanks Rob,
Ah yes, this explains the "zombie"
Sshd will spawn processes that deal with individual connections so even
though you stop the service there may still be sshd processes running. The
way to tell if your sshd daemon is stopped is to run a netstat -a | find
"ssh" | find "LISTEN". This will only find sshd processes that are
listening
Using cygwin1.dll from cvs checked out on 9/8. I built rsync using the
cygwin development package from cvs and also have openssh (not recompiled)
from cygwin package 1.5.21-1. Both these are running as services on Windows
2003 SP1 x64 using cygrunsrv. Under load, both the processes die. An
exam
just been getting
openssh and rsync services dying so I wasn't sure if this might be related
to the problem.
Thanks for the reference URL.
Rob
-Original Message-
From: Rob Bosch [mailto:[EMAIL PROTECTED]
Sent: Saturday, September 09, 2006 9:16 AM
To: 'cygwin@cygwin.com'
S
I was trying to compile rsync with the snapshot from 20060830 on Windows
Server 2003 x64 SP1. Ive successfully compiled the same source from the
snapshot on XP. To do the compile I'm trying to run autoconf-2.5x. I'm
getting the following error:
1148051 [main] perl 4528 modify_handle: virtual v
34 matches
Mail list logo
