4 ms·
Some loose remarks: - named streams are out => it becomes unlikely that we will see these become popular on any OS (because being incompatible with the market
by Someone 15y ago
Some loose remarks:
- named streams are out => it becomes unlikely that we will see these become popular on any OS (because being incompatible with the market leader is problematic; see Mac OS X, .DS_Store). I find that a pity.
- I guess quotas are out because there will be something else replacing it?
- Can anyone explain why a modern filesystem should have a limitation on path length? For APIs I can understand it because the standard C library thinks paths are fixed-length, but for file systems? I would think this complicates the implementation, as every directory would need to know the length of the deepest path below it (in case one attempts to rename it). Aggregating that info upwards whenever a file is created or renamed (let alone deleted) cannot come for free, can it?
- keeperofdakeys 15y ago> Can anyone explain why a modern filesystem should have a limitation on path length? Performance and verbosity of code. Having a limit allows the creation of fixed-sized structures, which makes the code much simpler (remember, code has bugs, so more code is more bugs). It also makes the generated machine code much simpler, leading to better performance.
- jensnockert 15y agoI guess it is the classic "You can create files with any name but don't ever try to access it" that happens in Windows with extremely long names.
- wvenable 15y agoNamed streams were always problematic especially in a connected heterogeneous computing environment. I'm not sad to see them go.
- Someone 15y agoBut that is chicken and egg. I would rather see a world where we worked on solving those problems, instead of giving up on them. On the good side, they are dropping support for 8.3 filenames (but it will be interesting to see how they solve the 'copy from this new file system to FAT' problem)
- adgar 15y ago> Aggregating that info upwards whenever a file is created or renamed (let alone deleted) cannot come for free, can it? Not free, but it's not asymptotically significant.
- tlb 15y agoEven when you reparent a directory? Reparenting a directory to a longer prefix would have to sometimes fail.
- wcoenen 15y ago> I guess quotas are out because there will be something else replacing it? If it works like ZFS, then you will be able to create as many filesystem volumes as you want on top of a storage pool, each with their own size limit. You could create separate file systems for each user. > Can anyone explain why a modern filesystem should have a limitation on path length? The 32K limit doesn't really matter, because we're effectively stuck forever with the much lower and older limit of 260 characters. Longer paths would crash existing applications who use 260 byte buffers to store file system paths. http://serverfault.com/questions/163419/window-256-characters-path-name-limitation http://serverfault.com/questions/163419/window-256-character...