From owner-freebsd-stable@FreeBSD.ORG Thu May 21 02:57:13 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 1279CD8A for ; Thu, 21 May 2015 02:57:13 +0000 (UTC) Received: from mail-ig0-x22e.google.com (mail-ig0-x22e.google.com [IPv6:2607:f8b0:4001:c05::22e]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id C92CE1E26 for ; Thu, 21 May 2015 02:57:12 +0000 (UTC) Received: by igbhj9 with SMTP id hj9so5370745igb.1 for ; Wed, 20 May 2015 19:57:12 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=neosmart.net; s=google; h=content-type:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=yq0C9TxWBvA9ll0Dqj+Q9dI+n/0K8q5a8WLoyA4P+qg=; b=Ff0yzBDSoWgncwQ/u2BTfZmeB+JTdagErozwGJQ3U5gSdyGV6DDy/y5+q/8HQSDQGC LV17D+x+GGoEzW1Sn/94pXVhmHyWdeMNM9oRQDlqwpsjnwjwsDRAgFeNDVjE2et6WXSP Br7XjJROPmJ6hGDnOXr8S2Bqd2sMqOl+KLna4= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:content-type:mime-version:subject:from :in-reply-to:date:cc:content-transfer-encoding:message-id:references :to; bh=yq0C9TxWBvA9ll0Dqj+Q9dI+n/0K8q5a8WLoyA4P+qg=; b=RKhAIfBcGY3NcCyWWluei+Tym1SpdRUvsz6Yt0V/GeljIkTshADhAqusjuUs3zHgx5 izGozJKe64mczNuL74OIOjONidDzKwxrd8pHdFdmZW2o2QxV0ea0V3SiLMiHJDM59YxD 6gu8AnfBSqsMxn81WKBJFTyVZpu+FHJXgVk4eiefYUFrN5SADjW6EnZbWHMEyastNJ1Q QIhygkkC1rn208fb5+N4FfZM56V/Fg5sw55xxezac3qN/9DUP7AuUv7ptU3DGiaNiTH1 wedUjkxOAxfd4LwtvVKgAcVHFIMXWjgoR901rFTRWC3K8Un5PB38pM47mCOY08+GDeiw lXFw== X-Gm-Message-State: ALoCoQlteBY3v6SmluiXJ70A1ec6j2KiJOgvmQgq50fKrYNr8dAhN7h5bPgpgNe5iee0nPtJvVIb X-Received: by 10.50.30.69 with SMTP id q5mr1153147igh.11.1432177032218; Wed, 20 May 2015 19:57:12 -0700 (PDT) Received: from ?IPv6:2601:249:e00:ac50::12a5? ([2601:249:e00:ac50::12a5]) by mx.google.com with ESMTPSA id 7sm13853709iol.43.2015.05.20.19.57.10 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Wed, 20 May 2015 19:57:11 -0700 (PDT) Content-Type: text/plain; charset=utf-8 Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2100\)) Subject: Re: Status of NFS4.1 FS_RECLAIM in FreeBSD 10.1? From: Mahmoud Al-Qudsi In-Reply-To: <1013279983.41809469.1432173463439.JavaMail.root@uoguelph.ca> Date: Wed, 20 May 2015 21:57:09 -0500 Cc: freebsd-stable@freebsd.org Content-Transfer-Encoding: quoted-printable Message-Id: References: <1013279983.41809469.1432173463439.JavaMail.root@uoguelph.ca> To: Rick Macklem X-Mailer: Apple Mail (2.2100) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.20 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, 21 May 2015 02:57:13 -0000 On May 20, 2015, at 8:57 PM, Rick Macklem wrote: > Only the global RECLAIM_COMPLETE is implemented. I'll be honest that > I don't even really understand what the "single fs reclaim_complete" > semantics are and, as such, it isn't implemented. Thanks for verifying that. > I think it is meant to be used when a file system is migrated from > one server to another (transferring the locks to the new server) or > something like that. > Migration/replication isn't supported. Maybe someday if I figure out > what the RFC expects the server to do for this case. I wasn=E2=80=99t clear on if this was lock reclaiming or block = reclaiming. Thanks. >> I can mount and use NFSv3 shares just fine with ESXi from this same >> server, and >> can mount the same shares as NFSv4 from other clients (e.g. OS X) as >> well. >>=20 > This is NFSv4.1 specific, so NFSv4.0 should work, I think. Or just use = NFSv3. >=20 > rick For some reason, ESXi doesn=E2=80=99t do ESXi 4.0, only v3 or v4.1. I am using NFS v3 for now, but unless I=E2=80=99m mistaken, since = FreeBSD supports neither =E2=80=9Cnohide=E2=80=9D nor =E2=80=9Ccrossmnt=E2=80=9D there is = no way for a single export(/import) to cross ZFS filesystem boundaries.=20 I am using ZFS snapshots to manage virtual machine images, each machine has its own ZFS filesystem so I can snapshot and rollback individually. = But=20 this means that under NFSv3 (so far as I can tell), each =E2=80=9Cfolder=E2= =80=9D (ZFS fs)=20 must be mounted separately on the ESXi host. I can get around exporting=20= them each individually with the -alldirs parameter, but client-side, = there does not seem to be a way of traversing ZFS filesystem mounts without = explicitly mounting each and every one - a maintenance nightmare if there ever was = one. The only thing I can think of would be unions for the top-level = directory, but I=E2=80=99m very, very leery of the the nullfs/unionfs modules as they=E2=80=99ve = been a source of=20 system instability for us in the past (deadlocks, undetected lock = inversions, etc). That and I really rather a maintenance nightmare than a hack. Would you have any other suggestions? Thanks, Mahmoud