[Bug 265849] makefs regression test triggers ZFS assertion failure

From: <bugzilla-noreply_at_freebsd.org>
Date: Mon, 15 Aug 2022 01:36:00 UTC

            Bug ID: 265849
           Summary: makefs regression test triggers ZFS assertion failure
           Product: Base System
           Version: CURRENT
          Hardware: Any
                OS: Any
            Status: New
          Severity: Affects Some People
          Priority: ---
         Component: bin
          Assignee: bugs@FreeBSD.org
          Reporter: markj@FreeBSD.org

When running tests on the latest main, I get:

makefs_zfs_tests:autoexpand  ->  passed  [0.924s]                               
makefs_zfs_tests:basic  ->  passed  [0.199s]                                    
makefs_zfs_tests:dataset_removal  ->  passed  [0.147s]                          
makefs_zfs_tests:empty_dir  ->  passed  [0.117s]                                
makefs_zfs_tests:empty_fs  ->  passed  [0.113s]                                 
makefs_zfs_tests:file_sizes  ->  passed  [0.164s]                               
makefs_zfs_tests:hard_links  ->  passed  [0.176s]                               
makefs_zfs_tests:indirect_dnode_array  ->  passed  [0.260s]                     
makefs_zfs_tests:long_file_name  ->  passed  [0.272s]                           
makefs_zfs_tests:multi_dataset_1  ->  passed  [0.158s]                          
makefs_zfs_tests:multi_dataset_2  ->  passed  [0.121s]                          
makefs_zfs_tests:multi_dataset_3  ->  passed  [0.136s]                          
makefs_zfs_tests:multi_dataset_4  ->  passed  [0.159s]                          
makefs_zfs_tests:reproducible  ->  passed  [2.149s]                             
makefs_zfs_tests:root_props  ->  passed  [0.221s]                               
makefs_zfs_tests:snapshot  ->  panic: VERIFY(compressed >= 0 ||
ddp->dd_compressed_bytes >= -compressed) failed                               

cpuid = 1                                                                       
time = 1660527088                                                               
KDB: stack backtrace:                                                           
db_trace_self_wrapper() at db_trace_self_wrapper+0x2b/frame 0xfffffe0063bc99b0  
vpanic() at vpanic+0x151/frame 0xfffffe0063bc9a00                               
spl_panic() at spl_panic+0x3a/frame 0xfffffe0063bc9a60                          
dsl_dir_diduse_transfer_space() at dsl_dir_diduse_transfer_space+0x351/frame
dsl_dir_diduse_space() at dsl_dir_diduse_space+0x1b7/frame 0xfffffe0063bc9b70   
dsl_pool_sync() at dsl_pool_sync+0x464/frame 0xfffffe0063bc9bf0                 
spa_sync() at spa_sync+0xfe1/frame 0xfffffe0063bc9e20                           
txg_sync_thread() at txg_sync_thread+0x35b/frame 0xfffffe0063bc9ef0             
fork_exit() at fork_exit+0x80/frame 0xfffffe0063bc9f30                          
fork_trampoline() at fork_trampoline+0xe/frame 0xfffffe0063bc9f30               
--- trap 0xc, rip = 0x2b61e877bca, rsp = 0x2b6311c3f48, rbp = 0x2b6311c3f60 --- 
KDB: enter: panic                                                               
[ thread pid 3152 tid 102127 ]                                                  
Stopped at      kdb_enter+0x32: movq    $0,0x127a023(%rip)

This seems to have started after the latest OpenZFS import.

You are receiving this mail because:
You are the assignee for the bug.