From: Patrick Doyle <wpdster@gmail.com>
To: jaegeuk@kernel.org
Cc: linux-f2fs-devel@lists.sourceforge.net
Subject: Re: Out of inodes on my f2fs partition
Date: Thu, 30 Aug 2018 13:07:18 -0400 [thread overview]
Message-ID: <CAF_dkJC5Z=hLdnkMMGHXw=5a49-HdrYoPwmaaEjcbjz3_Li+xA@mail.gmail.com> (raw)
In-Reply-To: <20180830165845.GB3742@jaegeuk-macbookpro.roam.corp.google.com>
On Thu, Aug 30, 2018 at 12:58 PM Jaegeuk Kim <jaegeuk@kernel.org> wrote:
> Patrick,
>
> Please download the latest f2fs-tools from
> https://git.kernel.org/pub/scm/linux/kernel/git/jaegeuk/f2fs-tools.git/log/
>
> Chao,
Jaegeuk,
Thank you very much. I just cloned that repository and I see that it
includes a "-i" option for "extended node bitmap".
(I have also completed my backup of my f2fs partition and stand ready
to reformat that partition.)
Can you give me a sense of what the "extended node bitmap" will do for
me? Will that address the lack of inodes?
Also, (although I will answer this by experimentation very shortly),
should I expect this to be compatible with my 4.15 kernel?
Finally, I see that there are mount options for various inline_*
possibilities, should I be turning those options on to address this
issue?
--wpd
------------------------------------------------------------------------------
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-08-30 17:07 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 [this message]
2018-08-30 17:56 ` Jaegeuk Kim
2018-08-30 18:06 ` Patrick Doyle
2018-09-05 15:49 ` Chao Yu
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='CAF_dkJC5Z=hLdnkMMGHXw=5a49-HdrYoPwmaaEjcbjz3_Li+xA@mail.gmail.com' \
--to=wpdster@gmail.com \
--cc=jaegeuk@kernel.org \
--cc=linux-f2fs-devel@lists.sourceforge.net \
/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).