From owner-freebsd-questions@FreeBSD.ORG Wed Mar 4 15:45:03 2015 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 64F2C142 for ; Wed, 4 Mar 2015 15:45:03 +0000 (UTC) Received: from mail.cyberleo.net (paka.cyberleo.net [216.226.128.180]) by mx1.freebsd.org (Postfix) with ESMTP id 43604665 for ; Wed, 4 Mar 2015 15:45:02 +0000 (UTC) Received: from [172.16.44.4] (vitani.den.cyberleo.net [216.80.73.130]) by mail.cyberleo.net (Postfix) with ESMTPSA id CFFA61BD2B; Wed, 4 Mar 2015 10:38:42 -0500 (EST) Message-ID: <54F72701.3030704@cyberleo.net> Date: Wed, 04 Mar 2015 09:38:41 -0600 From: CyberLeo Kitsana User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.3.0 MIME-Version: 1.0 To: Mike Tancsa , freebsd-questions Subject: Re: nfs mounted /tmp vs disk mounted /tmp References: <54F62D81.4060407@sentex.net> In-Reply-To: <54F62D81.4060407@sentex.net> Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 04 Mar 2015 15:45:03 -0000 On 03/03/2015 03:54 PM, Mike Tancsa wrote: > > While trying to test in the lab a migration of disks from an old pci-x > arcmrs array to a pcie card, I ran into an odd problem with the cli and > raid management daemon. I would start up the programs and they would > immediately exit > > Looking at the truss output, it seemed to bork soon after it tried to > create a file in /tmp. Testing all the same hardware, but then booting > from a disk, it worked. Back to netboot, but this time with /tmp > mounted via tmpfs, it also worked. So it seems there is something about > having tmp mounted via nfs that causes the program to die. The issue > seems to be the setting of locks. I am curious, is this something that > can be worked around in nfs, or due to the nature of nfs, this is not > possible ? I think I saw this same issue with virtual box in a netboot > environment > (https://lists.freebsd.org/pipermail/freebsd-emulation/2014-July/011693.html) > fcntl(4,F_SETLKW,0x7ffffffcde10) ERR#45 'Operation not > supported' The fcntl(2) manpage says that F_SETLKW is for advisory locking. Does your NFS infrastructure support advisory locks? Is lockd(8) running? -- Fuzzy love, -CyberLeo Technical Administrator CyberLeo.Net Webhosting http://www.CyberLeo.Net Furry Peace! - http://www.fur.com/peace/