Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754211Ab3JVO3z (ORCPT ); Tue, 22 Oct 2013 10:29:55 -0400 Received: from mail-ee0-f41.google.com ([74.125.83.41]:62761 "EHLO mail-ee0-f41.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754041Ab3JVO3H (ORCPT ); Tue, 22 Oct 2013 10:29:07 -0400 Message-ID: <52668BAE.2000301@linux.com> Date: Tue, 22 Oct 2013 16:29:02 +0200 From: Levente Kurusa Reply-To: levex@linux.com User-Agent: Mozilla/5.0 (X11; Linux i686; rv:24.0) Gecko/20100101 Thunderbird/24.0 MIME-Version: 1.0 To: jiaweiwei CC: "Theodore Ts'o" , Vyacheslav Dubeyko , "linux-kernel@vger.kernel.org" , Harry Wei Subject: Re: [RFC] Rollback FS References: <20131020123521.GA15627@thunk.org> <5263D576.70202@linux.com> <5263DA0A.7030004@linux.com> 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: 1706 Lines: 40 2013-10-20 17:22 keltez?ssel, jiaweiwei ?rta: > On Sun, Oct 20, 2013 at 9:26 PM, Levente Kurusa wrote: >> 2013-10-20 15:19 keltez?ssel, jiaweiwei ?rta: >>> On Sun, Oct 20, 2013 at 9:07 PM, Levente Kurusa wrote: >>> [...] >>>>> 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. >>> >>> Delete/move a file with a parameter, which would keep the blocks or inodes >>> in-place. Or we would keep the blocks or inodes for several seconds. >> >> The problem with keeping the inodes/blocks for several seconds is >> that you would need to find a magic number that is not small enough, >> because if it is, then what if the user doesn't notice the problem >> during a long operation? If the magic number is big, then we waste a >> lot of space. >> >> The problem with the parameter thing is that again, all the different >> filesystems need to support that feature. We can't just tell Ext3 or JFFS2 on the VFS level, >> that 'Hey, keep those inodes in place incase someone just made himself some headache.' >> > > Above you said are what we should do. I never said that. > Don't waste time, let me design and > implement it. I would send design document for review, thanks. Do it, but I don't think it would be accepted. -- 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/