Debian 13 "Trixie" Hits August 19th

Meanwhile I’m over here like…

> doc@gigabizzle:~$ uname -r 
> 6.15.6-1-liquorix-amd64
> doc@gigabizzle:~$ sudo zfs --version
> zfs-2.3.99-461_gd6dcae316
> zfs-kmod-2.3.99-461_gd6dcae316
> doc@gigabizzle:~$
2 Likes

How could you think that a liquorix kernel and zfs is a desirable state to be in?
My impression is that they are hi-tech fringe experimental stuff.
Correct me if you have a different view .

1 Like

The only issue I’m having here is the fact that I had to compile the ZFS kernel because of Debian’s “issues” with ZFS, so it’s kind of a bleeding edge version. Doesn’t give me the warm fuzzies, lets put it that way.

Not ideal, but until I can get my pool backed up in order to fix it …it is what it is. I’m not running ZFS on the root drive either, just on the storage drive.

Liquorix is a custom kernel build, mostly based on zen kernel patches, aimed at responsiveness and desktop interactivity. It’s often used by low-latency audio folks, gamers, or just people who want snappier UI behavior. It’s not experimental in the sense of “held together by duct tape,” but it does include more aggressive scheduler tweaks and features that haven’t hit mainline yet.

So basically..
I’m on Debian, so using zfs-dkms.
The issue isn’t Liquorix. It’s Debian stable pushing a newer ZFS version that:
Requires newer kernels than Debian ships by default.
Might mismatch the DKMS build during a kernel update, but that’s a ZFS-on-Linux packaging issue, not Liquorix’s fault.
Issues:
DKMS needing to be rebuilt whenever I update kernels — but that happens regardless of whether you’re on Liquorix, mainline, or a kernel you rolled yourself.

1 Like

A reliable filesystem is rather basic. You know what you are doing and you will make it work… maybe Debian testing and get a newer kernel.
Is this a server? I thought servers tended to be old stable stuff.?
I hate the thought of a filesystem misbehaving on me.

There is some sort of move towards shifting filesystems out of the kernel into user space (like FUSE). I saw some discussions in the NetBSD world.

2 Likes

In case anyone is interested, these are the release notes for “Trixie” aka Debian 13.
My own personal preference using Debian 12 as my daily driver is to hold fire until at the very least the first point release and probably later but will more than likely do a vanilla install to a new PC

1 Like

I have Debian 11. I am not going to try an upgrade. I shall wait, like you suggest, then do a fresh install on a new partition beside the Debian 11.
That gives me opportunity to transfer software and deal with any issues.

3 Likes

In that case, you may also find this resource helpful

3 Likes

nah this is my workstation. Nowadays my servers tend to be either HardenedBSD or FreeBSD.

1 Like

I dont think I would choose ZFS for a workstation… not a multiboot one anyway. It tends to want to ‘own’ the disks.

2 Likes

i dont have zfs on the boot disks, I just have ZFS on a third storage disk, shared between the two OSes.

1 Like

That makes sense, especially if you have lots of data and it is dynamic.
I have a shared data disk like that, but it is ext4. I rsync it to another disk nightly… sort of like a raid hand driven.

3 Likes

yeah. I got into ZFS via my servers, which have more of a use case for it since you have RAID Z1 Z2 … but it’s also good on single drives as well if for nothing else than the dataset/snapshot features.

But yeah, usually I have ZFS spread across 4 drives in a RAID 10 like setup. lol

2 Likes