Linux NILFS development
 help / color / mirror / Atom feed
From: Vyacheslav Dubeyko <slava-yeENwD64cLxBDgjK7y7TUQ@public.gmane.org>
To: Piotr Szymaniak <szarpaj-TbOm9Ca2r9GrDJvtcaxF/A@public.gmane.org>
Cc: "Elmer Zhang"
	<freeboy6716-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>,
	"Сергей Александров"
	<splavgm-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>,
	linux-nilfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: A lot of NILFS: bad btree node messages (readonly fs)
Date: Thu, 10 Jan 2013 11:12:05 +0400	[thread overview]
Message-ID: <1357801925.2050.41.camel@slavad-ubuntu> (raw)
In-Reply-To: <20130109210943.GA22054@wloczykij>

On Wed, 2013-01-09 at 22:09 +0100, Piotr Szymaniak wrote:
> On Tue, Jan 08, 2013 at 03:52:30PM +0300, Vyacheslav Dubeyko wrote:
> > 
[snip]

Thank you for additional details.

As I remember, you reported about issue with flush kernel thread firstly
and, then, about this issue. So, I think that you can have some similar
environment peculiarities as Elmer Zhang.

Could you share details of your virtual memory configuration
(especially, vm.min_free_kbytes)?

Could you share more detailed output of your system log? Especially, I
interested what was in the first case of the issue occurrence. But it
can be interested also part of system log that begins from system start
and ends with messages about remounting in RO state.

Thanks,
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-01-10  7:12 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-11-29 21:06 A lot of NILFS: bad btree node messages (readonly fs) Piotr Szymaniak
2012-11-30  6:09 ` Vyacheslav Dubeyko
2012-11-30  7:32   ` Piotr Szymaniak
2012-12-25  6:05     ` Vyacheslav Dubeyko
2012-12-25 20:54       ` Piotr Szymaniak
2013-01-03 21:49       ` Piotr Szymaniak
2013-01-04 12:46         ` Vyacheslav Dubeyko
     [not found]           ` <28ABE57F-66DD-491E-9FDB-A6CE3CF773FB-yeENwD64cLxBDgjK7y7TUQ@public.gmane.org>
2013-01-04 19:16             ` Piotr Szymaniak
2013-01-05 11:40               ` Vyacheslav Dubeyko
     [not found]                 ` <C2F4A5DE-538B-4468-9A6A-BA619EDDA462-yeENwD64cLxBDgjK7y7TUQ@public.gmane.org>
2013-01-05 16:47                   ` Piotr Szymaniak
2013-01-08 12:52                     ` Vyacheslav Dubeyko
     [not found]                       ` <504C0292-D0C6-426C-BDFD-1CD50FB32617-yeENwD64cLxBDgjK7y7TUQ@public.gmane.org>
2013-01-09  6:20                         ` Elmer Zhang
     [not found]                           ` <30D452FB-F1A5-425C-97ED-1A12CA4DCFD9-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2013-01-09 12:10                             ` Vyacheslav Dubeyko
2013-01-09 21:09                         ` Piotr Szymaniak
2013-01-10  7:12                           ` Vyacheslav Dubeyko [this message]
2013-01-12 21:24                             ` Piotr Szymaniak
2013-01-14 19:32                               ` Vyacheslav Dubeyko
2012-11-30  7:46   ` ARAI Shun-ichi

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=1357801925.2050.41.camel@slavad-ubuntu \
    --to=slava-yeenwd64clxbdgjk7y7tuq@public.gmane.org \
    --cc=freeboy6716-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
    --cc=linux-nilfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=splavgm-Re5JQEeQqe8AvxtiuMwx3w@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox