On Thu, Jan 17, 2013 at 5:52 AM, Gregory Farnum g...@inktank.com wrote:
My biggest concern with this was how it worked on cluster with
multiple data pools, and Sage's initial response was to either
1) create an object for each inode that lives in the metadata pool,
and holds the backtraces
On Wed, Jan 16, 2013 at 3:54 PM, Sam Lang sam.l...@inktank.com wrote:
On Wed, Jan 16, 2013 at 3:52 PM, Gregory Farnum g...@inktank.com wrote:
My biggest concern with this was how it worked on cluster with
multiple data pools, and Sage's initial response was to either
1) create an object for
One of the first things we need to fix in the MDS is how we support
lookup-by-ino. It's important for fsck, NFS reexport, and (insofar as
there are limitations to the current anchor table design) hard links and
snapshots.
Below is a description of the problem and a rough sketch of my proposed
