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>,
	linux-f2fs-devel@lists.sourceforge.net
Subject: Re: Out of inodes on my f2fs partition
Date: Thu, 30 Aug 2018 23:20:47 +0800	[thread overview]
Message-ID: <5adf6554-6881-1bd6-3be2-28ae6c72f794@kernel.org> (raw)
In-Reply-To: <CAF_dkJAhK_1WtPF_2s5xUX60k87iMLbAYHV1=0S2aKQv3jh8Ng@mail.gmail.com>

Hi Patrick,

Can you try -i option?

On 2018/8/30 22:44, Patrick Doyle wrote:
> I have run out of space on my 1TB SSD formatted with f2fs, but df
> shows it is only 35% full.
> 
> df -i shows 100% of the inodes are in use.
> 
> What can I do?  I don't see any mkfs.f2fs or mount options for
> increasing the number of inodes.
> 
> --wpd
> 
> ------------------------------------------------------------------------------
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> _______________________________________________
> Linux-f2fs-devel mailing list
> Linux-f2fs-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel
> 

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

  reply	other threads:[~2018-08-30 15:22 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 [this message]
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
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=5adf6554-6881-1bd6-3be2-28ae6c72f794@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).