Re: [Netatalk-devel] CNID database - better stability/recoverability

[Joerg L. <le...@wu...>]

anmar oueja:

> thanks for the thoruogh explanation. You answered alot of questions I 
> had for a while.

> Here is a suggestion that I think worth looking at:

> what is we forget about CNIDs and Appledouble and use the XFS files 
> system from (SGI). The file system supports metadata (resource fork) . 
> Each file can have multiple resource forks each is 64 FB although it is 
> not hard to extend them to 256 KB. that might not be big, but I yet to 
> see some Mac files that have more than a few kilobytes worth of a 
> resouce fork.

> By using a mechanism, sorry I am not a developer, we can get Netatalk to 
> talk to XFS and store the information properly. This will limit Netatalk 
> to XFS (using thie scheme) but other FS users can use the CNID_DB scheme .

> what do you think ??

> Anmar

Anmar,

storing the information together with the file (as metadata) would
certainly be a desirable solution. It would make metadata updates much
easier for starters. However, there are drawbacks unfortunately. One
is portability: Not everyone uses/can use XFS. It would be interesting
to generalize the ad_double API though to allow any sort of backing
store, database, extended attributes, whatever. The second would be
XFS itself at the moment, according to the limits you state. A
ressource fork can easily exceed several hundreds KB.

best regards,



-- 

Joerg Lenneis

email: le...@wu...