All of lore.kernel.org
 help / color / mirror / Atom feed
From: Vallo Kallaste <kalts@estpak.ee>
To: xfs@oss.sgi.com
Subject: State of ext4 auto_da_alloc-like workarounds in XFS
Date: Mon, 21 Dec 2015 20:37:26 +0200	[thread overview]
Message-ID: <20151221183726.GC482@hape.internal> (raw)

Hi

The ext4 workaround for wrong-but-common truncate/rename cases can be found at
https://en.wikipedia.org/wiki/Ext4#Delayed_allocation_and_potential_data_loss
This is the default "auto_da_alloc" mount option.

There is no mention of similar workaround in XFS FAQ at
http://xfs.org/index.php/XFS_FAQ nor
Wiki article at http://en.wikipedia.org/wiki/XFS
I suggest adding such a section.

I have read the thread at
http://article.gmane.org/gmane.comp.file-systems.xfs.general/53366
There seems to be definite answer at the top of
http://article.gmane.org/gmane.comp.file-systems.xfs.general/53376

But besides that I found
http://article.gmane.org/gmane.linux.kernel/812588 where it's mentioned that
/--/
The bigger problem from my perspective is that XFS is only doing this for the
truncate case, and (from what I've been told) not for the rename case.
/--/

I'd like to know the current state of ext4 auto_da_alloc-like workarounds in XFS,
particularly for RHEL7. Considering the two cases in
https://en.wikipedia.org/wiki/Ext4#Delayed_allocation_and_potential_data_loss
is XFS behaving the same as ext4, both mounted with default options?

thanks,
-- 
Vallo

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

             reply	other threads:[~2015-12-21 18:37 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-21 18:37 Vallo Kallaste [this message]
2015-12-21 18:48 ` State of ext4 auto_da_alloc-like workarounds in XFS Eric Sandeen
2015-12-21 19:37   ` Vallo Kallaste
2015-12-21 19:47     ` Eric Sandeen

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=20151221183726.GC482@hape.internal \
    --to=kalts@estpak.ee \
    --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 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.