On Wed, Feb 07, 2018 at 12:54:43PM +0200, Avi Kivity wrote: > On 02/07/2018 03:57 AM, Dave Chinner wrote: > >IOWs, inode32 limits where and how many inodes you can > >create, not how much user data you can write inode the filesystem. > > Thanks a lot for the clarifications. Looks like inode32 can be used > to reduce some of our pain. > > There's a danger that when switching from inode64 to inode32 you end > up with the inode32 address space already exhausted, right? Does > that result in ENOSPC or what? ENOSPC on inode allocation. > Anyway, can probably be fixed by stopping the load, copying files > around, and moving them back. Yup, assuming you're able to find the files that need to be moved in a finite period of time. Cheers, Dave. -- Dave Chinner david@xxxxxxxxxxxxx -- To unsubscribe from this list: send the line "unsubscribe linux-xfs" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
