[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <977288EE-C80D-4808-93E6-E019CA1DDC58@dubeyko.com>
Date: Sun, 20 Oct 2013 16:32:12 +0400
From: Vyacheslav Dubeyko <slava@...eyko.com>
To: Richard Weinberger <richard.weinberger@...il.com>
Cc: jiaweiwei <jiaweiwei.xiyou@...il.com>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
Harry Wei <harryxiyou@...il.com>
Subject: Re: [RFC] Rollback FS
On Oct 20, 2013, at 3:46 PM, Richard Weinberger wrote:
> On Sun, Oct 20, 2013 at 1:37 PM, jiaweiwei <jiaweiwei.xiyou@...il.com> wrote:
>> On Sun, Oct 20, 2013 at 6:43 PM, Vyacheslav Dubeyko <slava@...eyko.com> 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
Yes, I doubt also that it makes sense to implement such feature on VFS level only.
Anyway, it needs to have support of snapshot feature on concrete file system level.
Otherwise, if it doesn't take into account a concrete file system's internal techniques
then it will have such nonsense as COW under COW. :)
Maybe, VFS needs in transparent rollback support likewise online resize. But such
feature should be based on concrete file systems' internal techniques.
With the best regards,
Vyacheslav Dubeyko.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists