linux-f2fs-devel.lists.sourceforge.net archive mirror
 help / color / mirror / Atom feed
From: Chao Yu <chao@kernel.org>
To: Patrick Doyle <wpdster@gmail.com>
Cc: linux-f2fs-devel@lists.sourceforge.net
Subject: Re: Out of inodes on my f2fs partition
Date: Thu, 30 Aug 2018 23:39:55 +0800	[thread overview]
Message-ID: <e18462d8-10bb-3939-e3b3-cbd764654c31@kernel.org> (raw)
In-Reply-To: <CAF_dkJC5GvRzweVkCKWeHMuRWp=6tNdDDR14VLrGY7NcZs7ObQ@mail.gmail.com>

Hi Patrick,

On 2018/8/30 23:30, Patrick Doyle wrote:
> On Thu, Aug 30, 2018 at 11:22 AM Chao Yu <chao@kernel.org> wrote:
>>
>> Hi Patrick,
>>
>> Can you try -i option?

Sorry, I mean mkfs.f2fs -i /dev/xxx;

And you can use stat -f /your_mount_option to see whether largest number of
inode support in new image increased.

Inodes: Total: 719360     Free: 719357
        ^^^^^^^^^^^^^

Thanks,

>>
> Hello Chao,
> Thank you for your reply.  For which command should I try the -i
> option?  I presume you mean df:
> 
> $ df -i /home/wpd/src/
> Filesystem      Inodes   IUsed  IFree IUse% Mounted on
> /dev/nvme0n1   9784317 9410039 374278   97% /home/wpd/src
> 
> And, for reference:
> $ df /home/wpd/src
> Filesystem      1K-blocks      Used Available Use% Mounted on
> /dev/nvme0n1   1000202584 324990344 671159248  33% /home/wpd/src
> 
> My f2fs partition is only 33% full, but I can no longer build on it,
> as I keep getting "device out of space" errors.
> 
> I don't see any mechanism to tune (dynamically) or fix (at mkfs.f2fs
> time) the number of inodes.  I am desperately looking for a clue now
> :-)
> 
> --wpd
> 

------------------------------------------------------------------------------
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-08-30 15:40 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 [this message]
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
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=e18462d8-10bb-3939-e3b3-cbd764654c31@kernel.org \
    --to=chao@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).