From: Pavel Machek Subject: Re: [PATCH 00/22][RFC] Unionfs: Stackable Namespace Unification Filesystem Date: Mon, 4 Sep 2006 22:33:46 +0200 Message-ID: <20060904203346.GA6646@elf.ucw.cz> References: <20060901013512.GA5788@fsl.cs.sunysb.edu> <20060903110507.GD4884@ucw.cz> <1157376506.4398.15.camel@localhost.localdomain> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: Josef Sipek , linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org, hch@infradead.org, akpm@osdl.org, viro@ftp.linux.org.uk Return-path: Received: from gprs189-60.eurotel.cz ([160.218.189.60]:65193 "EHLO amd.ucw.cz") by vger.kernel.org with ESMTP id S1751515AbWIDUeD (ORCPT ); Mon, 4 Sep 2006 16:34:03 -0400 To: Shaya Potter Content-Disposition: inline In-Reply-To: <1157376506.4398.15.camel@localhost.localdomain> Sender: linux-fsdevel-owner@vger.kernel.org List-Id: linux-fsdevel.vger.kernel.org On Mon 2006-09-04 09:28:26, Shaya Potter wrote: > On Sun, 2006-09-03 at 11:05 +0000, Pavel Machek wrote: > > Hi! > > > > > - Modifying a Unionfs branch directly, while the union is mounted, is > > > currently unsupported. Any such change may cause Unionfs to oops and it > > > can even result in data loss! > > > > I'm not sure if that is acceptable. Even root user should be unable to > > oops the kernel using 'normal' actions. > > As I said in the other case. imagine ext2/3 on a a san file system > where 2 systems try to make use of it. Will they not have issues? They probably will have issues (altrough I'm not sure, perhaps ext2 has been debugged enough), but they'll fix them (as opposed to document that oopses are okay). Pavel -- (english) http://www.livejournal.com/~pavelmachek (cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html