aboutsummaryrefslogtreecommitdiff
path: root/tests/example_filesystems/v1.1-aessiv/gocryptfs.longname.dDhdE3C5egl47Q4C4SuPNGPGkzyxuuHCP1efYMCaGqk=.name
diff options
context:
space:
mode:
authorJakob Unterwurzacher2017-04-01 17:19:15 +0200
committerJakob Unterwurzacher2017-04-01 17:19:15 +0200
commit778c955eea1fdc16666f51f6f0a2fab0f580dbf0 (patch)
treef956c11bbc8a055dc9b72a842487bbb6ed4cbbc3 /tests/example_filesystems/v1.1-aessiv/gocryptfs.longname.dDhdE3C5egl47Q4C4SuPNGPGkzyxuuHCP1efYMCaGqk=.name
parente87aebb835b91ba66f288030ee3510df42b860a9 (diff)
fusefrontend_reverse: switch to stable inode numbers
The volatile inode numbers that we used before cause "find" to complain and error out. Virtual inode numbers are derived from their parent file inode number by adding 10^19, which is hopefully large enough no never cause problems in practice. If the backing directory contains inode numbers higher than that, stat() on these files will return EOVERFLOW. Example directory lising after this change: $ ls -i 926473 gocryptfs.conf 1000000000000926466 gocryptfs.diriv 944878 gocryptfs.longname.hmZojMqC6ns47eyVxLlH2ailKjN9bxfosi3C-FR8mjA 1000000000000944878 gocryptfs.longname.hmZojMqC6ns47eyVxLlH2ailKjN9bxfosi3C-FR8mjA.name 934408 Tdfbf02CKsTaGVYnAsSypA
Diffstat (limited to 'tests/example_filesystems/v1.1-aessiv/gocryptfs.longname.dDhdE3C5egl47Q4C4SuPNGPGkzyxuuHCP1efYMCaGqk=.name')
0 files changed, 0 insertions, 0 deletions