Kernel Newbies archive on
 help / color / Atom feed
From: "Valdis Klētnieks" <>
To: Jeno P <>
Subject: Re: fsync slowness + XFS -- Regd.
Date: Tue, 19 Mar 2019 01:32:48 -0400
Message-ID: <17020.1552973568@turing-police> (raw)
In-Reply-To: <>

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

  reply index

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-19  2:10 Jeno P
2019-03-19  5:32 ` Valdis Klētnieks [this message]
2019-03-19  6:06   ` Alex Painemilla

Reply instructions:

You may reply publically 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:

* 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 \ \ \ \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

Kernel Newbies archive on

Archives are clonable:
	git clone --mirror kernelnewbies/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 kernelnewbies kernelnewbies/ \
	public-inbox-index kernelnewbies

Newsgroup available over NNTP:

AGPL code for this site: git clone public-inbox