Linux NILFS development
 help / color / mirror / Atom feed
From: Jan de Kruyf <jan.de.kruyf-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: Ryusuke Konishi <ryusuke-sG5X7nlA6pw@public.gmane.org>
Cc: users-JrjvKiOkagjYtjvyW6yDsg@public.gmane.org
Subject: Re: cleanerd
Date: Sat, 17 Oct 2009 22:47:12 +0200	[thread overview]
Message-ID: <ee5afd760910171347x4ad27199ka59d0e76f3271050@mail.gmail.com> (raw)
In-Reply-To: <20091011.154916.07997858.ryusuke-sG5X7nlA6pw@public.gmane.org>


[-- Attachment #1.1: Type: text/plain, Size: 947 bytes --]

On Sun, Oct 11, 2009 at 8:49 AM, Ryusuke Konishi <ryusuke-sG5X7nlA6pw@public.gmane.org> wrote:

>
> According to the log, the error was repeatedly detected in a retry
> loop in the nilfs_clean_segments kernel function which cleanerd calls
> via ioctl.  The err=-28 means ENOSPC (no space left on the device).
>
> Yeah, if cleanerd falls into this state, it cannot handle any signals.
> And, it doesn't return to userspace until the error is removed.
>
> As you are pointing out, I wonder why this error is generated on the
> device having enough free space.
>
> I'll attach a patch to identify which function returns ENOSPC.  Could
> you try the patch ?
>

Hallo,
I have done the patch. The output, with debug switched on, is in the
attached file.

I have done some more analizing. Everything that looks helpful is included
in the file as wel.

I hope it is useful

Regards

Jan de Kruyf.

This day the Lord creates,
so let us celebrate with joy!

[-- Attachment #1.2: Type: text/html, Size: 1336 bytes --]

[-- Attachment #2: nilfsdebugVar.txt.gz --]
[-- Type: application/x-gzip, Size: 44410 bytes --]

[-- Attachment #3: Type: text/plain, Size: 158 bytes --]

_______________________________________________
users mailing list
users-JrjvKiOkagjYtjvyW6yDsg@public.gmane.org
https://www.nilfs.org/mailman/listinfo/users

  parent reply	other threads:[~2009-10-17 20:47 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-10 22:18 cleanerd Jan de Kruyf
     [not found] ` <ee5afd760910101518u4a85fd0fn6e5539a327b2a876-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2009-10-11  3:29   ` cleanerd Ryusuke Konishi
     [not found]     ` <20091011.122911.131278678.ryusuke-sG5X7nlA6pw@public.gmane.org>
2009-10-11  5:32       ` cleanerd Jan de Kruyf
     [not found]         ` <ee5afd760910102232o5f17c50cxb5024f6f76ecbcf5-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2009-10-11  6:49           ` cleanerd Ryusuke Konishi
     [not found]             ` <20091011.154916.07997858.ryusuke-sG5X7nlA6pw@public.gmane.org>
2009-10-13 19:57               ` cleanerd Jan de Kruyf
2009-10-17 20:47               ` Jan de Kruyf [this message]
     [not found]                 ` <ee5afd760910171347x4ad27199ka59d0e76f3271050-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2009-10-19  2:07                   ` cleanerd Ryusuke Konishi
  -- strict thread matches above, loose matches on Subject: below --
2008-11-05 21:45 cleanerd John Huttley
     [not found] ` <491213E2.4010905-jE24nFfhqzU3hwNNidygWXTaI6DYlTYJ@public.gmane.org>
2008-11-06  2:50   ` cleanerd Ryusuke Konishi

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=ee5afd760910171347x4ad27199ka59d0e76f3271050@mail.gmail.com \
    --to=jan.de.kruyf-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
    --cc=ryusuke-sG5X7nlA6pw@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