From: Sahitya Tummala <stummala@codeaurora.org>
To: Chao Yu <yuchao0@huawei.com>
Cc: Jaegeuk Kim <jaegeuk@kernel.org>,
linux-f2fs-devel@lists.sourceforge.net,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] f2fs: ratelimit recovery messages
Date: Tue, 28 May 2019 08:35:09 +0530 [thread overview]
Message-ID: <20190528030509.GE10043@codeaurora.org> (raw)
In-Reply-To: <94025a6d-f485-3811-5521-ed5c9b4d1d77@huawei.com>
Hi Chao,
On Tue, May 28, 2019 at 09:23:15AM +0800, Chao Yu wrote:
> Hi Sahitya,
>
> On 2019/5/27 21:10, Sahitya Tummala wrote:
> > Ratelimit the recovery logs, which are expected in case
> > of sudden power down and which could result into too
> > many prints.
>
> FYI
>
> https://lore.kernel.org/patchwork/patch/973837/
>
> IMO, we need those logs to provide evidence during trouble-shooting of file data
> corruption or file missing problem...
>
In one of the logs, I have noticed there were ~400 recovery prints in the
kernel bootup. I noticed your patch above and with that now we can always get
the error returned by f2fs_recover_fsync_data(), which should be good enough
for knowing the status of recovered files I thought. Do you think we need
individually each file status as well?
Thanks,
> So I suggest we can keep log as it is in recover_dentry/recover_inode, and for
> the log in do_recover_data, we can record recovery info [isize_kept,
> recovered_count, err ...] into struct fsync_inode_entry, and print them in
> batch, how do you think?
>
> Thanks,
>
> >
> > Signed-off-by: Sahitya Tummala <stummala@codeaurora.org>
> > ---
> > v2:
> > - fix minor formatting and add new line for printk
> >
> > fs/f2fs/recovery.c | 18 +++++++++---------
> > 1 file changed, 9 insertions(+), 9 deletions(-)
> >
> > diff --git a/fs/f2fs/recovery.c b/fs/f2fs/recovery.c
> > index e04f82b..60d7652 100644
> > --- a/fs/f2fs/recovery.c
> > +++ b/fs/f2fs/recovery.c
> > @@ -188,8 +188,8 @@ static int recover_dentry(struct inode *inode, struct page *ipage,
> > name = "<encrypted>";
> > else
> > name = raw_inode->i_name;
> > - f2fs_msg(inode->i_sb, KERN_NOTICE,
> > - "%s: ino = %x, name = %s, dir = %lx, err = %d",
> > + printk_ratelimited(KERN_NOTICE
> > + "%s: ino = %x, name = %s, dir = %lx, err = %d\n",
> > __func__, ino_of_node(ipage), name,
> > IS_ERR(dir) ? 0 : dir->i_ino, err);
> > return err;
> > @@ -292,8 +292,8 @@ static int recover_inode(struct inode *inode, struct page *page)
> > else
> > name = F2FS_INODE(page)->i_name;
> >
> > - f2fs_msg(inode->i_sb, KERN_NOTICE,
> > - "recover_inode: ino = %x, name = %s, inline = %x",
> > + printk_ratelimited(KERN_NOTICE
> > + "recover_inode: ino = %x, name = %s, inline = %x\n",
> > ino_of_node(page), name, raw->i_inline);
> > return 0;
> > }
> > @@ -642,11 +642,11 @@ static int do_recover_data(struct f2fs_sb_info *sbi, struct inode *inode,
> > err:
> > f2fs_put_dnode(&dn);
> > out:
> > - f2fs_msg(sbi->sb, KERN_NOTICE,
> > - "recover_data: ino = %lx (i_size: %s) recovered = %d, err = %d",
> > - inode->i_ino,
> > - file_keep_isize(inode) ? "keep" : "recover",
> > - recovered, err);
> > + printk_ratelimited(KERN_NOTICE
> > + "recover_data: ino = %lx (i_size: %s) recovered = %d, err = %d\n",
> > + inode->i_ino,
> > + file_keep_isize(inode) ? "keep" : "recover",
> > + recovered, err);
> > return err;
> > }
> >
> >
--
--
Sent by a consultant of the Qualcomm Innovation Center, Inc.
The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum.
next prev parent reply other threads:[~2019-05-28 3:05 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-27 13:10 [PATCH v2] f2fs: ratelimit recovery messages Sahitya Tummala
2019-05-28 1:23 ` Chao Yu
2019-05-28 1:23 ` Chao Yu
2019-05-28 3:05 ` Sahitya Tummala [this message]
2019-05-28 3:17 ` Chao Yu
2019-05-28 3:17 ` Chao Yu
2019-05-28 3:24 ` Sahitya Tummala
2019-05-28 3:30 ` [f2fs-dev] " Gao Xiang
2019-05-28 3:30 ` Gao Xiang
2019-05-28 7:37 ` Chao Yu
2019-05-28 7:37 ` Chao Yu
2019-05-28 11:05 ` Joe Perches
2019-05-28 12:16 ` Joe Perches
2019-05-29 2:03 ` Chao Yu
2019-05-29 2:03 ` Chao Yu
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=20190528030509.GE10043@codeaurora.org \
--to=stummala@codeaurora.org \
--cc=jaegeuk@kernel.org \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=yuchao0@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.