From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from szxga04-in.huawei.com ([45.249.212.190]:10655 "EHLO huawei.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1725832AbeHJLJx (ORCPT ); Fri, 10 Aug 2018 07:09:53 -0400 Subject: Re: [PATCH v3] f2fs: checkpoint disabling To: Daniel Rosenberg , Jaegeuk Kim , Jonathan Corbet , CC: , , , References: <20180807234843.129387-1-drosen@google.com> From: Chao Yu Message-ID: Date: Fri, 10 Aug 2018 16:40:53 +0800 MIME-Version: 1.0 In-Reply-To: <20180807234843.129387-1-drosen@google.com> Content-Type: text/plain; charset="windows-1252" Content-Language: en-US Content-Transfer-Encoding: 7bit Sender: linux-fsdevel-owner@vger.kernel.org List-ID: Hi Daniel, On 2018/8/8 7:48, Daniel Rosenberg wrote: > This adds a lightweight non-persistent snapshotting scheme to f2fs. > > To use, mount with the option checkpoint=disable, and to return to > normal operation, remount with checkpoint=enable. If the filesystem > is shut down before remounting with checkpoint=enable, it will revert > back to its apparent state when it was first mounted with > checkpoint=disable. This is useful for situations where you wish to be > able to roll back the state of the disk in case of some critical > failure. When filesystem is full, statfs shown abnormally as below: /dev/zram0 2095104 -17177769548 17179864652 - /mnt/f2fs I guess it's related to this patch, could you have a look at this? Thanks,