From: "Valdis Klētnieks" <valdis.kletnieks@vt.edu>
To: Jeno P <write2jeno@gmail.com>
Cc: kernelnewbies@kernelnewbies.org
Subject: Re: fsync slowness + XFS -- Regd.
Date: Tue, 19 Mar 2019 01:32:48 -0400 [thread overview]
Message-ID: <17020.1552973568@turing-police> (raw)
In-Reply-To: <CAAsGhvRuaBqfmatoYRrjD+Hg8zWrs=PC25gMcfVtu1CiTXpH-A@mail.gmail.com>
On Tue, 19 Mar 2019 07:40:29 +0530, Jeno P said:
> One of my module *(C/C++)* is writing to log files and periodically flushes
> it using *fsync()*. Even for small amount of data, *fsync* is taking more
> time *(>15 seconds)* than expected.
Is it possible that some other process is applying a file lock to the log file?
Any signs of I/O errors? 15 seconds is the sort of delay you might see on a
RAID controller with one dead or partially dead disk throwing timeouts...
_______________________________________________
Kernelnewbies mailing list
Kernelnewbies@kernelnewbies.org
https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
next prev parent reply other threads:[~2019-03-19 6:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-19 2:10 fsync slowness + XFS -- Regd Jeno P
2019-03-19 5:32 ` Valdis Klētnieks [this message]
2019-03-19 6:06 ` Alex Painemilla
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=17020.1552973568@turing-police \
--to=valdis.kletnieks@vt.edu \
--cc=kernelnewbies@kernelnewbies.org \
--cc=write2jeno@gmail.com \
/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).