linux-ext4.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Sebastian Biedermann <biedermann@seceng.informatik.tu-darmstadt.de>
To: linux-ext4@vger.kernel.org
Subject: Writing one file, observing two writes
Date: Sun, 13 Apr 2014 11:49:07 -0400	[thread overview]
Message-ID: <534AB1F3.2060700@seceng.informatik.tu-darmstadt.de> (raw)

Dear ext4 developers,

I'm working on a research project about side channel attacks to hard drives.
My testbed runs Ubuntu Linux 12.04 with ext4 file system.

When writing a random file with dd command to my hard drive, I could see
the process jbd2/sda1
writing two times while it seems to wait a fixed period of time between
these two writes.

I actually think that the process is first writing the data to the
sectors and then updating the ext4 data base in a second step.
Is that true or am I wrong? Why is it waiting some seconds between these
two steps and on what is that delay depending?

Thank you!
Sebastian

             reply	other threads:[~2014-04-13 15:55 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-13 15:49 Sebastian Biedermann [this message]
2014-04-13 19:03 ` Writing one file, observing two writes Theodore Ts'o

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=534AB1F3.2060700@seceng.informatik.tu-darmstadt.de \
    --to=biedermann@seceng.informatik.tu-darmstadt.de \
    --cc=linux-ext4@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).