On Wed, Apr 19, 2017 at 6:01 PM, Miklos Szeredi <miklos@xxxxxxxxxx> wrote: > On Wed, Apr 19, 2017 at 4:46 PM, Amir Goldstein <amir73il@xxxxxxxxx> wrote: >> Well, if you are lucky you can run into a filesystem that exports >> a file handle of type FILEID_INO32_GEN, then you *know* you're >> good to go. ext* will do that and xfs that was forever mounted with >> -o inode32. >> Even with xfs -o inode64, it will not use the MSB ino bits unless >> you are in the exabytes fs sizes. > > Could filesystems export a max-ino property in their sb? That would > help with doing this properly. > Sounds reasonable, but as max-ino usually derived from filesystem size and filesystems can grow size online, you will need to query both the 'soft' ino limit (without growing fs) and the 'hard' ino limit. Darrick, Are there bits in GETFSMAP to provide this info? -- To unsubscribe from this list: send the line "unsubscribe linux-unionfs" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
