-
Notifications
You must be signed in to change notification settings - Fork 62
Closed
Description
From dogfood, after a 4/8/2025 update:
root@oxz_switch1:~# pilot host exec -c 'echo "oxp datasets" && zfs list -r -o name,mounted,creation | grep oxp | grep -v yes || true' 0-31
7 BRM27230045 ok: oxp datasets
8 BRM44220011 ok: oxp datasets
oxp_cf940e15-dbc5-481b-866a-4de4b018898e/crypt/debug/acfdd1ac-9ccb-42a7-a4a8-e8c4dbea6ce2 no Thu May 1 20:25 2025
9 BRM44220005 ok: oxp datasets
oxp_0ae29053-29a2-489e-a1e6-6aec0ecd05f8/crypt/debug/62180262-5748-43fe-932f-cd90f3d2fa1f no Fri Feb 28 18:45 2025
10 BRM42220009 ok: oxp datasets
11 BRM42220006 ok: oxp datasets
12 BRM42220057 ok: oxp datasets
13 BRM42220018 ok: oxp datasets
14 BRM42220051 ok: oxp datasets
16 BRM42220014 ok: oxp datasets
17 BRM42220017 ok: oxp datasets
21 BRM42220031 ok: oxp datasets
oxp_160691d8-33a1-4d7d-a48a-c3fd27d76822/crypt/debug/47f33f49-405d-4faa-a453-ab5d4dd0ceaf no Thu May 8 20:10 2025
23 BRM42220016 ok: oxp datasets
25 BRM44220010 ok: oxp datasets
Also seen in cockroachdb:
root@[fd00:1122:3344:105::3]:32221/omicron> SELECT id,time_created,state,zpool_id FROM support_bundle;
id | time_created | state | zpool_id
---------------------------------------+-------------------------------+--------+---------------------------------------
47f33f49-405d-4faa-a453-ab5d4dd0ceaf | 2025-05-08 19:44:45.972186+00 | active | 160691d8-33a1-4d7d-a48a-c3fd27d76822
62180262-5748-43fe-932f-cd90f3d2fa1f | 2025-02-28 18:45:18.306219+00 | active | 0ae29053-29a2-489e-a1e6-6aec0ecd05f8
acfdd1ac-9ccb-42a7-a4a8-e8c4dbea6ce2 | 2025-05-01 20:07:18.363585+00 | active | cf940e15-dbc5-481b-866a-4de4b018898e
(3 rows)
Of note: The zpool UUIDs of the debug datasets that aren't mounted line-up with the zpools of the bundles.
Why are these bundles preventing the debug dataset from being mounted? More investigation is needed
Metadata
Metadata
Assignees
Labels
No labels