From: Stan Hoeppner <stan@hardwarefreak.com>
To: xfs@oss.sgi.com
Subject: Re: Delaylog
Date: Tue, 14 Sep 2010 15:03:24 -0500 [thread overview]
Message-ID: <4C8FD50C.1030905@hardwarefreak.com> (raw)
In-Reply-To: <201009142106.24448.arekm@maven.pl>
Arkadiusz Miskiewicz put forth on 9/14/2010 2:06 PM:
> On Tuesday 14 of September 2010, Fabricio Archanjo wrote:
>> Hey all,
>>
>> I just trying delaylog in my server that has a mysql database. When
>> i monted my /var/lib/mysql with delaylog option, it showed me:
>> "Enabling EXPERIMENTAL delayed logging feature - use at your own
>> risk". Ok, i know it's experimental, but what kind of problem could i
>> have using delaylog?
>
> ... and what problems in case of system hang or power loss when compared to
> nodelaylog mode?
This was covered in prior posts IIRC. Delaylog holds more write
transactions in memory in an effort to decrease the amount of disk I/O
and optimize write patterns. The more blocks waiting in the in memory
log, the more data will be lost due to power outage, controller/disk
failure, storage HBA/network failure (iSCSI/FC), kernel panics, etc.
Same failure modes as before, but with potentially greater loss of
data--unless there is an undiscovered bug that can wreck the entire
filesystem. ;) Which I believe is the reason for the "experimental"
boilerplate.
--
Stan
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2010-09-14 20:02 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <AANLkTin6FSBK3tMXhSxDuLdjyb+R0LhNnaa2CKt37FcV@mail.gmail.com>
2010-09-14 19:06 ` Delaylog Arkadiusz Miskiewicz
2010-09-14 19:20 ` Delaylog Fabricio Archanjo
2010-09-14 20:03 ` Stan Hoeppner [this message]
2010-09-14 21:32 ` Delaylog Fabricio Archanjo
2010-09-14 23:23 ` Delaylog Christoph Hellwig
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=4C8FD50C.1030905@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