From: David Arendt <admin-/LHdS3kC8BfYtjvyW6yDsg@public.gmane.org>
To: NILFS Users mailing list <users-JrjvKiOkagjYtjvyW6yDsg@public.gmane.org>
Subject: Re: NILFS 2.0.12 released
Date: Mon, 30 Mar 2009 21:29:27 +0200 [thread overview]
Message-ID: <49D11D97.3020702@prnet.org> (raw)
In-Reply-To: <f3642e6b0903301002v2e9fe0afj2b2a4b3d9dd2cecd-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
Hi,
Many thanks from me too.
Until now everything works completely fine.
I will report back if a problem will appear.
After using the new version, I had twice the following crash:
Call Trace:
[<c01247be>] copy_process+0xa3e/0xf90
[<c0124e27>] do_fork+0x77/0x2c0
[<c017b740>] sys_pipe2+0x40/0x70
[<c0101622>] sys_clone+0x32/0x40
[<c0103131>] sysenter_do_call+0x12/0x25
but I will report this to the kernel mailing list as I suspect this has
nothing to do with nilfs, but was triggered by pure hazard after running
the new version.
Bye,
David
Andreas Hartmetz wrote:
> On 3/30/09, Ryusuke Konishi <ryusuke-sG5X7nlA6pw@public.gmane.org> wrote:
>
>> Dear NILFS users,
>>
>> We have released nilfs-2.0.12.
>>
>> This release fixes GC-related problems which are suspected to cause
>> filesystem corruption recently reported in this mailing list.
>>
>> Thanks to David Arendt and Andreas Hartmetz for their feedback and
>> cooperation. I hope this will stabilize cleaner operation.
>>
>> The updated package is available at:
>> http://www.nilfs.org/en/download.html
>>
>> Thanks,
>> Ryusuke Konishi
>>
>
> I'm testing it already :)
> If you don't hear back from me you can assume that the problem is
> solved for me - so far there have been no errors. Thanks!
> _______________________________________________
> users mailing list
> users-JrjvKiOkagjYtjvyW6yDsg@public.gmane.org
> https://www.nilfs.org/mailman/listinfo/users
>
prev parent reply other threads:[~2009-03-30 19:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-30 9:33 NILFS 2.0.12 released Ryusuke Konishi
[not found] ` <20090330.183317.16041871.ryusuke-sG5X7nlA6pw@public.gmane.org>
2009-03-30 17:02 ` Andreas Hartmetz
[not found] ` <f3642e6b0903301002v2e9fe0afj2b2a4b3d9dd2cecd-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2009-03-30 19:29 ` David Arendt [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=49D11D97.3020702@prnet.org \
--to=admin-/lhds3kc8bfytjvyw6ydsg@public.gmane.org \
--cc=users-JrjvKiOkagjYtjvyW6yDsg@public.gmane.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