From owner-freebsd-hackers@FreeBSD.ORG Mon Dec 17 16:46:32 2012 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id BDE23134; Mon, 17 Dec 2012 16:46:32 +0000 (UTC) (envelope-from wojtek@wojtek.tensor.gdynia.pl) Received: from wojtek.tensor.gdynia.pl (wojtek.tensor.gdynia.pl [188.252.31.196]) by mx1.freebsd.org (Postfix) with ESMTP id 2E7888FC0A; Mon, 17 Dec 2012 16:46:31 +0000 (UTC) Received: from wojtek.tensor.gdynia.pl (localhost [127.0.0.1]) by wojtek.tensor.gdynia.pl (8.14.5/8.14.5) with ESMTP id qBHGkRwA001592; Mon, 17 Dec 2012 17:46:27 +0100 (CET) (envelope-from wojtek@wojtek.tensor.gdynia.pl) Received: from localhost (wojtek@localhost) by wojtek.tensor.gdynia.pl (8.14.5/8.14.5/Submit) with ESMTP id qBHGkRw5001589; Mon, 17 Dec 2012 17:46:27 +0100 (CET) (envelope-from wojtek@wojtek.tensor.gdynia.pl) Date: Mon, 17 Dec 2012 17:46:26 +0100 (CET) From: Wojciech Puchar To: Ivan Voras Subject: Re: iSCSI vs. SMB with ZFS. In-Reply-To: Message-ID: References: User-Agent: Alpine 2.00 (BSF 1167 2008-08-23) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Greylist: Sender passed SPF test, not delayed by milter-greylist-4.2.7 (wojtek.tensor.gdynia.pl [127.0.0.1]); Mon, 17 Dec 2012 17:46:27 +0100 (CET) Cc: freebsd-hackers@freebsd.org X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 17 Dec 2012 16:46:32 -0000 > With a network file system (either SMB or NFS, it doesn't matter), you > need to ask the server for *each* of the following situations: > * to ask the server if a file has been changed so the client can use > cached data (if the protocol supports it) > * to ask the server if a file (or a portion of a file) has been locked > by another client not really if there is only one user of file - then windows know this, but change to behaviour you described when there are more users. AND FINALLY the latter behaviour fails to work properly since windows XP (worked fine with windows 98). If you use programs that read/write share same files you may be sure data corruption would happen. you have to set locking = yes oplocks = no level2 oplocks = no to make it work properly but even more slow!. > This basically means that for almost every single IO, you need to ask > the server for something, which involves network traffic and round-trip > delays. Not that. The problem is that windows do not use all free memory for caching as with local or "local" (iSCSI) disk.