From owner-freebsd-stable@FreeBSD.ORG Thu Jan 22 13:28:35 2015 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 5CF679D for ; Thu, 22 Jan 2015 13:28:35 +0000 (UTC) Received: from smarthost1.greenhost.nl (smarthost1.greenhost.nl [195.190.28.81]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 203E3372 for ; Thu, 22 Jan 2015 13:28:34 +0000 (UTC) Received: from smtp.greenhost.nl ([213.108.104.138]) by smarthost1.greenhost.nl with esmtps (TLS1.0:RSA_AES_256_CBC_SHA1:32) (Exim 4.72) (envelope-from ) id 1YEHnU-00057F-00 for freebsd-stable@freebsd.org; Thu, 22 Jan 2015 14:28:31 +0100 Content-Type: text/plain; charset=iso-8859-15; format=flowed; delsp=yes To: freebsd-stable@freebsd.org Date: Thu, 22 Jan 2015 14:27:42 +0100 Subject: mmap on tmpfs not updating mtime MIME-Version: 1.0 Content-Transfer-Encoding: 7bit From: "Ronald Klop" Message-ID: User-Agent: Opera Mail/1.0 (Win32) X-Authenticated-As-Hash: 398f5522cb258ce43cb679602f8cfe8b62a256d1 X-Virus-Scanned: by clamav at smarthost1.samage.net X-Spam-Level: - X-Spam-Score: -1.0 X-Spam-Status: No, score=-1.0 required=5.0 tests=ALL_TRUSTED, BAYES_20 autolearn=disabled version=3.3.1 X-Scan-Signature: 9090f8a1960d7f777b94d17b6f36e747 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 22 Jan 2015 13:28:35 -0000 Hello, Tested on 10.1-STABLE/amd64 and 11-CURRENT/arm. I spotted this because rrdtool didn't update mtime of the database files so they were not backuped by my rsync scripts. I remembered and found these mails from November 2014 about mtime+mmap on ZFS. https://lists.freebsd.org/pipermail/freebsd-stable/2014-November/081138.html which resulted in https://lists.freebsd.org/pipermail/freebsd-stable/2014-December/081184.html My tests with the test program in the November mails result in: On 10.1-STABLE/ZFS its OK: $ 14:18:08 ronald@sjakie [~/test] ls -lT mdata; /tmp/a.out mdata; ls -lT mdata -rw------- 1 ronald staff 1024 Jan 22 14:18:08 2015 mdata -rw------- 1 ronald staff 1024 Jan 22 14:18:10 2015 mdata On 11/UFS its OK: $ 14:16:16 ronald@sheeva [~/test] ls -lT mdata; /tmp/a.out mdata; ls -lT mdata -rw------- 1 ronald staff 1024 Jan 22 14:16:16 2015 mdata -rw------- 1 ronald staff 1024 Jan 22 14:16:21 2015 mdata On 11/tmpfs it fails: (same on 10.1-STABLE/tmpfs) $ 14:15:44 ronald@sheeva [/tmp] ls -lT mdata; /tmp/a.out mdata; ls -lT mdata -rw------- 1 ronald wheel 1024 Jan 22 14:15:37 2015 mdata -rw------- 1 ronald wheel 1024 Jan 22 14:15:37 2015 mdata Should a similar patch as ZFS got be applied to tmpfs? Regards, Ronald.