Search results

Restart not needed

Only fix for me was disabling direct on zfs, not had a problem since.

I’m 4+ days in and no more issues here so far.

I have disabled direct io, and it looks like the DIO isn't increasing now: zfs set direct=disabled I will monitor it

Thanks :)

@Impact Apologies if this is not the correct process, I was trying to separate things. Should I delete it/and or add to the existing?

I have disabled direct write and cleared the DIO counters, see what happens.

pool: data state: ONLINE scan: scrub repaired 0B in 00:05:25 with 0 errors on Thu Jan 22 16:26:36 2026 config: NAME STATE READ WRITE CKSUM DIO data ONLINE 0 0 0...

Hi all, Any advice on this? Since moving to 9, currently running 9.1.4, we are experiencing Status: io-error on VM's on ZFS. Pools have been scrubbed, disks pass smart and 0/1 percent wear out, plenty of space and RAM, and it happens on multiple servers randomly. We have to stop VM and...

Sorry @Impact, will use code blocks going forward: All look good, scrub ran and no errors: pool: DATA state: ONLINE scan: scrub repaired 0B in 00:07:20 with 0 errors on Thu Jan 22 16:27:43 2026 config: NAME STATE READ WRITE...

Same here, if it helps here are ours: NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS FSTYPE LABEL MODEL nvme1n1 259:0 0 894.3G 0 disk SAMSUNG MZQL2960HCJR-00A07 |-nvme1n1p1 259:5 0 1007K 0 part |-nvme1n1p2 259:6 0...

I have put the subscription back for now, was just doing it early, I will push for the budget

That didn't work, this is the what I see:

I see that when I check for updates in the gui, and I just did an update from the gui, I will try a dist-upgrade now, thanks for the link.

Just moved from enterprise repo to community repo and got this error: "unknown variant `Suspended`, expected one of `new`, `notfound`, `active`, `invalid`, `expired` at line 1 column 159 (500)" Not the end of the world. its all working but bit wierd. Budget cuts :(

I was on 2.2.5, I will try 2.2.5-1 today if I get a minute :)

upgraded to 2.2.5 and got a kernel panic on boot after not finding root to mount, rebooted previous and all good.

I have moved the servers to backup at different intervals to each other and I have not had a failure in 48 hours, 2 hours schedule used.

Are you using httpS ?

And the failure happened :( That will teach me to be an optimist! Back to nursing the backups I guess.