From: Edward Shishkin <edward.shishkin@gmail.com>
To: Morgan Smith <moondog13@gmail.com>
Cc: ReiserFS Development mailing list <reiserfs-devel@vger.kernel.org>
Subject: Re: Flushing like mad
Date: Fri, 19 Jul 2013 15:22:17 +0200 [thread overview]
Message-ID: <51E93D89.8050801@gmail.com> (raw)
In-Reply-To: <51E82DF2.8030704@gmail.com>
Hello.
Yes, it can happen, especially under high workload.
Also you may observe the warning: "search by key:
too many iterations", which has the similar nature.
If those warnings are sporadic, then simply ignore them.
We are not ready to get rid of them completely for now,
as in some cases it indicates data corruption (in this
case the warnings look like flood).
Thanks for report,
Edward.
On 07/18/2013 08:03 PM, Morgan Smith wrote:
> Good morning.
>
> I have a machine with a reiser4 formatted drive of redundant data on it.
> The data is accessed and modified daily as if it were a production
> machine except that nobody cares if the data is lost.
>
> I have noticed these warnings in the daily logs:
>
> Jul 14 06:37:08 logan kernel: reiser4[ktxnmgrd:sdb1:r(31883)]: commit_current_atom (fs/reiser4/txnmgr.c:1049)[nikita-3176]:
>
> Jul 14 06:37:08 logan kernel: WARNING: Flushing like mad: 16384
>
>
> This is even after a file system check with fsck.reiser4 1.0.8 which
> reported 0 issues. I don't seem to have any performance issues or data
> corruptions though I'd like to provide what information I can regarding
> this if it's of any concern. I believe the drive was formatted with the
> following options:
>
> create=reg40,hash=tea_hash,fibration=lexic_fibre,formatting=smart
>
>
> -- Morgan
>
>
> --
> To unsubscribe from this list: send the line "unsubscribe reiserfs-devel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
prev parent reply other threads:[~2013-07-19 13:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-18 18:03 Flushing like mad Morgan Smith
2013-07-19 13:22 ` Edward Shishkin [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=51E93D89.8050801@gmail.com \
--to=edward.shishkin@gmail.com \
--cc=moondog13@gmail.com \
--cc=reiserfs-devel@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).