public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Emmanuel Florac <eflorac@intellique.com>
To: Rakesh Patel <patelrakeshcomp@gmail.com>
Cc: xfs@oss.sgi.com
Subject: Re: regarding journaling mode
Date: Thu, 9 Jul 2015 15:32:24 +0200	[thread overview]
Message-ID: <20150709153224.0f197584@harpe.intellique.com> (raw)
In-Reply-To: <CAMcfJ7sZaLwO7Gz8f7E9GBrX75Ddc8JvLntPRpjw=KPNOV7TLg@mail.gmail.com>

Le Thu, 9 Jul 2015 10:18:55 +0530
Rakesh Patel <patelrakeshcomp@gmail.com> écrivait:

> https://www.kernel.org/doc/Documentation/filesystems/ext4.txt
> 
> data=writeback		Data ordering is not preserved, data
> may be written into the main file system after its metadata has been
> 			committed to the journal.

First, this is ext4, not xfs. However XFS behaves the same way, that
is, it may update metadata BEFORE the data has been committed to disk.
This has been the standard behaviour of all filesystems since linux
2.6.30 I guess.

If you're interested in the details, search for O_PONIES on the web...

-- 
------------------------------------------------------------------------
Emmanuel Florac     |   Direction technique
                    |   Intellique
                    |	<eflorac@intellique.com>
                    |   +33 1 78 94 84 02
------------------------------------------------------------------------

_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs

  parent reply	other threads:[~2015-07-09 13:32 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-09  4:48 regarding journaling mode Rakesh Patel
2015-07-09  8:46 ` Jan Kara
2015-07-09 11:47   ` Rakesh Patel
2015-07-09 13:32 ` Emmanuel Florac [this message]
  -- strict thread matches above, loose matches on Subject: below --
2015-07-06  6:08 Rakesh Patel
2015-07-07  0:24 ` Dave Chinner
2015-07-07  2:51   ` rakesh patel
2015-07-09  2:43   ` rakesh patel

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=20150709153224.0f197584@harpe.intellique.com \
    --to=eflorac@intellique.com \
    --cc=patelrakeshcomp@gmail.com \
    --cc=xfs@oss.sgi.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox