From mboxrd@z Thu Jan 1 00:00:00 1970 From: Oren Laadan Subject: Re: [PATCH 00/16][cr][v3]: C/R file owner, locks, leases Date: Wed, 04 Aug 2010 15:16:17 -0400 Message-ID: <4C59BC81.80401@cs.columbia.edu> References: <1280877097-12377-1-git-send-email-sukadev@linux.vnet.ibm.com> <1280918720.2566.18.camel@localhost> <20100804190112.GA11571@us.ibm.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Steven Whitehouse , Serge Hallyn , Matt Helsley , Dan Smith , John Stultz , Matthew Wilcox , Jamie Lokier , linux-fsdevel@vger.kernel.org, Containers To: Sukadev Bhattiprolu Return-path: Received: from brinza.cc.columbia.edu ([128.59.29.8]:36682 "EHLO brinza.cc.columbia.edu" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S933091Ab0HDTRO (ORCPT ); Wed, 4 Aug 2010 15:17:14 -0400 In-Reply-To: <20100804190112.GA11571@us.ibm.com> Sender: linux-fsdevel-owner@vger.kernel.org List-ID: On 08/04/2010 03:01 PM, Sukadev Bhattiprolu wrote: > Steven Whitehouse [swhiteho@redhat.com] wrote: > | Hi, > | > | On Tue, 2010-08-03 at 16:11 -0700, Sukadev Bhattiprolu wrote: > |> Checkpoint/restart file owner, file-locks and file-lease information. > |> > | Can you explain roughly how this is intended to work, or point me at a > | document explaining it? > > Well, there is no document atm and I tried to explain how it is supposed > to work in the patches that restart file-locks (patches 4. 9, 16). > > | > | I'm trying to figure out how the file lock checkpoint will work with > | cluster filesystems, or if there needs to be a mechanism to turn this > | feature off for those filesystems. What prevents the lock state changing > | in an incompatible way between the checkpoint and the restore? > > But I see that your question is about the bigger picture. Given that > this question was asked on the previous version of the patchset, I will > add a FAQ/description in patch 0 next time. > > For now, please see: > > http://marc.info/?l=linux-fsdevel&m=127657580718791&w=2 > Would probably be a good idea to put something on the wiki and/or inside Documentation/checkpoint/... Oren