Work at SourceForge, help us to make it a better place! We have an immediate need for a Support Technician in our San Francisco or Denver office.

Close

#488 CNID database move to devID+inode

open
nobody
None
5
2013-01-20
2013-01-20
bmn13
No

I had a look in the Berkeley DB and see that you are storing full paths to every file.

This means that if a file is renamed on the local Linux server, rather than via the AFP server, we will lose the CNID mapping and therefore also lose any shortcuts that pointed to that ID on the Mac side.

Why not change the BDB database to this format?
devID, inode, CNID
0, 1232, 324

That means that the file can be moved absolutely anywhere (within the same device) and still be found in the database, no matter what it is named.

Discussion

  • bmn13
    bmn13
    2013-01-20

    If you are actually already doing dev+inode mappings, then please update your Netatalk documentation, because it doesn't describe this anywhere.

     
  • Ralph Böhme
    Ralph Böhme
    2013-01-20

    Consider queriying the Netatalk developer list, possibly someone cares to answer. Alternatively look for someone who provides consulting services.