[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <1157245402.4398.6.camel@localhost.localdomain>
Date: Sat, 02 Sep 2006 21:03:22 -0400
From: Shaya Potter <spotter@...columbia.edu>
To: Trond Myklebust <trond.myklebust@....uio.no>
Cc: Josef Sipek <jsipek@...sunysb.edu>, linux-kernel@...r.kernel.org,
linux-fsdevel@...r.kernel.org, hch@...radead.org, akpm@...l.org,
viro@....linux.org.uk
Subject: Re: [PATCH 04/22][RFC] Unionfs: Common file operations
On Fri, 2006-09-01 at 18:57 -0400, Trond Myklebust wrote:
> On Fri, 2006-09-01 at 18:36 -0400, Shaya Potter wrote:
> > On Fri, 2006-09-01 at 18:20 -0400, Trond Myklebust wrote:
> >
> > > Race! You cannot open an underlying NFS file by name after it has been
> > > looked up: you have no guarantee that it hasn't been renamed.
> >
> > In a unionfs case that's not an issue. Nothing else is allowed to use
> > the backing store (i.e. the nfs fs) while unionfs is using it, so there
> > shouldn't be a renaming issue.
>
> How are you enforcing that on the server?
If I formatted a partition on a san w/ ext3, who would enforce that only
one machine has access to it at a time?
the administrator of the file system.
--
VGER BF report: H 0
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists