From: Heinz Diehl <htd@fancy-poultry.org>
To: dm-crypt@saout.de
Subject: Re: [dm-crypt] dm-crypt flush-to-disk freezes
Date: Mon, 23 Aug 2010 08:24:16 +0200 [thread overview]
Message-ID: <20100823062416.GA6456@fancy-poultry.org> (raw)
In-Reply-To: <20100822215142.GA16551@tansi.org>
On 23.08.2010, Arno Wagner wrote:
> > In case of the filesystem barriers (not the IO barriers, which are
> > different AFAIK) they're used to make sure, that the COMMITS in the
> > journal are written after the journal is correctly flushed out.
> If that means I am back to ext2 safety levels, then I can
> live with that.
You could turn the hardware wb cache of your harddrive off and leave the
barriers off too..
I've been running my disks a liftime without barrier support without any
hassle, because it improves speed and interactivity a lot, but I must
admit that my machines are all UPS secured.
/dev/mapper/root on / type xfs (rw,noatime,logbsize=256k,logbufs=2,nobarrier)
/dev/mapper/home on /home type xfs (rw,noatime,logbsize=256k,logbufs=2,nobarrier)
next prev parent reply other threads:[~2010-08-23 6:24 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-17 18:46 [dm-crypt] dm-crypt flush-to-disk freezes Arno Wagner
2010-08-18 8:31 ` Heinz Diehl
2010-08-18 11:09 ` Rick Moritz
2010-08-18 11:43 ` Milan Broz
2010-08-18 13:18 ` Heinz Diehl
2010-08-18 14:36 ` Milan Broz
2010-08-18 13:22 ` Heinz Diehl
2010-08-18 14:12 ` Arno Wagner
2010-08-18 14:47 ` Milan Broz
2010-08-18 15:44 ` Arno Wagner
2010-08-22 19:52 ` Arno Wagner
2010-08-22 21:42 ` Christoph Anton Mitterer
2010-08-22 21:51 ` Arno Wagner
2010-08-22 21:58 ` Christoph Anton Mitterer
2010-08-22 22:01 ` Christoph Anton Mitterer
2010-08-23 6:24 ` Heinz Diehl [this message]
2010-08-23 0:47 ` Arno Wagner
2010-08-23 7:13 ` Milan Broz
2010-08-25 2:40 ` Arno Wagner
2010-08-25 14:13 ` Heinz Diehl
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=20100823062416.GA6456@fancy-poultry.org \
--to=htd@fancy-poultry.org \
--cc=dm-crypt@saout.de \
/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