Sure, except that there are those pesky legacy constraints.
The latest NFS protocol specifies that the token passed over the wire is a 64 bit value (earlier versions specified a 32 bit value)
Other network filesystems have similar specifications.
In fact, from a little googling, it looks like the POSIX spec says that these cookies are of type 'long'. this makes changing it to something like a variable length string like you would need to use the filename extremely hard.
Posted Mar 28, 2013 10:32 UTC (Thu) by paulj (subscriber, #341)
[Link]
Sure. There's 2 trains of thought going through my head:
a) How to get a stable order over fixed-length IDs (dir size limited to the ID space then).
b) Assuming you can't get that, how would you design sane APIs that still allowed iteration of directories?
For b, it's names. However, I still don't understand why 'a' isn't possible. See my comment on the companion ext4 article about using a ring for the ID space.
A kernel change breaks GlusterFS
Posted Mar 28, 2013 16:29 UTC (Thu) by Cyberax (✭ supporter ✭, #52523)
[Link]
Use "last returned filename" as a cookie. Easy and simple - Amazon does this for S3 and it works splendidly.
