public inbox for hail-devel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jeff Garzik <jeff@garzik.org>
To: Project Hail <hail-devel@vger.kernel.org>
Subject: chunkd on-disk format update
Date: Sun, 04 Jul 2010 02:08:29 -0400	[thread overview]
Message-ID: <4C30255D.3040901@garzik.org> (raw)


A disruptive chunkd on-disk file format change was just pushed to 
hail.git.  It is a minor format update, but it is incompatible.  chunkd 
v0.8+ objects are now binary-incompatible with the just-released chunkd 
v0.7.

The update adds a magic number and object size to the on-disk object 
header (struct be_fs_obj_hdr), plus some reserved space for future 
additions.

The magic number and object size add easy (and CPU-inexpensive) sanity 
checks to the object I/O code.  The object size field is largely 
redundant, intended mainly for disaster recovery.  However, storing the 
object size enables the file format to support multiple objects inside a 
single POSIX filesystem file.

Hopefully this means implementing an APPEND operation in chunkd is now 
feasible.  But if APPEND falls through, these two new be_fs_obj_hdr 
members retain some utility anyway.

	Jeff




                 reply	other threads:[~2010-07-04  6:08 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=4C30255D.3040901@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox