Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751253Ab3JTNHI (ORCPT ); Sun, 20 Oct 2013 09:07:08 -0400 Received: from mail-ea0-f176.google.com ([209.85.215.176]:35319 "EHLO mail-ea0-f176.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751019Ab3JTNHG (ORCPT ); Sun, 20 Oct 2013 09:07:06 -0400 Message-ID: <5263D576.70202@linux.com> Date: Sun, 20 Oct 2013 15:07:02 +0200 From: Levente Kurusa User-Agent: Mozilla/5.0 (X11; Linux i686; rv:24.0) Gecko/20100101 Thunderbird/24.0 MIME-Version: 1.0 To: jiaweiwei , "Theodore Ts'o" , Vyacheslav Dubeyko , "linux-kernel@vger.kernel.org" , Harry Wei Subject: Re: [RFC] Rollback FS References: <20131020123521.GA15627@thunk.org> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1182 Lines: 38 2013-10-20 14:59 keltez?ssel, jiaweiwei ?rta: > 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. Keep them where? On the HDD? We just deleted/moved that. In memory? How about a 4+ GB file(s)? > >> >>> 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. > > I think he meant to be ironic. -- Regards, Levente Kurusa -- 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/