From: Arno Wagner <arno@wagner.name>
To: dm-crypt@saout.de
Subject: Re: [dm-crypt] Computer locking up on heavy disk IO
Date: Tue, 1 Aug 2017 11:57:20 +0200 [thread overview]
Message-ID: <20170801095720.GA12498@tansi.org> (raw)
In-Reply-To: <200f2782-fc53-5555-036e-2cf5891375b4@gmail.com>
Maybe your disk is dying or your CPU is inadequately cooled?
Or there is something else putting high load on your machine?
Regards,
Arno
On Tue, Aug 01, 2017 at 10:52:48 CEST, heinrich5991@gmail.com wrote:
> Hi,
>
> I've noticed that my computer performs worse than optimal in cases of
> much disk IO. Now that I tried to use dd to securely erase a large disk
> (as in 2.19 of the FAQ at
> https://gitlab.com/cryptsetup/cryptsetup/wikis/FrequentlyAskedQuestions#2-setup),
> the computer completely locked up after half a minute or so. Before
> locking up one completely, it showed high load (>80) and high io wait. I
> was able to reboot the computer using Magic SysRq sequences, although
> they had a big delay.
>
> Previously, I tried to see how fast the drive can go and just dd'ed
> /dev/zero directly onto it. The computer handled that one fine, disk
> transfer averaged out at ~150MiB/s.
>
> # Tests are approximate using memory only (no storage IO).
> PBKDF2-sha1 1016062 iterations per second for 256-bit key
> PBKDF2-sha256 1432480 iterations per second for 256-bit key
> PBKDF2-sha512 976327 iterations per second for 256-bit key
> PBKDF2-ripemd160 815377 iterations per second for 256-bit key
> PBKDF2-whirlpool 580606 iterations per second for 256-bit key
> # Algorithm | Key | Encryption | Decryption
> aes-cbc 128b 655.6 MiB/s 2261.2 MiB/s
> serpent-cbc 128b 80.7 MiB/s 323.3 MiB/s
> twofish-cbc 128b 186.4 MiB/s 352.1 MiB/s
> aes-cbc 256b 481.6 MiB/s 1724.6 MiB/s
> serpent-cbc 256b 80.7 MiB/s 323.2 MiB/s
> twofish-cbc 256b 186.4 MiB/s 351.9 MiB/s
> aes-xts 256b 1956.1 MiB/s 1965.6 MiB/s
> serpent-xts 256b 332.8 MiB/s 316.9 MiB/s
> twofish-xts 256b 345.8 MiB/s 347.2 MiB/s
> aes-xts 512b 1526.4 MiB/s 1522.7 MiB/s
> serpent-xts 512b 333.4 MiB/s 316.8 MiB/s
> twofish-xts 512b 345.5 MiB/s 346.7 MiB/s
>
> Thanks
> _______________________________________________
> dm-crypt mailing list
> dm-crypt@saout.de
> http://www.saout.de/mailman/listinfo/dm-crypt
--
Arno Wagner, Dr. sc. techn., Dipl. Inform., Email: arno@wagner.name
GnuPG: ID: CB5D9718 FP: 12D6 C03B 1B30 33BB 13CF B774 E35C 5FA1 CB5D 9718
----
A good decision is based on knowledge and not on numbers. -- Plato
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:[~2017-08-01 10:03 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-01 8:52 [dm-crypt] Computer locking up on heavy disk IO heinrich5991
2017-08-01 9:57 ` Arno Wagner [this message]
2017-08-01 10:25 ` heinrich5991
2017-08-01 20:22 ` heinrich5991
2017-08-01 20:40 ` Arno Wagner
2017-08-01 22:08 ` heinrich5991
2017-08-01 20:47 ` Michael Kjörling
2017-08-01 22:19 ` heinrich5991
2017-08-01 23:17 ` [dm-crypt] Fwd: " heinrich5991
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=20170801095720.GA12498@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.