Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751523Ab3JTLqk (ORCPT ); Sun, 20 Oct 2013 07:46:40 -0400 Received: from mail-vb0-f54.google.com ([209.85.212.54]:35759 "EHLO mail-vb0-f54.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751221Ab3JTLqj (ORCPT ); Sun, 20 Oct 2013 07:46:39 -0400 MIME-Version: 1.0 In-Reply-To: References: Date: Sun, 20 Oct 2013 13:46:38 +0200 Message-ID: Subject: Re: [RFC] Rollback FS From: Richard Weinberger To: jiaweiwei Cc: Vyacheslav Dubeyko , "linux-kernel@vger.kernel.org" , Harry Wei Content-Type: text/plain; charset=ISO-8859-1 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1016 Lines: 29 On Sun, Oct 20, 2013 at 1:37 PM, jiaweiwei wrote: > On Sun, Oct 20, 2013 at 6:43 PM, Vyacheslav Dubeyko wrote: >> Anyway, you need to use Copy-On-Write (COW) approach for such file system. >> But there are file systems that implements snapshot approach yet: NILFS2, ext3cow, >> Next3, and so on. >> > > Any file system should rollback but not specific ones. Therefore, a > VFS like mechanism should be designed and implemented. -ENOPATCH >> Do you really want to implement something likewise snapshot feature in a file system >> from the scratch? >> > > Maybe, I would give detail design, thanks. Linux's next generation filesystem, btrfs, has already support for file and volume level snapshots. -- Thanks, //richard -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/