From: Jaegeuk Kim <jaegeuk@kernel.org>
To: Gao Xiang <hsiangkao@redhat.com>
Cc: linux-fsdevel@vger.kernel.org, linux-f2fs-devel@lists.sourceforge.net
Subject: Re: [f2fs-dev] Fwd: Any tools of f2fs to inspect infos?
Date: Wed, 1 Jul 2020 09:08:08 -0700 [thread overview]
Message-ID: <20200701160808.GA1704717@google.com> (raw)
In-Reply-To: <20200701091622.GA5411@xiangao.remote.csb>
On 07/01, Gao Xiang wrote:
> (cc linux-f2fs-devel, Jaegeuk, Chao.
> It'd be better to ask related people and cc the corresponding list.)
>
> On Wed, Jul 01, 2020 at 03:29:41PM +0800, lampahome wrote:
> > As title
> >
> > Any tools of f2fs to inspect like allocated segments, hot/warm/cold
> > ratio, or gc is running?
# cat /sys/kernel/debug/f2fs/status ?
> >
> > thx
_______________________________________________
Linux-f2fs-devel mailing list
Linux-f2fs-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel
next prev parent reply other threads:[~2020-07-01 16:08 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAB3eZfsO0ZN_79oaFpooJ32WNZwwyaS4GBb+W6jR=buU-VczAA@mail.gmail.com>
2020-07-01 9:16 ` [f2fs-dev] Fwd: Any tools of f2fs to inspect infos? Gao Xiang
2020-07-01 16:08 ` Jaegeuk Kim [this message]
2020-07-02 3:00 ` lampahome
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=20200701160808.GA1704717@google.com \
--to=jaegeuk@kernel.org \
--cc=hsiangkao@redhat.com \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=linux-fsdevel@vger.kernel.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).