Permanode, or not?

[Alok Parlikar]

Sorry I'm sending too many questions lately :-)

I'm not quite sure which files I camput should, or should not be permanodes.

Should I import all my data with --filenodes and make everything permanodes?  If so, when would I not create permanodes for something I camput?

Alok

[Simon B.]

To start off with, my (probably flawed) understanding is that when you're used to hierarchical directories, your best bet is to create and use camlistore via a mountpoint. I think you get one added as default, that you can find (and upload/download from/to) via the web interface - that one with the "pig logo" Pudgy http://blog.sergiusens.org/img/camlistore00.png

And if you like me have backups of backups laying around, you might save some disk space, and headaches. I'm also hoping to figure out how to handle revision history for some drawings edited at different computers and saved at varying variations and stages of completeness. And finally fixing up my old mixed arvhives of email (Mailbox, *.pst, ...) and photos from varying cameras and photographers.

Good luck :)

[Mathieu Lonjaret]

Permanodes are the anchors that keep your data alive and visible, so
yes, your files should usually be somehow reachable through a
permanode. Although it's not always direct; e.g. there could be a
permanode only for a directory (static-set), but no permanode for each
of the files in that directory (the static-set entries).

A rule of thumb to keep in mind for later: the garbage collector will
start enumerating from the known roots and mark everything it can
reach from there on. So if one of your files is not reachable through
any schema relation (say as the camliContent of a permanode), it would
not be marked, and would eventually be collected. Which is fair game
since you wouldn't be able to find it back anyway.

> --
> You received this message because you are subscribed to the Google Groups
> "Camlistore" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to camlistore+...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.

[Alok Parlikar]

Ah. Okay. I think I'm so far doing the right thing then. All my old data is reachable from a permanode (top level node for each disk copied in). But I won't be able to search pics or media until I make each of those permanodes, but at the same time I don't really want to make my code archives and .git files all show up unnecessarily.. maybe. :-)

Maybe I can selectively permafy. Or perhaps I can go all permanode (which would happen if I had been using fuse rw) and not care.

Would be good to know what some of you have done so far :-)

(phone)

You received this message because you are subscribed to a topic in the Google Groups "Camlistore" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/camlistore/E_GI0140DG8/unsubscribe.
To unsubscribe from this group and all its topics, send an email to camlistore+...@googlegroups.com.

[Mathieu Lonjaret]

ymmv, but keep in mind that in most cases the disk space cost of a
permanode + claim is pretty neglectable compared to the space usage of
the data itself.
I "permafy" all of my pictures.