This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
Home Products Support Community News


[Xen-users] Re: UnionFS in initrd

To: xen-users@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-users] Re: UnionFS in initrd
From: Charles Duffy <cduffy@xxxxxxxxxxx>
Date: Thu, 10 Nov 2005 10:53:36 -0600
Delivery-date: Thu, 10 Nov 2005 17:00:04 +0000
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <4373750D.40005@xxxxxxxxxxxxxxx>
List-help: <mailto:xen-users-request@lists.xensource.com?subject=help>
List-id: Xen user discussion <xen-users.lists.xensource.com>
List-post: <mailto:xen-users@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
References: <4373750D.40005@xxxxxxxxxxxxxxx>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mozilla Thunderbird 1.0.6 (X11/20050716)
Dennis wrote:
I've played around with UnionFS a bit.  I like the idea for a COW file

It doesn't work properly right now for a root FS running a completely unmodified distribution; there are some bad interactions with procfs (/proc/<pid>/exe ends up pointing at the particular UnionFS branch rather than at the UnionFS filesystem itself, which confuses a number of distributions' tools for checking daemon status), and the unionfs patch I've been using to override this issue via changing /proc's symlink resolution is a bit crashy (though there are newer proposed patches I haven't been able to test with yet). See my posts on gmane.comp.file-systems.unionfs.general and the surrounding threads.

Xen-users mailing list

<Prev in Thread] Current Thread [Next in Thread>