| 15 Mar 2026 |
 matthewcroughan | Mic92: any idea why the CI fails for https://github.com/nix-community/disko/pull/1235 | 12:52:29 |
| 18 Mar 2026 |
|  Sol Astrius Phoenix joined the room. | 21:38:56 |
| Sol Astrius Phoenix changed their display name from sol to Sol Astrius Phoenix. | 21:54:30 |
 ed209 | what would be required to implement this? https://github.com/nix-community/disko/issues/1189 | 22:40:02 |
| 20 Mar 2026 |
|  Evrim Ulu joined the room. | 13:03:20 |
| 23 Mar 2026 |
|  XYenon joined the room. | 10:50:22 |
| 27 Mar 2026 |
|  Yushi joined the room. | 09:51:30 |
| Yushi | Hi everyone. If I want to add a new zfs dataset, do I create the dataset manually and then add that dataset to disko config so that disko can help manage the corresponding fileSystems config? | 09:54:41 |
| Yushi | I mean on a running system | 09:56:22 |
 magic_rb | With just disko, its gonna have to be manual. Have a look at https://redalder.org/blog/disko-zfs-declaratively-managing-zfs-datasets.html | 10:25:58 |
| Yushi | Thanks. disko-zfs seems quite handy for a zfs system. | 11:01:14 |
| magic_rb | There are bugs, if you rely on zfs encryption with a keyfile youll hit one. If you rely on zvols youll hit another. Here be dragons | 11:21:12 |
|  smoothie_one joined the room. | 13:02:56 |
| 29 Mar 2026 |
|  arcayr joined the room. | 11:16:15 |
|  lillecarl changed their profile picture. | 20:55:44 |
| 1 Apr 2026 |
|  Benedikt Ritter (britter) joined the room. | 10:25:56 |
| Benedikt Ritter (britter) | Hey friends, I run a server on Hetzner that I installed with nixos-anywhere and disko. I'm no running low on disk space and want to mount an additional block volume. I wonder what the disko story for that is. As far as I understand the new volumne will be made available as a device with a filesystem pre-configured. Should I use the "classical" filesystems configuration to just add it as an additional FS or can I somehow put this into disko as well? | 10:29:36 |
|  theutz joined the room. | 10:42:55 |
 phaer | Formatting it would require the (risky/"experimental") incremental mode. But as it's already formatted, you can do either. Adding it to your disko config should add it to your fileSystems config implicitly. The only real advantage would be if you were to re-provision that host with a similar block volume. And at that point, why not start with a bigger disk to begin with? | 10:55:20 |
| Benedikt Ritter (britter) | Okay, so you're essentially saying "just put it into filesystems directly to keep things simple"? | 10:56:38 |
| phaer | I don't think there's a "right" answer here. I'd personally would do just fileSystems in that case, but it comes down to taste & future plans IMO | 10:57:47 |
| phaer | Depending on how you manage your hetzner resources, changes are that provisioning the volume isn't 100% declarative to begin with (which is most often is fine IMO) | 10:59:29 |
| phaer | * Depending on how you manage your hetzner resources, chances are that provisioning the volume isn't 100% declarative to begin with (which is most often is fine IMO) | 10:59:35 |
| Benedikt Ritter (britter) | We're provisioning it via terraform. But thats disconnected from everything we do in Nix. Its a different layer of our infrastructure setup. | 11:25:59 |
| Benedikt Ritter (britter) | But thanks giving your opinion! I think we'll go with filesystems. | 11:26:20 |
| matthewcroughan | If you had used systemd-repart from the beginning here, it has this functionality you want already baked in | 12:33:04 |
| matthewcroughan | in disko AFAIK this was planned but stalled | 12:33:14 |
| matthewcroughan | But systemd-repart already has what you're seeking Ibelieve | 12:33:36 |
| matthewcroughan | * But systemd-repart already has what you're seeking I believe | 12:33:43 |
| Benedikt Ritter (britter) | Thanks for the pointer, I'll have a look! | 15:48:26 |
