From: Ryusuke Konishi <konishi.ryusuke-Zyj7fXuS5i5L9jVzuh4AOg@public.gmane.org>
To: llucax-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org
Cc: albertito-vOTlzuNH1/1M3YmQoIpPTg@public.gmane.org,
linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
users-JrjvKiOkagjYtjvyW6yDsg@public.gmane.org,
konishi.ryusuke-Zyj7fXuS5i5L9jVzuh4AOg@public.gmane.org
Subject: Re: NILFS2 get stuck after bio_alloc() fail
Date: Tue, 23 Jun 2009 13:40:26 +0900 (JST) [thread overview]
Message-ID: <20090623.134026.08265083.ryusuke@osrg.net> (raw)
In-Reply-To: <20090614181313.GA16597-ukiYB341y+1jWMeXa1+QZ5bDTtF7IOEM@public.gmane.org>
Hi Leandro,
On Sun, 14 Jun 2009 15:13:13 -0300, Leandro Lucarella <llucax-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote:
> Ryusuke Konishi, el 15 de junio a las 03:02 me escribiste:
> [snip]
> > > Here is the complete trace:
> > > http://pastebin.lugmen.org.ar/4931
> >
> > Thank you for your help.
> >
> > According to your log, there seems to be a leakage in clear processing
> > of the writeback flag on pages. I will review the error path of log
> > writer to narrow down the cause.
>
> Oh! I forgot to tell you that the cleanerd process was not running. When
> I mounted the NILFS2 filesystem the cleanerd daemon said:
>
> nilfs_cleanerd[29534]: start
> nilfs_cleanerd[29534]: cannot create cleanerd on /dev/loop0
> nilfs_cleanerd[29534]: shutdown
>
> I thought I might have an old utilities version and that could be because
> of that (since the nilfs website was down I couldn't check), but now
> I checked in the backup nilfs website that latest version is 2.0.12 and
> I have that (Debian package), so I don't know why the cleanerd failed to
> start in the first place.
At the last weekend, several users gave me feedback on the same early
failure of cleanerd process.
This problem turned out to be caused by an elementaly bug in the
userland library of nilfs; there was a lack of canonicalization of
pathname in the library, and it caused the failure, for example, when
user adds an extra slash symbol to the mount directory name.
We have released nilfs2-utils-2.0.13 yesterday to resolve this mess.
If you didn't know it, please try the updated package.
Thanks,
Ryusuke Konishi
next prev parent reply other threads:[~2009-06-23 4:40 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20090614013211.GA22552@homero.springfield.home>
2009-06-14 1:52 ` NILFS2 get stuck after bio_alloc() fail Alberto Bertogli
2009-06-14 6:30 ` Ryusuke Konishi
2009-06-14 7:00 ` Pekka Enberg
2009-06-14 12:34 ` Ryusuke Konishi
2009-06-14 3:45 ` Ryusuke Konishi
2009-06-14 15:32 ` Leandro Lucarella
2009-06-14 18:02 ` Ryusuke Konishi
2009-06-14 18:13 ` Leandro Lucarella
2009-06-18 17:34 ` [PATCH] nilfs2: fix hang problem after bio_alloc() failed Ryusuke Konishi
2009-06-21 11:08 ` Andi Kleen
2009-06-21 12:34 ` [NILFS users] " Ryusuke Konishi
[not found] ` <20090614181313.GA16597-ukiYB341y+1jWMeXa1+QZ5bDTtF7IOEM@public.gmane.org>
2009-06-23 4:40 ` Ryusuke Konishi [this message]
[not found] ` <20090623.134026.08265083.ryusuke-sG5X7nlA6pw@public.gmane.org>
2009-06-23 12:55 ` NILFS2 get stuck after bio_alloc() fail Leandro Lucarella
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=20090623.134026.08265083.ryusuke@osrg.net \
--to=konishi.ryusuke-zyj7fxus5i5l9jvzuh4aog@public.gmane.org \
--cc=albertito-vOTlzuNH1/1M3YmQoIpPTg@public.gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=llucax-Re5JQEeQqe8AvxtiuMwx3w@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