From: Vallo Kallaste <kalts@estpak.ee>
To: xfs@oss.sgi.com
Subject: Re: State of ext4 auto_da_alloc-like workarounds in XFS
Date: Mon, 21 Dec 2015 21:37:24 +0200 [thread overview]
Message-ID: <20151221193724.GD482@hape.internal> (raw)
In-Reply-To: <5678497F.1020104@sandeen.net>
On Mon, Dec 21, 2015 at 12:48:31PM -0600, Eric Sandeen <sandeen@sandeen.net> wrote:
[...]
> > 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?
>
> The sync-on-close-after-file-got-truncated case has been handled since 2007; see
>
> https://git.kernel.org/cgit/linux/kernel/git/dgc/linux-xfs.git/commit/?id=ba87ea699ebd9dd577bf055ebc4a98200e337542
>
> The sync-after-rename behavior was suggested and rejected for xfs, see
>
> http://marc.info/?t=139845506300002&r=1&w=2
>
> If you'd like to add this information to the XFS wiki, please do so!
Thanks, this is an exemplary answer, not to mention lightning fast as well!
I would consider if Wiki had at http://xfs.org/index.php/Special:RequestAccount page:
* Privacy policy http://xfs.org/index.php/XFS.org:Privacy_policy
* Terms of Service http://xfs.org/index.php?title=XFS.org:Terms_of_Service&action=edit&redlink=1
The latter being something I must read and agree on before I can request a user
account.
BR,
--
Vallo
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2015-12-21 19:37 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-21 18:37 State of ext4 auto_da_alloc-like workarounds in XFS Vallo Kallaste
2015-12-21 18:48 ` Eric Sandeen
2015-12-21 19:37 ` Vallo Kallaste [this message]
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=20151221193724.GD482@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox