From: Arno Wagner <arno@wagner.name>
To: dm-crypt@saout.de
Subject: Re: [dm-crypt] dm-crypt flush-to-disk freezes
Date: Sun, 22 Aug 2010 23:51:42 +0200 [thread overview]
Message-ID: <20100822215142.GA16551@tansi.org> (raw)
In-Reply-To: <1282513364.3227.16.camel@fermat.scientia.net>
On Sun, Aug 22, 2010 at 11:42:44PM +0200, Christoph Anton Mitterer wrote:
> On Sun, 2010-08-22 at 21:52 +0200, Arno Wagner wrote:
> > What do I lose with barriers off?
> data security ;)
>
>
> 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.
Arno
--
Arno Wagner, Dr. sc. techn., Dipl. Inform., CISSP -- Email: arno@wagner.name
GnuPG: ID: 1E25338F FP: 0C30 5782 9D93 F785 E79C 0296 797F 6B50 1E25 338F
----
Cuddly UI's are the manifestation of wishful thinking. -- Dylan Evans
If it's in the news, don't worry about it. The very definition of
"news" is "something that hardly ever happens." -- Bruce Schneier
next prev parent reply other threads:[~2010-08-22 21:51 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 [this message]
2010-08-22 21:58 ` Christoph Anton Mitterer
2010-08-22 22:01 ` Christoph Anton Mitterer
2010-08-23 6:24 ` Heinz Diehl
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=20100822215142.GA16551@tansi.org \
--to=arno@wagner.name \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.