ZFS freezes userspace on write operations
Posted: Sat Sep 30, 2023 4:11 pm
Hello there!
I'm running into an issue with my ZFS pool (O3X 2.1.6) on Mojave 10.14.6 (18G9323).
Here is my setup:
I recently replaces all of these drives and expanded the pool and ever since I expanded the pool, large write operations make the user space completely freeze. The operations successfully complete and I get no panics, but I can't interact with the OS using the keyboard or mouse and in-progress operations on the screen freeze. I'm pasting in my arc-stat log where you can see that at one point, it skips a few minutes.
I replaced the disks one-at-a-time, once per week over the course of month and did a scrub before I expanded the pool. Everything was functioning normally right before I expanded the pool but afterwards, I started having this behavior.
I've always had this experience whenever I've used ZFS in the past, but on laptops, without a lot of memory to go around, but now I have 128 GB so I figured that should be enough.
Also, there seems to be a disparity between the 16.4T in `zpool` and the maybe 11T available in `zfs`.
In any case, I don't know if there is a tunable or if this is a known issue and I just skipped a step somewhere.
Thank you!
I'm running into an issue with my ZFS pool (O3X 2.1.6) on Mojave 10.14.6 (18G9323).
Here is my setup:
- Code: Select all
NAME STATE READ WRITE CKSUM
ranvol ONLINE 0 0 0
raidz1-0 ONLINE 0 0 0
media-CB90139A-5957-11EC-8988-3C07547EECD7 ONLINE 0 0 0
media-47247846-0AD3-4348-8B7E-4B50DA8341B5 ONLINE 0 0 0
media-6754CB3A-ADE7-BD4E-A34F-FBEBB3166868 ONLINE 0 0 0
I recently replaces all of these drives and expanded the pool and ever since I expanded the pool, large write operations make the user space completely freeze. The operations successfully complete and I get no panics, but I can't interact with the OS using the keyboard or mouse and in-progress operations on the screen freeze. I'm pasting in my arc-stat log where you can see that at one point, it skips a few minutes.
I replaced the disks one-at-a-time, once per week over the course of month and did a scrub before I expanded the pool. Everything was functioning normally right before I expanded the pool but afterwards, I started having this behavior.
I've always had this experience whenever I've used ZFS in the past, but on laptops, without a lot of memory to go around, but now I have 128 GB so I figured that should be enough.
- Code: Select all
ranvel@grey-lodge %> zfs list ~
NAME USED AVAIL REFER MOUNTPOINT
ranvol 4.51T 6.27T 128K none
ranvol/data 2.33T 6.27T 2.33T /var/data/rdata
ranvol/media 2.18T 6.27T 2.18T /var/data/media
ranvel@grey-lodge %> zpool list ~
NAME SIZE ALLOC FREE CKPOINT EXPANDSZ FRAG CAP DEDUP HEALTH ALTROOT
ranvol 16.4T 6.76T 9.59T - - 1% 41% 1.00x ONLINE -
Also, there seems to be a disparity between the 16.4T in `zpool` and the maybe 11T available in `zfs`.
In any case, I don't know if there is a tunable or if this is a known issue and I just skipped a step somewhere.
Thank you!