public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: George Nychis <gnychis@cmu.edu>
To: lkml <linux-kernel@vger.kernel.org>
Subject: hanging in fsync for 3+ seconds
Date: Tue, 08 Jan 2008 13:04:49 -0500	[thread overview]
Message-ID: <4783BB41.4010707@cmu.edu> (raw)

Hi all,

I noticed that all of a sudden my disk writes using VIM/EMACS are taking 
3+ seconds for even just a single byte.  So, I've used strace to narrow 
it down to fsync.

The following log is an fsync opening up a new file 'test' inserting a 
't' and writing and quitting in vim:
   http://www.andrew.cmu.edu/user/gnychis/slog

If you do a search for the only fsync, you will see it takes more than 3 
seconds:
   15171      0.000094 fsync(6)            = 0 <3.386504>

What can I do to determine why the fsync is taking so long?  I am not 
getting any disk error messages in system logs.

Info about my system:
   Ubuntu Gutsy Gibbon desktop machine, updated as of last night
   Linux 2.6.22-14-generic #1 SMP i686 GNU/Linux, running reiserFS.

Thanks!
George

             reply	other threads:[~2008-01-08 18:17 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-08 18:04 George Nychis [this message]
2008-01-08 20:09 ` hanging in fsync for 3+ seconds George Nychis

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=4783BB41.4010707@cmu.edu \
    --to=gnychis@cmu.edu \
    --cc=linux-kernel@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