Re:Google Drive does a surprise rollout of file limits, lock...
by yjftsjthsd-h on Saturday April 01, 2023 @02:11PM
(#35402533)
Sure, everything has some limit. But the lowest limit I see on that page is 2^32, which is just a touch higher than 5 million. (/s) And far more importantly, none of those filesystems just decided one day to reduce the limit, which is kind of a big deal. (Although funny, in a horrible way; imagine booting up your machine one day and it tells you that your home filesystem needs to drop a few million files before it can mount. Can you imagine?)
[ Parent
| on HN ]
Re:Google Drive does a surprise rollout of file limits, lock...
by viraptor on Saturday April 01, 2023 @06:33PM
(#35404828)
> none of those filesystems just decided one day to reduce the limit
Yes and no. This works differently from one filesystem to another, but search for "running out of inodes" to find many ways this can happen in reality, way below the technical limit of the filesystem itself. You can end up in situations where you can't create a new file and need to remove more than one to solve the situation. (Or even where removing many files doesn't seem to make a difference)
Re:Google Drive does a surprise rollout of file limits, lock...
by Dylan16807 on Saturday April 01, 2023 @06:52PM
(#35404987)
The thing about running out of inodes is that the format command scales them with the size of the drive, and the default is 1 inode per 16KB. So for a standard google account at 2TB or maybe 5TB you'd have 125 million or 312 million inodes.
They've basically gone and set it up like "largefile" mode, 1 inode per 1MB, forced upon all users. That's a bad default and an even worse mandate.