Re: wait until swapoff is actually finished (it returns too early)?

To: debian-user@lists.debian.org
Subject: Re: wait until swapoff is *actually* finished (it returns too early)?
From: Stefan Monnier <monnier@iro.umontreal.ca>
Date: Thu, 22 Aug 2024 08:43:11 -0400
Message-id: <[🔎] jwva5h4g24b.fsf-monnier+gmane.linux.debian.user@gnu.org>
References: <[🔎] Pine.BSM.4.64L.2408202323480.21887@herc.mirbsd.org> <[🔎] 60c30fb7-e1e7-4dac-bfd9-0b257cea7511@gmail.com> <[🔎] Pine.BSM.4.64L.2408212105060.28533@herc.mirbsd.org>

> Not the right condition though… it’s absent there but still in use.
> I am looking for the right thing to check…

How 'bout checking the success of `cryptdisks_stop`?


        Stefan

Reply to:

Follow-Ups:
- Re: wait until swapoff is *actually* finished (it returns too early)?
  - From: Mike Castle <dalgoda+debian@gmail.com>

References:
- wait until swapoff is *actually* finished (it returns too early)?
  - From: Thorsten Glaser <tg@debian.org>
- Re: wait until swapoff is *actually* finished (it returns too early)?
  - From: Franco Martelli <martellif67@gmail.com>
- Re: wait until swapoff is *actually* finished (it returns too early)?
  - From: Thorsten Glaser <tg@debian.org>

Prev by Date: Re: What tool(s) reports OS buss width, which processor present?
Next by Date: Re: update-alternatives: install with permanent arguments
Previous by thread: Re: wait until swapoff is *actually* finished (it returns too early)?
Next by thread: Re: wait until swapoff is *actually* finished (it returns too early)?
Index(es):
- Date
- Thread

Re: wait until swapoff is *actually* finished (it returns too early)?

Re: wait until swapoff is actually finished (it returns too early)?