From: Stan Hoeppner <stan@hardwarefreak.com>
To: xfs@oss.sgi.com
Subject: Re: Slow delete
Date: Tue, 20 Jul 2010 12:09:05 -0500 [thread overview]
Message-ID: <4C45D831.5010102@hardwarefreak.com> (raw)
In-Reply-To: <201007201304.28490@zmi.at>
Michael Monnerie put forth on 7/20/2010 6:04 AM:
> Can someone guess the exact problems that can happen with delayed
> transaction on a crash?
The only real crash scenario difference, as I understand it, is that with
delayed logging enabled you'll potentially lose more data due to crash as more
is held memory resident with delayed logging enabled. The characteristics of
the data loss are the same with and without this enabled, it's just
potentially more severe with delayed logging enabled.
If your systems are prone to power loss, hardware failures, or kernel panics,
I'd not enable delayed logging. If your systems are rock solid, and you can
benefit from the minor decrease in file fragmentation and the increase in mass
file delete speed, then enable it.
--
Stan
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2010-07-20 17:06 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <AANLkTinPmhJRD3CDdsHtkLFzYd2jF9ee7gPqgO6XBSfl@mail.gmail.com>
2010-07-05 15:13 ` Slow delete Emmanuel Florac
2010-07-05 15:33 ` Andrei Deftu
2010-07-05 18:21 ` Peter Grandi
2010-07-05 18:54 ` Christoph Hellwig
2010-07-05 23:34 ` Dave Chinner
2010-07-12 12:17 ` Michael Monnerie
2010-07-19 18:54 ` Alex Elder
2010-07-20 11:04 ` Michael Monnerie
2010-07-20 17:09 ` Stan Hoeppner [this message]
2010-07-20 23:18 ` Dave Chinner
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=4C45D831.5010102@hardwarefreak.com \
--to=stan@hardwarefreak.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