Skip to content

Conversation

@zowoq
Copy link
Contributor

@zowoq zowoq commented May 2, 2024

No description provided.

@Mic92
Copy link
Member

Mic92 commented Jun 8, 2024

Should I test installing this on build01?

@zowoq
Copy link
Contributor Author

zowoq commented Jun 8, 2024

Should I test installing this on build01?

No, I'll do it myself.

I would appreciate a response to #1207 (comment).

@Mic92
Copy link
Member

Mic92 commented Jun 10, 2024

Should I test installing this on build01?

No, I'll do it myself.

I would appreciate a response to #1207 (comment).

Without trying it myself, I can't tell.

@zowoq zowoq force-pushed the zfs-swap branch 2 times, most recently from a2310a7 to 32f118f Compare July 5, 2024 06:14
@zowoq
Copy link
Contributor Author

zowoq commented Jul 5, 2024

@Mic92 I tried this on build01. Installed, booted, another zfs import error. Is there some sort of weird systemd-boot / zfs problem?

@Mic92
Copy link
Member

Mic92 commented Jul 5, 2024

@Mic92 I tried this on build01. Installed, booted, another zfs import error. Is there some sort of weird systemd-boot / zfs problem?

No. I use systemd-boot in many places. Only thing I can think of is that the pool is not exported correctly. In nixos-anywhere we do this: https://github.com/nix-community/nixos-anywhere/blob/f99d120b3788a286989db4e592a698f5d310d2f6/src/nixos-anywhere.sh#L516

@zowoq
Copy link
Contributor Author

zowoq commented Jul 6, 2024

I disabled uefi on build03 so now it is the same as 01 and 02.

mountpoint = "/";
options.mountpoint = "legacy";
};
writeback = {
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

cannot create 'zroot/writeback': out of space

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

For a new installation or incremental one?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Seems to be a problem with the size of the disk, test works if it is 1G or created as a sparse disk. I've seen some comments that sparse can't be problematic so not going to use it.

# Sometimes fails after the first try, with duplicate pool name errors
boot.initrd.systemd.services.zfs-import-zroot.serviceConfig.Restart = "on-failure";

zramSwap.writebackDevice = "/dev/zvol/zroot/writeback";
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Doesn't this suffer from the same issue that we also have with swap files on zfs filesystems? Also now that zfs has proper direct I/O maybe this is not an issue? https://github.com/openzfs/zfs/releases/tag/zfs-2.3.0-rc1

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

zvol is used as an example in the zram-generator docs so I'm assuming that it works.

https://github.com/systemd/zram-generator/blob/766bfb0d297fe083cc29ab1886d8feff24f2ee58/man/zram-generator.conf.md?plain=1#L85

@zowoq
Copy link
Contributor Author

zowoq commented Jan 29, 2025

Going to test this on build01, created the volume manually and added the writeback device in #1689.

@zowoq
Copy link
Contributor Author

zowoq commented Feb 3, 2025

Going to test this on build01, created the volume manually and added the writeback device in #1689.

Seems that doesn't do anything, it doesn't have any defaults, users need to write their own triggers and set timers for the triggers. Reverted in #1696.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants