From: "Joshua M. Clulow" <josh@sysmgr.org>
To: illumos-discuss <discuss@lists.illumos.org>
Subject: Re: [discuss] shutdown hang with zpools on ISCSI devices
Date: Tue, 6 Aug 2024 12:04:12 -0700 [thread overview]
Message-ID: <CAEwA5nJaRsBj_XbfJtn1dXMgJjj2zHZUSbxUWzDM01=uR1+vcA@mail.gmail.com> (raw)
In-Reply-To: <17229544470.58aA.943111@composer.illumos.topicbox.com>
On Tue, 6 Aug 2024 at 07:27, Carsten Grzemba via illumos-discuss
<discuss@lists.illumos.org> wrote:
> What does the shutdown process do with the zpools?
Pools that are still imported at the very last point, when the kernel
is preparing to reboot, are like any other file system: we try to sync
outstanding changes to disk, which usually generates at least a little
bit of I/O. Nothing is unmounted, just made consistent.
The reason this is a challenge for network file systems and block
devices, of course, is that we've already brought down the IP stack.
That's why the iSCSI initiator service unmounts file systems from
vfstab(5), and why your iSCSI pools likely need to be exported prior
to that point.
> It is not a zfs umount or zpool export. If so the zpool.cache file would be deleted.
Correct. An explicit export is required to remove a pool from the
cache file that was used when it was imported.
--
Joshua M. Clulow
http://blog.sysmgr.org
next prev parent reply other threads:[~2024-08-06 19:04 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-05 20:50 Carsten Grzemba
2024-08-05 21:46 ` [discuss] " Joshua M. Clulow
2024-08-06 5:17 ` Carsten Grzemba
2024-08-06 5:29 ` Carsten Grzemba
2024-08-06 5:46 ` Joshua M. Clulow
2024-08-06 6:36 ` Carsten Grzemba
2024-08-06 6:46 ` Joshua M. Clulow
2024-08-06 14:27 ` Carsten Grzemba
2024-08-06 15:16 ` Carsten Grzemba
2024-08-06 19:04 ` Joshua M. Clulow [this message]
2024-09-06 11:53 ` Illumos future and compatibility with Open-ZFS gea
2024-09-07 8:30 ` [discuss] " Joshua M. Clulow
2024-09-07 11:12 ` Gea
2024-09-07 16:38 ` Joshua M. Clulow
2024-09-07 21:37 ` Gea
2024-09-08 8:50 ` Jorge Schrauwen
2024-09-08 9:55 ` d
2024-09-09 10:41 ` Gea
2024-09-09 11:32 ` Toomas Soome
2024-09-09 9:29 ` Volker A. Brandt
2024-09-09 9:49 ` bronkoo
2024-09-09 11:13 ` Jorgen Lundman
2024-09-09 12:27 ` Gea
2024-09-09 14:47 ` gea
2024-09-09 19:29 ` Joshua M. Clulow
2024-12-11 8:47 ` zt958bjm via illumos-discuss
2024-12-11 8:56 ` zt958bjm via illumos-discuss
2024-12-11 9:01 ` zt958bjm via illumos-discuss
2024-12-11 10:09 ` Jorgen Lundman
2024-12-11 12:17 ` zt958bjm via illumos-discuss
2024-09-07 14:32 ` Miles Nordin
2024-08-05 22:45 ` [discuss] shutdown hang with zpools on ISCSI devices John D Groenveld
2024-08-05 22:55 ` Joshua M. Clulow
2024-08-06 15:56 ` Gordon Ross
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='CAEwA5nJaRsBj_XbfJtn1dXMgJjj2zHZUSbxUWzDM01=uR1+vcA@mail.gmail.com' \
--to=josh@sysmgr.org \
--cc=discuss@lists.illumos.org \
/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;
as well as URLs for NNTP newsgroup(s).