From: Jeff Garzik <jeff@garzik.org>
To: hail-devel@vger.kernel.org
Subject: Re: [PATCH] chunkd: update backend to support binary keys
Date: Wed, 04 Nov 2009 01:26:50 -0500 [thread overview]
Message-ID: <4AF11EAA.6090302@garzik.org> (raw)
In-Reply-To: <20091104055137.GA17995@havoc.gtf.org>
On 11/04/2009 12:51 AM, Jeff Garzik wrote:
>
> (yeah, the summary line needs s/cld:/chunkd:/)
>
>
> Just committed the following change to chunkd's storage backend API,
> preparing chunkd for variable-length opaque binary keys.
>
>
>
> commit 0a8c3225355de86484eba71279c646f7790d5bb1
> Author: Jeff Garzik<jeff@garzik.org>
> Date: Wed Nov 4 00:44:55 2009 -0500
>
> cld: update storage backend to store based on opaque binary key + key length
>
> Change internal structure to utilize an opaque binary key, rather than the
> existing probably-nul-terminated, fixed length C hexidecimal string key.
>
> Storage backend now names files based on the SHA256 of the key.
>
> The key, in its entirety, is written to each object's header in the
> filesystem, to assist in recovery.
To emphasize, this is a chunkd on-disk database format change.
Jeff
prev parent reply other threads:[~2009-11-04 6:26 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-04 5:51 [PATCH] chunkd: update backend to support binary keys Jeff Garzik
2009-11-04 6:26 ` Jeff Garzik [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4AF11EAA.6090302@garzik.org \
--to=jeff@garzik.org \
--cc=hail-devel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.