@openindiana.org
Subject: Re: [OpenIndiana-discuss] Case sensitivity mixed vs
sensitive
Message-ID: 5394cc3a.5040...@workingcode.com
Content-Type: text/plain; charset=ISO-8859-1
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 6/8/2014 6:06 AM, Cal Sawyer wrote:
Thanks for your responses, Rich
--
Message: 3
Date: Sat, 7 Jun 2014 07:48:52 +0200
From: John Ryan john.r...@bsse.ethz.ch
To: openindiana-discuss@openindiana.org
Subject: Re: [OpenIndiana-discuss] Case sensitivity mixed vs
sensitive
Message-ID: 5392a7c4.5020...@bsse.ethz.ch
Content-Type: text/plain; charset=ISO-8859-1; format
On 08/06/2014 12:06, Cal Sawyer wrote:
Further investigation shows that any dataset i create w/o specifying
casesensitivity=sensitive during zfs create defaults to insensitive,
although the pool itself is case sensitive. Is this intended behaviour and
if so why?
I cannot confirm what you are
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 6/8/2014 6:06 AM, Cal Sawyer wrote:
Thanks for your responses, Rich and John
In my examples, i was creating *only *new files and directories.
Further investigation shows that any dataset i create w/o
specifying casesensitivity=sensitive
Hello
Our 151a8 server is an rsnapshot collector using rsync. Since setting
it up a few weeks ago, i've been noting flurries of file creation errors
in the sync logs. It's taken days to figure this out owing to the large
amounts of data we're transferring, but it's boiling down to case
On Fri, 6 Jun 2014, Cal Sawyer wrote:
# touch a
# touch A
(ok, so far so good ...)
Did you do an ls after those commands? If a file exists, touch
won't complain. It'll just silently do what you asked it too:
update the file's mtime to the current time. In other words,
your touch commands
On 6/06/2014 1:52 PM, Cal Sawyer wrote:
Hello
Our 151a8 server is an rsnapshot collector using rsync. Since setting
it up a few weeks ago, i've been noting flurries of file creation
errors in the sync logs. It's taken days to figure this out owing to
the large amounts of data we're