From: Joel Fernandes <agnel.joel@gmail.com>
To: linux-fsdevel@vger.kernel.org,
kernelnewbies <kernelnewbies@nl.linux.org>
Subject: ext3 writing of data before metadata in ordered mode
Date: Sun, 25 Oct 2009 14:33:59 -0700 [thread overview]
Message-ID: <9ff7a3bc0910251433k2c719989n981e3652162cafdf@mail.gmail.com> (raw)
In data=ordered mode the ext3_ordered_commit_write function marks the
buffers as dirty, how then does the JBD ensure that the data is
written before the metadata? Once the data buffers are marked as
dirty, JBD doesn't have control anymore over when the data is written
is actually written to disk right? Because the actually writing of the
data is handled by the page wtriteback mechanism (pdflush) right?
I might be missing something here, thanks for your time and patience.
-Joel
next reply other threads:[~2009-10-25 21:33 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-25 21:33 Joel Fernandes [this message]
2009-10-26 4:40 ` ext3 writing of data before metadata in ordered mode Mulyadi Santosa
2009-10-26 7:17 ` Joel Fernandes
2009-10-26 13:19 ` Josef Bacik
2009-10-26 17:21 ` Joel Fernandes
2009-10-26 17:58 ` Josef Bacik
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=9ff7a3bc0910251433k2c719989n981e3652162cafdf@mail.gmail.com \
--to=agnel.joel@gmail.com \
--cc=kernelnewbies@nl.linux.org \
--cc=linux-fsdevel@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).