!oNSIfazDqEcwhcOjSL:matrix.org

disko

366 Members
disko - declarative disk partitioning - https://github.com/nix-community/disko93 Servers

Load older messages


SenderMessageTime
14 Dec 2023
@matthewcroughan:defenestrate.itmatthewcroughan Ah yeah in that case it looks like it builds the kernel 6.5, presumably with bcachefs set to y instead of modular 10:05:58
@matthewcroughan:defenestrate.itmatthewcroughanah, but that fails to patch on my nixpkgs, darnit10:06:16
@matthewcroughan:defenestrate.itmatthewcroughan * ah, but that fails to patch on my nixpkgs, which is latest nixos-unstable darnit10:06:21
@matthewcroughan:defenestrate.itmatthewcroughanbcachefs creation works, just not mounting of it 10:13:01
@matthewcroughan:defenestrate.itmatthewcroughan
piygg-disko-images> mounting version 1.3: rebalance_work
piygg-disko-images> initializing new filesystem
piygg-disko-images> going read-write
piygg-disko-images> initializing freespace
piygg-disko-images> + set -efux
piygg-disko-images> + device=/dev/vda
piygg-disko-images> + imageSize=3G
piygg-disko-images> + name=disk1
piygg-disko-images> + type=disk
piygg-disko-images> + device=/dev/vda
piygg-disko-images> + type=gpt
piygg-disko-images> + device=/dev/vda
piygg-disko-images> + imageSize=3G
piygg-disko-images> + name=disk1
piygg-disko-images> + type=disk
piygg-disko-images> + device=/dev/vda
piygg-disko-images> + type=gpt
piygg-disko-images> + device=/dev/disk/by-partlabel/disk-disk1-root
piygg-disko-images> + extraArgs=()
piygg-disko-images> + declare -a extraArgs
piygg-disko-images> + format=bcachefs
piygg-disko-images> + mountOptions=('defaults')
piygg-disko-images> + declare -a mountOptions
piygg-disko-images> + mountpoint=/
piygg-disko-images> + type=filesystem
piygg-disko-images> + findmnt /dev/disk/by-partlabel/disk-disk1-root /mnt/
piygg-disko-images> + mount /dev/disk/by-partlabel/disk-disk1-root /mnt/ -t bcachefs -o defaults -o X-mount.mkdir
piygg-disko-images> mount: /mnt/: unknown filesystem type 'bcachefs'.
piygg-disko-images>        dmesg(1) may have more information after failed mount system call.
piygg-disko-images> + rm -rf /tmp/tmp.vfRvJa95kq
piygg-disko-images> [    5.642972] reboot: Power down
10:13:15
@matthewcroughan:defenestrate.itmatthewcroughan
piygg-disko-images> + uname -a
piygg-disko-images> Linux (none) 6.1.67 #1-NixOS SMP Mon Dec 11 09:41:01 UTC 2023 aarch64 GNU/Linux
10:14:47
@matthewcroughan:defenestrate.itmatthewcroughanWhy is the kernel version in the make-disk-image not the same as mine?10:14:59
@matthewcroughan:defenestrate.itmatthewcroughanis extendModules working correctly?10:15:08
@matthewcroughan:defenestrate.itmatthewcroughanvmTools!10:36:18
@matthewcroughan:defenestrate.itmatthewcroughan Figured it out, making a PR now, but it does increase the necessary memSize 10:59:58
@matthewcroughan:defenestrate.itmatthewcroughanmaybe the VM should have zram :D11:00:24
@matthewcroughan:defenestrate.itmatthewcroughanIt is quite unfortunate, but there is no way to get a list of kernel module names for the filesystems involved in a nixos configuration 11:02:00
@matthewcroughan:defenestrate.itmatthewcroughan
nixosConfigurations.pi3.config.boot.supportedFilesystems
[ "bcachefs" "bcachefs" "vfat" ]
11:02:21
@matthewcroughan:defenestrate.itmatthewcroughanThis is not a module list, even though it looks like one 11:02:27
@matthewcroughan:defenestrate.itmatthewcroughanhttps://github.com/NixOS/nixpkgs/tree/master/nixos/modules/tasks/filesystems11:02:47
@matthewcroughan:defenestrate.itmatthewcroughan if the string "bcachefs" is found in the supportedFilesystems, it will add boot.initrd.availableKernelModules = [ "bcachefs" "sha256" "chacha20" "poly1305" ]; to the nixosConfiguration 11:03:24
@matthewcroughan:defenestrate.itmatthewcroughanmaybe this is only really a problem for zfs, actually11:04:59
@matthewcroughan:defenestrate.itmatthewcroughan * maybe this is only really a problem for zfs, actually, since it needs to be in the modulesTree11:05:09
@matthewcroughan:defenestrate.itmatthewcroughan * maybe this is only really a problem for zfs, actually, since it needs to be in the rootModules11:05:17
@matthewcroughan:defenestrate.itmatthewcroughan * maybe this is only really a problem for zfs, actually, since it needs to be in the rootModules and can't be dynamically loaded11:05:28
@matthewcroughan:defenestrate.itmatthewcroughanzram inside of vm tests might be a big boost for all performance actually 11:09:59
@matthewcroughan:defenestrate.itmatthewcroughanI wonder why we don't to that11:10:02
@matthewcroughan:defenestrate.itmatthewcroughan * I wonder why we don't do that to the nodes by default 11:10:08
@matthewcroughan:defenestrate.itmatthewcroughan lassulus: I enabled zram inside the disk builder VM, and it allowed me to install a closure with 1024M that I could only install with 2048M otherwise 11:22:34
@matthewcroughan:defenestrate.itmatthewcroughan * lassulus: I enabled zram inside the disk builder VM, and it allowed me to install a closure with 1024M that I could only install with 3GB otherwise 11:22:40
@lassulus:lassul.uslassulusuh weird11:23:16
@lassulus:lassul.uslassulusbut ok11:23:18
@matthewcroughan:defenestrate.itmatthewcroughan @ 12:09:31
@matthewcroughan:defenestrate.itmatthewcroughan * https://github.com/nix-community/disko/pull/46712:09:33
@matthewcroughan:defenestrate.itmatthewcroughan I'm thinking something like disko.imageBuilder as an option namespace might begin to make sense, but not for this PR 12:10:22

Show newer messages


Back to Room ListRoom Version: 10