From: starlight.2012q2@binnacle.cx
To: cygwin@cygwin.com
Subject: Re: CYGWIN inode over Samba share not constructed from IndexNumber
Date: Fri, 11 May 2012 16:38:00 -0000 [thread overview]
Message-ID: <6.2.5.6.2.20120511122904.05ccc3b8@binnacle.cx> (raw)
In-Reply-To: <20120511162351.GK13090@calimero.vinschen.de>
At 06:23 PM 5/11/2012 +0200, Corinna Vinschen wrote:
>Additionally, the returned file ID must be > 0xffffffff,
>otherwise we don't trust the server to generate
>usefule file IDs. This usually only affects remote
>NT4 NTFS and Samba < 3.0.
Running Samba 3.6.4 and it is returning
IndexNumber: 0x81f
which is the actual inode value and the
Samba devs indicated this is the behavior
as designed.
Also
$ getVolInfo //siobhan/d | fgrep -i ACL
FILE_PERSISTENT_ACLS : TRUE
Thank you very much for your reply.
======
$ getVolInfo //siobhan/d
Device Type : 7
Characteristics : 10
Volume Name : <d>
Serial Number : 2717179013
Max Filenamelength : 255
Filesystemname : <NTFS>
Flags : 1002f
FILE_CASE_SENSITIVE_SEARCH : TRUE
FILE_CASE_PRESERVED_NAMES : TRUE
FILE_UNICODE_ON_DISK : TRUE
FILE_PERSISTENT_ACLS : TRUE
FILE_FILE_COMPRESSION : FALSE
FILE_VOLUME_QUOTAS : TRUE
FILE_SUPPORTS_SPARSE_FILES : FALSE
FILE_SUPPORTS_REPARSE_POINTS: FALSE
FILE_SUPPORTS_REMOTE_STORAGE: FALSE
FILE_VOLUME_IS_COMPRESSED : FALSE
FILE_SUPPORTS_OBJECT_IDS : TRUE
FILE_SUPPORTS_ENCRYPTION : FALSE
FILE_NAMED_STREAMS : FALSE
FILE_READ_ONLY_VOLUME : FALSE
FILE_SEQUENTIAL_WRITE_ONCE : FALSE
FILE_SUPPORTS_TRANSACTIONS : FALSE
--
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
next prev parent reply other threads:[~2012-05-11 16:38 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-11 15:53 starlight.2012q2
2012-05-11 16:22 ` Corinna Vinschen
2012-05-11 16:24 ` Corinna Vinschen
2012-05-11 16:38 ` starlight.2012q2 [this message]
2012-05-11 16:58 starlight.2012q2
2012-05-11 17:59 ` Corinna Vinschen
2012-05-11 19:49 ` starlight.2012q2
2012-05-11 21:15 ` Jeremy Allison
2012-05-12 10:54 ` Corinna Vinschen
2012-05-14 17:33 ` Jeremy Allison
2012-05-21 10:49 ` Corinna Vinschen
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=6.2.5.6.2.20120511122904.05ccc3b8@binnacle.cx \
--to=starlight.2012q2@binnacle.cx \
--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).