On 2018/8/30 23:45, Patrick Doyle wrote: > On Thu, Aug 30, 2018 at 11:40 AM Chao Yu <c...@kernel.org> wrote: >> 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; > -i isn't an allowable option to mkfs.f2fs: > Usage: mkfs.f2fs [options] device [sectors] > [options]: > -a heap-based allocation [default:1] > -d debug level [default:0] > -e [extension list] e.g. "mp3,gif,mov" > -l label > -o overprovision ratio [default:5] > -O set feature > -q quiet mode > -s # of segments per section [default:1] > -z # of sections per zone [default:1] > -t 0: nodiscard, 1: discard [default:1]
Can you upgrade your f2fs tools and kernel to make it getting supported? > >> >> And you can use stat -f /your_mount_option to see whether largest number of >> inode support in new image increased. > "stat -f" shows the same information as "df -i". Both show that I > have 9784317 total inodes, and that isn't enough for the builds I am That's correct, they are using the same syscall to get the fs statistic info. > performing on this partition. (The free number has gone up a bit as I > have deleted results from a previous build). > > --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
