Skip to content
View in the app

A better way to browse. Learn more.

Unraid

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

Slow parity check after adding zfs drive

Featured Replies

I reformatted my system cache drive to zfs, and added a disk to the array for zfs snapshot replication.

 

Most of my array drives (including the new zfs drive) are 4TB, and typical read speeds for parity check start around 140-150MB/s and head down to ~80MB/s toward the end of the 4TB space on the array

 

After backing up my cache drive to the array, restoring it back to the cache, and adding the new drive, I decided to kick off a parity check  (there were some issues with mover hanging on the docker folders of the cache drive)

 

Read speeds around the 1TB mark for the parity check are already down to ~33-40MB/s

 

What would cause such a slow parity check after adding a new drive?  Does having a mix of xfs and zfs drives affect parity check performance?

Edited by veri745
typos

  • Community Expert
2 hours ago, veri745 said:

What would cause such a slow parity check after adding a new drive?  Does having a mix of xfs and zfs drives affect parity check performance?

In theory it should not make any difference, but is ZFS housekeeping accesses drives then that could slow down the parity check.

  • Author

Whatever it was causing the slow parity check did not persist the second night of the parity check (I have it set to pause during the day and resume at night), so I didn't get a chance to grab the diagnostics in the midst of the issue.

 

Going to chalk it up to one of my docker containers doing some sort of media scan, since I had to blow away the docker system directory and re-create all the containers (although my appdata was all intact after the cache drive migration).  I dunno.

Edited by veri745

  • 3 weeks later...

I transitioned all array disks to ZFS and am seeing parity check crawling along at 28MB/sec. Previously with XFS it was over 100 MB/sec with 10TB parity.

 

Stopped docker services - no change to parity speed.
Started docker services - docker tab showed as not running, no start stop would make a difference.
Reboot
Partity sync restarted and back to over 100 MB/sec.
Docker containers all running fine.

 

strange.

 

 

diagnostics-20231001-0055.zip

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.