From: Phillip Susi <phill@thesusis.net>
To: Damien Le Moal <dlemoal@kernel.org>
Cc: linux-ide@vger.kernel.org, linux-scsi@vger.kernel.org,
"Martin K . Petersen" <martin.petersen@oracle.com>,
John Garry <john.g.garry@oracle.com>,
Rodrigo Vivi <rodrigo.vivi@intel.com>,
Paul Ausbeck <paula@soe.ucsc.edu>,
Kai-Heng Feng <kai.heng.feng@canonical.com>,
Joe Breuer <linux-kernel@jmbreuer.net>,
Geert Uytterhoeven <geert@linux-m68k.org>,
Chia-Lin Kao <acelan.kao@canonical.com>
Subject: Re: [PATCH v8 00/23] Fix libata suspend/resume handling and code cleanup
Date: Mon, 02 Oct 2023 20:27:12 -0400 [thread overview]
Message-ID: <87h6n87dac.fsf@vps.thesusis.net> (raw)
In-Reply-To: <874jj8sia5.fsf@vps.thesusis.net>
Phillip Susi <phill@thesusis.net> writes:
> I noticed though, that when entering system suspend, a disk that has
> already been runtime suspended is resumed only to immediately be
> suspended again before the system suspend. That shouldn't happen should
> it?
It seems that it is /sys/power/sync_on_suspend. The problem went away
when I unmounted the disk, or I could make the disk wake up by running
sync. I thought that it used to be that as long as you mounted an ext4
filesystem with -o relatime, it wouldn't keep dirtying the cache as long
as you weren't actually writing to the filesystem. Either I'm
misremembering something, or this is no longer the case. Also if there
are dirty pages in the cache, I thought the default was for them to be
written out after 5 seconds, which would keep the disk awake, rather
than waiting until system suspend to sync.
I guess I could mount the filesystem readonly. It's probably not a good
idea to disable sync_on_suspend for the whole system.
next prev parent reply other threads:[~2023-10-03 0:36 UTC|newest]
Thread overview: 50+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-27 14:18 [PATCH v8 00/23] Fix libata suspend/resume handling and code cleanup Damien Le Moal
2023-09-27 14:18 ` [PATCH v8 01/23] ata: libata-core: Fix ata_port_request_pm() locking Damien Le Moal
2023-09-27 14:18 ` [PATCH v8 02/23] ata: libata-core: Fix port and device removal Damien Le Moal
2023-09-27 14:18 ` [PATCH v8 03/23] ata: libata-scsi: link ata port and scsi device Damien Le Moal
2023-09-27 14:18 ` [PATCH v8 04/23] scsi: sd: Differentiate system and runtime start/stop management Damien Le Moal
2023-09-27 19:50 ` Martin K. Petersen
2023-10-10 13:09 ` Phillip Susi
2023-10-10 14:04 ` Damien Le Moal
2023-10-15 16:14 ` Phillip Susi
2023-10-15 22:44 ` Damien Le Moal
2023-10-16 12:39 ` Phillip Susi
2023-10-16 12:55 ` Damien Le Moal
2023-10-17 18:03 ` Phillip Susi
2023-10-17 23:32 ` Damien Le Moal
2023-10-20 19:00 ` Phillip Susi
2023-10-18 6:16 ` Damien Le Moal
2023-10-20 21:23 ` Phillip Susi
2023-10-23 5:51 ` Damien Le Moal
2023-10-26 21:21 ` Phillip Susi
2023-09-27 14:18 ` [PATCH v8 05/23] ata: libata-scsi: Disable scsi device manage_system_start_stop Damien Le Moal
2023-09-27 14:18 ` [PATCH v8 06/23] scsi: Do not attempt to rescan suspended devices Damien Le Moal
2023-09-27 19:51 ` Martin K. Petersen
2023-09-27 14:18 ` [PATCH v8 07/23] ata: libata-scsi: Fix delayed scsi_rescan_device() execution Damien Le Moal
2023-09-27 14:18 ` [PATCH v8 08/23] ata: libata-core: Do not register PM operations for SAS ports Damien Le Moal
2023-09-27 14:18 ` [PATCH v8 09/23] scsi: sd: Do not issue commands to suspended disks on shutdown Damien Le Moal
2023-09-27 19:52 ` Martin K. Petersen
2023-09-27 14:18 ` [PATCH v8 10/23] ata: libata-core: Fix compilation warning in ata_dev_config_ncq() Damien Le Moal
2023-09-27 14:18 ` [PATCH v8 11/23] ata: libata-eh: Fix compilation warning in ata_eh_link_report() Damien Le Moal
2023-09-27 14:18 ` [PATCH v8 12/23] scsi: Remove scsi device no_start_on_resume flag Damien Le Moal
2023-09-27 19:52 ` Martin K. Petersen
2023-09-27 14:18 ` [PATCH v8 13/23] ata: libata-scsi: Cleanup ata_scsi_start_stop_xlat() Damien Le Moal
2023-09-27 14:18 ` [PATCH v8 14/23] ata: libata-core: Synchronize ata_port_detach() with hotplug Damien Le Moal
2023-09-27 14:18 ` [PATCH v8 15/23] ata: libata-core: Detach a port devices on shutdown Damien Le Moal
2023-09-27 14:18 ` [PATCH v8 16/23] ata: libata-core: Remove ata_port_suspend_async() Damien Le Moal
2023-09-27 14:18 ` [PATCH v8 17/23] ata: libata-core: Remove ata_port_resume_async() Damien Le Moal
2023-09-27 14:18 ` [PATCH v8 18/23] ata: libata-core: Do not poweroff runtime suspended ports Damien Le Moal
2023-09-27 14:18 ` [PATCH v8 19/23] ata: libata-core: Do not resume " Damien Le Moal
2023-09-27 14:18 ` [PATCH v8 20/23] ata: libata-sata: Improve ata_sas_slave_configure() Damien Le Moal
2023-09-27 14:18 ` [PATCH v8 21/23] ata: libata-eh: Improve reset error messages Damien Le Moal
2023-09-27 14:18 ` [PATCH v8 22/23] ata: libata-eh: Reduce "disable device" message verbosity Damien Le Moal
2023-09-27 14:18 ` [PATCH v8 23/23] ata: libata: Cleanup inline DMA helper functions Damien Le Moal
2023-10-02 23:39 ` [PATCH v8 00/23] Fix libata suspend/resume handling and code cleanup Phillip Susi
2023-10-03 0:27 ` Phillip Susi [this message]
2023-10-03 0:44 ` Damien Le Moal
2023-10-03 21:22 ` Phillip Susi
2023-10-03 23:46 ` Damien Le Moal
2023-10-04 21:01 ` Phillip Susi
2023-10-04 22:33 ` Damien Le Moal
2023-10-05 12:38 ` Phillip Susi
2023-10-03 0:32 ` Damien Le Moal
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=87h6n87dac.fsf@vps.thesusis.net \
--to=phill@thesusis.net \
--cc=acelan.kao@canonical.com \
--cc=dlemoal@kernel.org \
--cc=geert@linux-m68k.org \
--cc=john.g.garry@oracle.com \
--cc=kai.heng.feng@canonical.com \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@jmbreuer.net \
--cc=linux-scsi@vger.kernel.org \
--cc=martin.petersen@oracle.com \
--cc=paula@soe.ucsc.edu \
--cc=rodrigo.vivi@intel.com \
/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.