public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Bengt Larsson <lists.cygwin4@bengtl.net>
To: cygwin@cygwin.com
Subject: Re: NOACL leads to a massive speed slowdown in file system processes
Date: Sun, 13 Sep 2015 15:44:00 -0000	[thread overview]
Message-ID: <i46bvahk3frb9hq6l9279v2pl1h5ohgoqn@4ax.com> (raw)
In-Reply-To: <1750747142.592411.1442135988978.JavaMail.ngmail@webmail17.arcor-online.net>

tiwasey@arcor.de wrote:
>Hello, I've used Cygwin under WinXP and now Win8.1. Among others I'm using it to rsync big folders.  I had one big problem. On the destination the file system permissions where that wrong, that I could not enter the rsynced folders. As it is said in the internet, the solution for this is to use NOACL as fstab option. But that leads to massive speed slowdown. rsync processes took around 10 times as before. The same for du on a complex directory. Without NOACL it needed in one example 5sec and with NOACL around 10 minutes. So it seems like that the NOACL option leads to problems with file system processes. Whats the reason and is there a solution for that?
>
>Thank you for helping.

Try adding the "notexec" option. If it's mounted "noacl" Cygwin checks
for executable by opening the file and checking the two first bytes.

--
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

  reply	other threads:[~2015-09-13 15:44 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-13  9:19 tiwasey
2015-09-13 15:44 ` Bengt Larsson [this message]
2015-09-13 15:59   ` Bengt Larsson
2015-09-13 17:36   ` Mikkel Filla
2015-09-13 18:35     ` Andrey Repin
2015-09-14  6:39 tiwasey
2015-09-14 18:50 ` Andrey Repin

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=i46bvahk3frb9hq6l9279v2pl1h5ohgoqn@4ax.com \
    --to=lists.cygwin4@bengtl.net \
    --cc=cygwin@cygwin.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).