X-Spam-Check-By: sourceware.org Mime-Version: 1.0 (Apple Message framework v746.2) In-Reply-To: <20051203094941.GB2999@calimero.vinschen.de> References: <20051130171137.GE2999@calimero.vinschen.de> <57A85FA1-5088-4CB9-8998-9853FC0DDBB1@rehley.net> <20051201213806.GM2999@calimero.vinschen.de> <9ED848C7-59B5-4009-BB85-5BCA9F5E3F53@rehley.net> <20051202111414.GO2999@calimero.vinschen.de> <20051203094941.GB2999@calimero.vinschen.de> Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Message-Id: Content-Transfer-Encoding: 7bit From: Peter Rehley Subject: Re: Call for testing Cygwin snapshot (problem with inode numbers. problem figured out) Date: Sun, 4 Dec 2005 11:41:15 -0800 To: cygwin@cygwin.com X-IsSubscribed: yes Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm Precedence: bulk List-Unsubscribe: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.com On Dec 3, 2005, at 1:49 AM, Corinna Vinschen wrote: > On Dec 2 12:34, Peter Rehley wrote: >> On Dec 2, 2005, at 3:14 AM, Corinna Vinschen wrote: >>> The problem is, that your Samba version apparently screws up the >>> inode >>> information and we have re-enabled using the inode numbers sent from >>> remote file systems which are supposed to be capable of that. For >>> this >>> we use the HAS_PERSISTENT_ACLS property. >>> >>> What Samba version is your Mac OS X using? I'm using 3.0.20a for >>> which >>> the inode information is useable. Is Samba a part of the OS >>> packages or >>> did you install it from an external source? Is it a rather old one? >>> Can you upgrade? The problem is that there's no way for us to >>> distinguish >>> between a newer and an older version of Samba. I would rather not >>> lose >>> the inode information when available. >>> >> I'm using mac os x 10.4.3 which is using samba version 3.0.10. So >> it's not that old. However, I did find one reference that implied >> that mac did something funny for acl's. >> >> I'm going to try install a non-apple version of samba and see what >> happens. > > Keep us informed, please. I'd rather keep the inode handling as it > is now, but we should at least know if there are ways to solve the > problem one way or the other. Can I say "D'oh"? I knew I could ;) The problem turned out to be a samba configuration issue. Several months ago I had added the parameter "large readwrite = no" to my smb.conf file in order to speed up transfers between my mac and windows. When it's in the configuration file the inodes are messed up. When I remove it, the inodes are fine. I get the same behavior on a non-apple version of samba... in my case I tried the darwinports version, 3.0.20b, and large readwrite had the same problem. So problem solved. Thanks for all you help, Peter > > > Corinna > > -- > Corinna Vinschen Please, send mails regarding > Cygwin to > Cygwin Project Co-Leader cygwin AT cygwin DOT com > Red Hat, Inc. > > -- > Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple > Problem reports: http://cygwin.com/problems.html > Documentation: http://cygwin.com/docs.html > FAQ: http://cygwin.com/faq/ > > -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/