All of lore.kernel.org
 help / color / mirror / Atom feed
From: Vyacheslav Dubeyko <slava-yeENwD64cLxBDgjK7y7TUQ@public.gmane.org>
To: Piotr Szymaniak <szarpaj-TbOm9Ca2r9GrDJvtcaxF/A@public.gmane.org>
Cc: linux-nilfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: Strange "flush" process bahaviour
Date: Mon, 01 Apr 2013 10:06:11 +0400	[thread overview]
Message-ID: <1364796371.2202.16.camel@slavad-ubuntu> (raw)
In-Reply-To: <20130331132609.GA1781@wloczykij>

On Sun, 2013-03-31 at 15:26 +0200, Piotr Szymaniak wrote:

[snip]
> 
> Hrm, maybe this is btrfs realated then? But I suppose I don't have any
> btrfs on the second machine with flush issues.
> 

If you detected issue with flush-8:0 kernel thread then it is a NILFS2
related issue, as I understand. Because flush-8:0 processes /dev/sda
drive and you have NILFS2 partition on /dev/sda3 (/dev/sda3 on / type
nilfs2 (rw,noatime,nodiratime,gcpid=16150)).

> I had a system freeze yesterday and right after reboot flush is back.
> So it looks like I can reproduce it (something makes the flush thing
> while booting. Maybe I can catch some debug info there?). Right now I'm
> going back to 3.4.x series kernel.
> 

The visible symptoms of the issue (flush kernel thread "abnormal"
activity) is not a reason of the issue. Such "abnormal" activity of
flush kernel thread takes place because in nilfs_mdt_write_page() and
nilfs_write_page() can be called with wbc->for_kupdate or
wbc->for_background flags. It is made simply
redirty_page_for_writepage() for such case.

The real issue hides in other NILFS2 subsystem. And only clear
understanding of file system operation that initiates such "abnormal"
activity of flush kernel thread can be a basis for further debugging and
investigation of the issue.

With the best regards,
Vyacheslav Dubeyko.

> 
> Piotr Szymaniak.


--
To unsubscribe from this list: send the line "unsubscribe linux-nilfs" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

  reply	other threads:[~2013-04-01  6:06 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-11-12 20:19 Strange "flush" process bahaviour fwdnilfsml.to.11df-2pMamKoQTv4
     [not found] ` <50A159BC.9060600-3TRaYzfGuuI@public.gmane.org>
2012-11-13  6:13   ` Vyacheslav Dubeyko
2012-11-13 13:04     ` Strange "flush" process bahaviour (fwdnilfsml: message 2 of 20) Александр
     [not found]       ` <50A24564.7000704-3TRaYzfGuuI@public.gmane.org>
2012-11-13 13:41         ` Strange "flush" process bahaviour Vyacheslav Dubeyko
2012-11-13 14:01           ` fwdnilfsml.to.11df-2pMamKoQTv4
2012-11-15 22:58           ` fwdnilfsml.to.11df-2pMamKoQTv4
     [not found]             ` <50A5737C.2040805-3TRaYzfGuuI@public.gmane.org>
2012-11-16  3:13               ` Ryusuke Konishi
     [not found]                 ` <201211160313.AA04185-ZdTO5nnmHvkOizVVqyxoihMFgDP4sedm@public.gmane.org>
2012-11-16 15:02                   ` fwdnilfsml.to.11df-2pMamKoQTv4
     [not found]                     ` <50A65588.3000205-3TRaYzfGuuI@public.gmane.org>
2012-11-17  1:27                       ` Ryusuke Konishi
     [not found]                         ` <CAKFNMomO6ebYkXk=A9H2Wieswvogt6dj16Otj0u74M4aHOOPBg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2012-11-27 15:19                           ` Piotr Szymaniak
2012-11-27 17:43                             ` Vyacheslav Dubeyko
     [not found]                               ` <295B3FE7-A44E-4D57-9A6A-B725EF1BA9EB-yeENwD64cLxBDgjK7y7TUQ@public.gmane.org>
2012-11-28 14:21                                 ` Piotr Szymaniak
2012-11-28 14:39                                   ` Vyacheslav Dubeyko
2012-11-28 20:59                                     ` Piotr Szymaniak
2012-11-29  7:00                                       ` Vyacheslav Dubeyko
2013-03-28 12:07                                         ` Piotr Szymaniak
2013-03-28 19:22                                           ` Vyacheslav Dubeyko
     [not found]                                             ` <E24177B1-2EF0-4274-BD13-4642E3663D08-yeENwD64cLxBDgjK7y7TUQ@public.gmane.org>
2013-03-29  7:42                                               ` Piotr Szymaniak
2013-03-29  8:15                                                 ` Vyacheslav Dubeyko
2013-03-29 10:37                                                   ` Piotr Szymaniak
2013-03-29 11:29                                                     ` Vyacheslav Dubeyko
2013-03-29 13:57                                                       ` Piotr Szymaniak
2013-03-31 11:14                                                         ` Vyacheslav Dubeyko
     [not found]                                                           ` <1D751B59-8E60-4D32-80CA-734BD25EE12C-yeENwD64cLxBDgjK7y7TUQ@public.gmane.org>
2013-03-31 13:26                                                             ` Piotr Szymaniak
2013-04-01  6:06                                                               ` Vyacheslav Dubeyko [this message]
2013-01-08 13:22                                       ` Vyacheslav Dubeyko
2012-11-13 15:28   ` Piotr Szymaniak
2012-11-13 18:24     ` Vyacheslav Dubeyko
     [not found]       ` <6B9E40B0-90F8-4130-9798-87253FEDDA78-yeENwD64cLxBDgjK7y7TUQ@public.gmane.org>
2012-11-13 17:49         ` fwdnilfsml.to.11df-2pMamKoQTv4

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=1364796371.2202.16.camel@slavad-ubuntu \
    --to=slava-yeenwd64clxbdgjk7y7tuq@public.gmane.org \
    --cc=linux-nilfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=szarpaj-TbOm9Ca2r9GrDJvtcaxF/A@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.