From mboxrd@z Thu Jan 1 00:00:00 1970 From: Miklos Szeredi Subject: Re: Unionmount status? Date: Fri, 15 Apr 2011 14:48:05 +0200 Message-ID: References: <4DA4B6A8.7030804@gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Cc: Jiri Kosina , Ric Wheeler , linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org, David Howells , Ian Kent , Jeff Moyer , Christoph Hellwig To: Michal Suchanek Return-path: Received: from mail-bw0-f46.google.com ([209.85.214.46]:58916 "EHLO mail-bw0-f46.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752938Ab1DOMsH (ORCPT ); Fri, 15 Apr 2011 08:48:07 -0400 In-Reply-To: Sender: linux-fsdevel-owner@vger.kernel.org List-ID: On Fri, Apr 15, 2011 at 2:34 PM, Michal Suchanek wrote: > On 15 April 2011 14:29, Miklos Szeredi wrote: >> 2) take whiteout/opaque support from union mounts and use that > > How far from importing full unionmount is that? Whiteout/opaque support is quite separate from the rest of union mounts, and could be reusable for overlayfs. There are several reasons why I didn't want to go that way with: - lots of filesystems would have to be updated - it introduces incompatibility in the filesystem format, which can be a real pain (not for tmpfs, obviously, since tmpfs doesn't have a persistent backing) There *are* advantages to doing whiteouts in the filesystem, for example it makes file removal atomic. But atomicity is something that needs to be addressed in lots of other places (e.g. copy up) not just during whiteout, and there are other ways to do that than push the responsibility into each and every filesystem. Thanks, Miklos