Hi Patrick,
On 2018/8/30 23:30, Patrick Doyle wrote:
> On Thu, Aug 30, 2018 at 11:22 AM Chao Yu <c...@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
_______________________________________________
Linux-f2fs-devel mailing list
Linux-f2fs-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel
