linux-f2fs-devel.lists.sourceforge.net archive mirror
 help / color / mirror / Atom feed
From: Chao Yu <chao@kernel.org>
To: Jaegeuk Kim <jaegeuk@kernel.org>
Cc: Patrick Doyle <wpdster@gmail.com>,
	linux-f2fs-devel@lists.sourceforge.net
Subject: Re: Out of inodes on my f2fs partition
Date: Wed, 5 Sep 2018 23:49:20 +0800	[thread overview]
Message-ID: <7e01fdd5-f39e-793b-97d7-72b93f567579@kernel.org> (raw)
In-Reply-To: <20180830165845.GB3742@jaegeuk-macbookpro.roam.corp.google.com>

Jaegeuk,

I missed to reply this thread.

On 2018/8/31 0:58, Jaegeuk Kim wrote:
> Chao,
> 
> It seems we may need to consider tune.f2fs for this case.

It may need to expand NAT size, which needs a extra resize operation, or we just
need to consider non-expanding case?

> Could you TAL?
What does TAL mean... I didn't find out the meaning even though via google.

Thanks,

> 
> Thanks,

------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot

  parent reply	other threads:[~2018-09-05 15:49 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-08-30 14:44 Out of inodes on my f2fs partition Patrick Doyle
2018-08-30 15:20 ` Chao Yu
2018-08-30 15:30   ` Patrick Doyle
2018-08-30 15:38     ` Patrick Doyle
2018-08-30 15:39     ` Chao Yu
2018-08-30 15:45       ` Patrick Doyle
2018-08-30 15:50         ` Chao Yu
2018-08-30 16:58           ` Jaegeuk Kim
2018-08-30 17:07             ` Patrick Doyle
2018-08-30 17:56               ` Jaegeuk Kim
2018-08-30 18:06                 ` Patrick Doyle
2018-09-05 15:49             ` Chao Yu [this message]
2018-09-05 16:57               ` 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=7e01fdd5-f39e-793b-97d7-72b93f567579@kernel.org \
    --to=chao@kernel.org \
    --cc=jaegeuk@kernel.org \
    --cc=linux-f2fs-devel@lists.sourceforge.net \
    --cc=wpdster@gmail.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 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).