From: Pete Zaitcev <zaitcev@redhat.com>
To: Jeff Garzik <jeff@garzik.org>
Cc: Project Hail <hail-devel@vger.kernel.org>
Subject: Re: tabled version 0.5.1 released
Date: Wed, 11 Aug 2010 10:34:51 -0600 [thread overview]
Message-ID: <20100811103451.2258863e@lembas.zaitcev.lan> (raw)
In-Reply-To: <4C624913.6050602@garzik.org>
On Wed, 11 Aug 2010 02:54:11 -0400
Jeff Garzik <jeff@garzik.org> wrote:
> Note that underlying chunkd disk format changed, so volumes must be
> upgraded (manually).
I killed them one by one and let tabled replication to rebuild them.
It kinda takes longer than I expected... And we do not have any good
stats regarding the current redundancy levels, so I watched what the
stat dumps says about the last keys processed, and just waited for
the activity to cease.
-- Pete
prev parent reply other threads:[~2010-08-11 16:34 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-11 6:54 tabled version 0.5.1 released Jeff Garzik
2010-08-11 16:34 ` Pete Zaitcev [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=20100811103451.2258863e@lembas.zaitcev.lan \
--to=zaitcev@redhat.com \
--cc=hail-devel@vger.kernel.org \
--cc=jeff@garzik.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).