Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751159Ab3JTM7R (ORCPT ); Sun, 20 Oct 2013 08:59:17 -0400 Received: from mail-wg0-f44.google.com ([74.125.82.44]:53750 "EHLO mail-wg0-f44.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751003Ab3JTM7Q (ORCPT ); Sun, 20 Oct 2013 08:59:16 -0400 MIME-Version: 1.0 In-Reply-To: <20131020123521.GA15627@thunk.org> References: <20131020123521.GA15627@thunk.org> Date: Sun, 20 Oct 2013 20:59:14 +0800 Message-ID: Subject: Re: [RFC] Rollback FS From: jiaweiwei To: "Theodore Ts'o" , jiaweiwei , 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: 960 Lines: 31 On Sun, Oct 20, 2013 at 8:35 PM, Theodore Ts'o wrote: > On Sun, Oct 20, 2013 at 07:37:01PM +0800, jiaweiwei wrote: >> >> Any file system should rollback but not specific ones. Therefore, a >> VFS like mechanism should be designed and implemented. > > And what if the blocks or inodes used for the files that were deleted > have already been used and overwritten? A good catch. Following ideas would be suitable. 1, Keep the blocks or inodes by a parameter we give. 2, Keep the blocks or inodes for several seconds. > >> Maybe, I would give detail design, thanks. > > I encourage you to try to do that; you might find it to be an > educational exercise. > Yeah, I would, thanks. -- do kernel -- 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/