| 22 Mar 2025 |
 Arian | That makes 0 sense to me | 09:20:04 |
| Arian | Ah yeh we use online resize for cloud images etc. I remember now | 09:21:28 |
 @elvishjerricco:matrix.org | after repart finishes, I see Changed plugged -> dead for each of the partitions in the systemd debug logging, and then immediately after I see Changed dead -> plugged for them | 09:23:12 |
| @elvishjerricco:matrix.org | vda3: Processing udev action (SEQNUM=1400, ACTION=remove)
then I get a
vda: Processing udev action (SEQNUM=1401, ACTION=change)
And then I get
vda3: Processing udev action (SEQNUM=1404, ACTION=add)
| 09:23:57 |
| @elvishjerricco:matrix.org | * vda3: Processing udev action (SEQNUM=1400, ACTION=remove)
then I get a
vda: Processing udev action (SEQNUM=1401, ACTION=change)
And then I get
vda3: Processing udev action (SEQNUM=1404, ACTION=add)
| 09:24:15 |
| @elvishjerricco:matrix.org | I feel like this can't possibly be right, because then imagine what happens with a normal stage 2 repart service. It would repartition, and immediately cancel all mount jobs depending on those partitions, stopping local-fs.target | 09:26:43 |
| Arian | Is Dev/vda3 mounted at this point? | 09:27:35 |
| @elvishjerricco:matrix.org | no | 09:27:41 |
| Arian | Maybe you only get these events for unmounted partitions | 09:27:59 |
| @elvishjerricco:matrix.org | well that would still be the case in stage 2 | 09:28:25 |
| @elvishjerricco:matrix.org | for any non-root partitions | 09:28:28 |
| Arian | That would explain why it doesn mess with the root fs. But it would indeed screw things up for anything else in fstab | 09:28:34 |
| @elvishjerricco:matrix.org | I think I'm going to take my eyes off this problem for a bit and get some sleep. Arian Do you have any interest in taking a glance at my test config in the meantime? | 09:30:29 |
| @elvishjerricco:matrix.org | (it's using my fancy "installer-small" nixos test setup that makes installer tests way way more efficient) | 09:30:58 |
| Arian | Yah send a link. I might have a look later | 09:32:01 |
