From: Tom Vier <tmv@comcast.net>
To: reiserfs-list@namesys.com
Subject: dirsync doesn't seem to work
Date: Thu, 29 Jul 2004 21:15:05 -0400 [thread overview]
Message-ID: <20040730011505.GB4950@zero> (raw)
when i run this:
while true; do touch heh; rm -f heh; done
on reiserfs, it doesn't seem to be actually writing. the wait cpu % is very
low when using reiserfs or normal mode ext3. when i mount ext3 using dirsync,
and i run the loop, wait time is above 90%.
this is the best test method i can think of right now. i can't hear a
difference in the drive (which might be using write back cache, but i can't
reformat any of my scsi drives in ext3 right now to see they make more noise
with dirsync + write-through).
--
Tom Vier <tmv@comcast.net>
DSA Key ID 0x15741ECE
reply other threads:[~2004-07-30 1:15 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20040730011505.GB4950@zero \
--to=tmv@comcast.net \
--cc=reiserfs-list@namesys.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.