On Thu, Aug 30, 2018 at 1:56 PM Jaegeuk Kim <jaeg...@kernel.org> wrote: > Hi, > I expect "-i" should give more # of inodes, since without it, F2FS relied on > relatively small (but enough on smaller capacity) checkpoint blocks to provide > them. With the option, it expands checkpoint space to allow more nids which > will > be used for inodes and file's index blocks. Let us know, if you are in trouble > with that option. > > The mount options would be set by default. If your files are mostly larger > than > 3.5KB, it'd be better to turn inline_data off. If your directories contain > huge > number of childrens, it'd be better to turn inline_dentry off and tune > sys/fs/dir_level. OK. Thanks for the information. And thank you especially for the help. I was dead in the water, and google searches were turning up nothing useful. (Plenty of stuff regarding resizing extN file systems, and lots of stuff regarding the design of f2fs, but not much on what to do when it breaks.)
I poked around a bit before I deployed this 1TB drive. It seemed to me that f2fs is the right approach for file systems on SSDs. And, while it is still fairly new, it's not _that_ new. That's why I was so baffled when I ran into this problem. I had no idea if it was an issue with the new drive, f2fs, or something else going on with my computer. Thanks again. --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
