On 02/13/2012 03:34 PM, Chester wrote:

On Mon, Feb 13, 2012 at 1:17 AM, Ralf-Peter Rohbeck [off-list ref] wrote:

quoted

Hello,
is it possible to set nodatacow on a per-file basis? I couldn't find anything.
If not, wouldn't that be a great feature to get around the performance issues with VM and database storage? Of course cloning should still cause COW.

IIRC this is already a feature in btrfs. I didn't catch the whole
talk, but Chris mentioned something like this at Scale 10x. I also
remember seeing a patch for it a while back (I think it was from liu
bo) that does this.

You're right, and I've made the prog patches which is against linux-ulit(chattr/lsattr):

http://www.spinics.net/lists/linux-btrfs/msg09604.html
http://www.spinics.net/lists/linux-btrfs/msg09605.html

but they are not merged yet.

thanks,
liubo

quoted

Thanks,
Ralf-Peter
--
To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

--
To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html