public inbox for dm-crypt@saout.de
 help / color / mirror / Atom feed
From: "Michael Kjörling" <michael@kjorling.se>
To: dm-crypt@saout.de
Subject: Re: [dm-crypt] LUKS2 SSD swap and system freeze
Date: Tue, 15 Dec 2020 11:59:20 +0000	[thread overview]
Message-ID: <fa44642d-98ea-424a-a055-4455aa093050@localhost> (raw)
In-Reply-To: <de03f33e-76cb-7eb5-836f-438815515beb@gmail.com>

On 15 Dec 2020 11:42 +0100, from germano.massullo@gmail.com (Germano Massullo):
> To check if the complete stuck of the system was caused by encryption, I
> tried to disable SSD swap, and create a unencrypted swap on a regular
> HDD, and then when I had write bursts, the system slowed, but it did not
> freeze.

Note that by doing so, you actually changed at least two things at
once: absence/presence of encryption, and SSD/HDD. There is also a
possibility that you changed the properties of the storage
interconnect. You've shown that by changing all at once, you can
eliminate or introduce the problem, but you haven't unequivocally
shown which specific change made the difference.

To eliminate those factors and further narrow down the problem, can
you change just _one_ of those at a time? For example, do you still
see the same issue with similarly encrypted swap on the HDD, or with
unencrypted swap on the SSD? The answer would help at least somewhat
to lay the blame on either the storage device or the cryptography.

Also, have you checked the SMART data for the SSD?

Another thing that could be worth testing is to access that system
over the network. Assuming your firewall settings allow ICMP, does it
respond to pings while appearing frozen, for example?

-- 
Michael Kjörling • https://michael.kjorling.se • michael@kjorling.se
 “Remember when, on the Internet, nobody cared that you were a dog?”

WARNING: multiple messages have this Message-ID (diff)
From: "Michael Kjörling" <michael@kjorling.se>
To: dm-crypt@saout.de
Subject: Re: [dm-crypt] LUKS2 SSD swap and system freeze
Date: Tue, 15 Dec 2020 11:59:20 +0000	[thread overview]
Message-ID: <fa44642d-98ea-424a-a055-4455aa093050@localhost> (raw)
Message-ID: <20201215115920.rN_o68ctnV8Q02L-sVYyXYsbdZbYgOjblZ7qUNHKhg8@z> (raw)
In-Reply-To: <de03f33e-76cb-7eb5-836f-438815515beb@gmail.com>

On 15 Dec 2020 11:42 +0100, from germano.massullo@gmail.com (Germano Massullo):
> To check if the complete stuck of the system was caused by encryption, I
> tried to disable SSD swap, and create a unencrypted swap on a regular
> HDD, and then when I had write bursts, the system slowed, but it did not
> freeze.

Note that by doing so, you actually changed at least two things at
once: absence/presence of encryption, and SSD/HDD. There is also a
possibility that you changed the properties of the storage
interconnect. You've shown that by changing all at once, you can
eliminate or introduce the problem, but you haven't unequivocally
shown which specific change made the difference.

To eliminate those factors and further narrow down the problem, can
you change just _one_ of those at a time? For example, do you still
see the same issue with similarly encrypted swap on the HDD, or with
unencrypted swap on the SSD? The answer would help at least somewhat
to lay the blame on either the storage device or the cryptography.

Also, have you checked the SMART data for the SSD?

Another thing that could be worth testing is to access that system
over the network. Assuming your firewall settings allow ICMP, does it
respond to pings while appearing frozen, for example?

-- 
Michael Kjörling • https://michael.kjorling.se • michael@kjorling.se
 “Remember when, on the Internet, nobody cared that you were a dog?”

_______________________________________________
dm-crypt mailing list
dm-crypt@saout.de
https://www.saout.de/mailman/listinfo/dm-crypt

  parent reply	other threads:[~2020-12-15 11:59 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-15 10:42 [dm-crypt] LUKS2 SSD swap and system freeze Germano Massullo
2020-12-15 10:42 ` Germano Massullo
2020-12-15 11:59 ` Michael Kjörling [this message]
2020-12-15 11:59   ` Michael Kjörling
2020-12-22 13:31 ` Milan Broz

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=fa44642d-98ea-424a-a055-4455aa093050@localhost \
    --to=michael@kjorling.se \
    --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