Lew Wolfgang wrote:
True, but that wouldn't help for the high inodes already created. I think the problem would still exist.
Only safe way I could think of might be something like copying the entire disk off to another disk or directory that only has 32 bit inodes, then copy it back to the original. Not the easiest -- depends on needs...but...fyi
We use multiple partitions bigger than 20-TB containing thousands of 4-GB files. This is why we selected xfs some years ago and haven't had any "known" issues until now. We'll just be careful with home partitions, which don't really need to be xfs in the first place. Acroread wouldn't know what to do with a 4-GB binary file anyway!
---- Maybe acroread 9.x doesn't... but I know photoshop and Adobe utils deal with
4GB files... have had image files that were that large -- that are also that large when you save them in PDF format (which you can usually do in many Adobe utils)...
Thanks again. I brought it up here in case other folks might run into the issue. Of course, I wonder what issues reiserfs and/or ext4 have? :-)
Might depend on how they count files... Windows has all the inode type info in 1-4 (usually 1-2) MftZone Regions... So there, I'd think you'd need to run close to 1-2billion files before needing > 32bits... but Windows ntfs isn't known for being able to handle multiple simultaneous reads and writes in different places like XFS was designed for -- that's why they allow them to be spread out -- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org