On Nov 29, 2006, at 4:20 PM, Phil Carns wrote:
Good call. I went ahead and committed both of these changes.
Great- thanks!
FWIW, I'm not crazy about the redundancy that we have for
filesystems in the fs.conf and the collections.db. Would anyone
else be in favor of getting rid of the collections.db
altogether? I looked at the code, and the only time we ever use
that db is when we create or delete a collection, or to verify
that an fsid is valid. pvfs2- showcoll uses it to print all of
the collections, but for all these cases we could just use the
entries in the fs.conf, or look for actual directories in the
storage space. The advantage to removing the collections.db
would be that trove_initialize wouldn't need a method for itself,
independent of the individual collections. Thoughts?
That seems reasonable to me. Can this be done without breaking
storage space compatibility? It seems like it should- newer
servers would probably just ignore the old collections.db if it is
still laying around.
Yes I think so.
-sam
-Phil
_______________________________________________
Pvfs2-developers mailing list
[email protected]
http://www.beowulf-underground.org/mailman/listinfo/pvfs2-developers
