debian developer | 31 Jul 10:06
Picon

Re: start the logging for atomic commit

Hi Ogawa,

Thanks for working on this project. We are eagerly awaiting for this release.

You have any updates on atomic commit? What part are you working on?
Where has Daniel disappeared?

Thanks,
On Mon, Jun 29, 2009 at 7:26 AM, OGAWA
Hirofumi<hirofumi <at> mail.parknet.co.jp> wrote:
> Hi,
>
> Those patches are start to logging for atomic commit, and fix the
> stage_delta()/flush_log() to flush correctly. Also, this fixes the
> deferred bfree stuff.  And some bug fixes.
>
> The problem of this patchset is, first of all, I worked only for
> creation path as start.
>
> I copied code from kernel to utility.*, so we would need to think about
> license of those, or remove the code from this patch.
>
> And test is not enough, some programs/code-path would be untested at all.
>
> Main known problems are: It will still use writeback stuff, so, we need
> more code to switch to commit stuff. But, before switch, we will need to
> add to flush bitmap inode.
>
> And This is first one to start logging, so, there may be bugs on around
> those.  Kernel is compile test only.
(Continue reading)

debian developer | 31 Jul 11:10
Picon

Re: Current Activities?

Hi Daniel,

On Fri, May 1, 2009 at 9:19 AM, Daniel Phillips<phillips <at> phunq.net> wrote:
> On Wednesday 29 April 2009, t3right.thebashar <at> xoxy.net wrote:
>> Hi Daniel,
>>
>> I want to apologize upfront if I sound like one of those "when will it
>> be done" questions that are best left unasked with most open source
>> projects.  Actually, I'm just really curious about what's been going
>> on lately.  I am somewhat embarrassed to admit that I became
>> fascinated with tux3's development since the first time it was
>> featured in an article on kerneltrap.  I've greatly enjoyed reading
>> your design notes and dialog with the btrfs team.  I had no naive
>> hopes that tux3 would get integrated into the linux kernel
>> immediately, but I've been extremely surprised at the loss of public
>> progress notes from you after the initial review request back and
>> forth died off.  In fact it seems like there's only been 7 postings
>> from you in the month since the last kernel merge related thread.
>>
>> I've really missed the public view into tux3's progress.  If it's not
>> too presumptuous, how are you? How's tux3 coming along?  What part of
>> the kernel port is taking the bulk of the work?  What new and
>> interesting challenges have you been wrestling with?
>
> Actually, I have been busy with real life for the last couple
> of months.  An interesting challenge is how I can keep up the
> previous development without any corporate support.  Zero.  Zip.
> Nada.  There has been exactly zero support from the usual
> suspects, who all have their own good reasons no doubt, which
> do not necessarily have much to do with the good of the Linux
(Continue reading)

OGAWA Hirofumi | 31 Jul 13:15
Picon
Gravatar

Re: start the logging for atomic commit

debian developer <debiandev <at> gmail.com> writes:

> Hi Ogawa,
>
> Thanks for working on this project. We are eagerly awaiting for this release.
>
> You have any updates on atomic commit? What part are you working on?

I had no time this month at all, and I couldn't discuss or work for
this. So there is no update from me, although if I make the time, I'm
going to play with atomic commit.

You want to work for some part?

> Where has Daniel disappeared?

We were almost all discussing about tux3 on irc.oftc.net#tux3, not
mailing-list. I'm still a bit busy state, so I'm not sure current state
for now.

Thanks.
--

-- 
OGAWA Hirofumi <hirofumi <at> mail.parknet.co.jp>

Gmane