| 22 Mar 2025 |
ElvishJerricco | is it not normal for a device's partitions to be removed and added from udev's perspective when the device is partscanned? | 09:19:01 |
Arian | Well you just said it's possible to resize a partition that is mounted. In that case it doesn't sound like sane behaviour that the underlying device would disappear and appear no | 09:19:50 |
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 | 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 | 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 | * 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 | 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 | no | 09:27:41 |
Arian | Maybe you only get these events for unmounted partitions | 09:27:59 |
ElvishJerricco | well that would still be the case in stage 2 | 09:28:25 |
ElvishJerricco | 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 | 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 | (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 |
Arian | Though I'm gonna do some touristic stuff with @flokli:matrix.org first | 09:32:13 |
ElvishJerricco | Arian: https://github.com/ElvishJerricco/nixpkgs/commits/installer-small/
The last commit probably breaks all the other ones so if you're interested in the installer-small stuff check out the one before it. But the last one contains the repart test case
| 09:37:23 |
ElvishJerricco | * Arian: https://github.com/ElvishJerricco/nixpkgs/commits/installer-small/
The last commit probably breaks all the other ones so if you're interested in the installer-small stuff check out the ones before it. But the last one contains the repart test case
| 09:37:34 |
| 23 Mar 2025 |
@srestegosaurio:tchncs.de | If I assign a non-existent slice to a service, will it be created with default values or return an error? | 02:42:45 |
Arian | I dont remember | 09:22:13 |
Arian | Try it out? | 09:22:20 |
antifuchs | soooo how long is scripted initrd going to be a thing? I have a truly annoying (semi-guaranteed to be racy) nixos test for scripted, and would love to get rid of it someday | 23:39:24 |
ElvishJerricco | I have not made as much time as I usually do for nixos stuff since 24.11, so systemd by default in 25.05 is unlikely, again :( | 23:44:41 |
ElvishJerricco | plus I've been sidetracked by a couple other nixos things like the ISO | 23:45:08 |
antifuchs | understandable yet sad | 23:45:13 |
antifuchs | no worries, I'm gonna figure this out one way or the other | 23:45:24 |
antifuchs | can you think of a good way to halt the boot process in scripted initrd until a condition is met? I have been trying
boot.initrd.preLVMCommands = ''
while ! [ -f /tmp/fnord ] ; do
sleep 1
done
'';
and it sure seems to stop the boot but you don't get output from the machine in case anything goes wrong...
| 23:46:42 |
ElvishJerricco | yea that's, uh... a good use case for systemd initrd :P | 23:48:41 |