I'm a user of xfs and linux-vserver (http://linux-vserver.org/).
I'd like vserver to work better with xfs (or vice versa) and am trying to
proxy between the two development communities (which in the case of vserver
is not very large).
vservers are basically chroots on steroids: the host runs a single kernel,
but it isolates processes running in the guests from each other. There is a
"copy on write hardlink breaking" feature that allows you to hardlink files
(such as libc6) of different guests together (so that they only get mapped
into memory once), and have the kernel break the link if the inode is opened
for writing (by creating a copy and returning a FD to the copy).
This feature relies on inode flags (like the 'immutable' bit). vserver adds
two fields to the inode (the other is used to tag inodes with a context ID).
The kernel parts work, but xfs_repair breaks such filesystems because it
thinks the flags are invalid.
I approached David Chinner and Eric Sandeen about this on IRC, and they said
that the first step towards any improvement would be to share with this list
the parts of the vserver patch that affect xfs, so that's what I'm doing
Please find attached the output of
filterdiff -i '*xfs*' patch-3.7-vs188.8.131.52.diff
(the latter was obtained from http://vserver.13thfloor.at/Experimental/ but
the xfs specific parts apparently haven't changed in a while).
Andras Korn <korn at elan.rulez.org>
I ? Unicode.
Description: Text Data