Jeremy Bryan Smith
Jeremy Bryan Smith
I noticed that in the NOOP send, there's the line: ``` snapshot_limit: 18446744073709551614 ``` The source dataset has that value: ``` # zfs get snapshot_limit -p dpool/backups/xyz/jbsnet/latitude/CURRENT/rpool/scratch NAME PROPERTY VALUE...
Ahh, what the heck: Here's the only dbgmsg output from the recv command: ``` 1597125475 spa_history.c:309:spa_history_log_sync(): txg 2828496 resume receive dpool/backups/xyz/jbsnet/latitude/CURRENT/rpool/scratch/%recv (id 530023) 1597125475 spa_history.c:309:spa_history_log_sync(): txg 2828497 finish receiving dpool/backups/xyz/jbsnet/latitude/CURRENT/rpool/scratch/%recv...
This also crashes when sending to an entirely new dataset on a different pool, different server (5.4.0-40-generic / 0.8.3-1ubuntu12), even after reducing the snapshot_limit to 9999999 (but this time it...
Hmm. So either the assertion fails when `dsl_fs_ss_count_adjust()` was called with dataset `%recv` and `prop` being `DD_FIELD_SNAPSHOT_COUNT` or with dataset being something else, right? Could it be that the snapshot...
I ran into another problem (#10787) that's kept me from further troubleshooting this. Also, I couldn't find how to print the stack trace and those vars, can anyone help with...
I was hoping this would have been resolved by some changes in the 2.0 release, but I am still encountering what appears to be the same PANIC when attempting to...
Dataset details: ``` root@myhost-mirror ~ # cat /sys/module/zfs/parameters/zfs_dbgmsg_enable 1 root@myhost-mirror ~ # zfs get all data/myhost-main/data/backupdata/veeam/repos/repo_01_old NAME PROPERTY VALUE SOURCE data/myhost-main/data/backupdata/veeam/repos/repo_01_old type volume - data/myhost-main/data/backupdata/veeam/repos/repo_01_old creation Mon Oct 5 22:29...
I also tried aborting the send: ``` root@myhost-mirror ~ # zfs recv -A data/myhost-main/data/backupdata/veeam/repos/repo_01_old Message from syslogd@myhost-mirror at Jan 26 16:01:26 ... kernel:[ 534.938981] VERIFY3(count >= 0) failed (-1 >=...
> The originally-reported issue should have been resolved by #10791, which is fixed in 2.0. It's possible that if your filesystem (data/myhost-main/data/backupdata/veeam/repos/repo_01_old) was created on an earlier release, you could...
I have yet to be able to try that as the system encountering this problem is in production and it's critical that it stay up and running. But I have...