From: Jaegeuk Kim <jaegeuk@kernel.org>
To: Chao Yu <yuchao0@huawei.com>
Cc: zhangdianfang@huawei.com, linux-f2fs-devel@lists.sourceforge.net
Subject: Re: [PATCH v3] f2fs: report error if quota off error during umount
Date: Sat, 28 Jul 2018 19:06:01 -0700 [thread overview]
Message-ID: <20180729020601.GI83620@jaegeuk-macbookpro.roam.corp.google.com> (raw)
In-Reply-To: <d39bdd51-f5e2-29df-b8ca-73e6c68bc85a@huawei.com>
On 07/28, Chao Yu wrote:
> Ping,
Please check dev-test.
>
> On 2018/6/26 16:34, Chao Yu wrote:
> > On 2018/6/26 13:12, Yunlei He wrote:
> >> Now, we depend on fsck to ensure quota file data is ok,
> >> so we scan whole partition if checkpoint without umount
> >> flag. It's same for quota off error case, which may make
> >> quota file data inconsistent.
> >>
> >> Signed-off-by: Yunlei He <heyunlei@huawei.com>
> >
> > Reviewed-by: Chao Yu <yuchao0@huawei.com>
> >
> > Thanks,
> >
> >
> > ------------------------------------------------------------------------------
> > Check out the vibrant tech community on one of the world's most
> > engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> > _______________________________________________
> > Linux-f2fs-devel mailing list
> > Linux-f2fs-devel@lists.sourceforge.net
> > https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel
> >
> >
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
next prev parent reply other threads:[~2018-07-29 2:06 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-26 5:12 [PATCH v3] f2fs: report error if quota off error during umount Yunlei He
2018-06-26 8:34 ` Chao Yu
2018-07-28 9:49 ` Chao Yu
2018-07-29 2:06 ` Jaegeuk Kim [this message]
2018-07-29 3:07 ` Chao Yu
2018-07-29 3:41 ` Jaegeuk Kim
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20180729020601.GI83620@jaegeuk-macbookpro.roam.corp.google.com \
--to=jaegeuk@kernel.org \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=yuchao0@huawei.com \
--cc=zhangdianfang@huawei.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.