From: fugazzi® <fugazzi99@gmail.com>
To: Btrfs mailing list <linux-btrfs@vger.kernel.org>
Subject: BTRFS - Write Barriers
Date: Thu, 31 Dec 2015 09:01:51 +0000 [thread overview]
Message-ID: <4794805.EoAJ2iVUQK@orione> (raw)
Hi everyone :-)
Just one question for the gurus here.
I was wondering: if I disable write barriers in btrfs with the mount option
nobarrier I just disable the periodic flushes of the hardware disk cache or
I'm disabling also the order of the writes directed to the hard disk?
What I mean is: is it safe to disable write barrier with a UPS with which I
will likely have the hardware always powered even in the event of a kernel
crash, freeze, etc?
I'm asking because if also the ordering of the write is no more guaranteed I
guess it would not be safe to disable write barrier even if the possibility of
an unexpected power down of the HD was remote because in the case of a crash
the order of the write would be messed up anyway and we could boot up with a
completely corrupted fs.
Thank you very much for your kinds answers.
Warm Regards,
Mario
next reply other threads:[~2015-12-31 9:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-31 9:01 fugazzi® [this message]
2015-12-31 9:34 ` BTRFS - Write Barriers Duncan
2015-12-31 10:26 ` fugazzi®
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=4794805.EoAJ2iVUQK@orione \
--to=fugazzi99@gmail.com \
--cc=linux-btrfs@vger.kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).