Bug #6036

Updated by Toomas Soome 10 months ago

One of the zfs-tests (functional/inuse/inuse_003_pos.ksh) uses ufsrestore which happens to segfault.    I don't think it is an issue with the test, but rather ufsrestore has a bug of some sort.    Since some folks have run into it independently: 

 > $c 
 lookupparent+0x7a(8064b25, 2c, 66664, fef6e000, fef6e824, 80ef600) 
 addentry+0x8d(8064b25, 2, 2, 0, 10001, fef6e000) 
 initsymtable+0xa1(0, 8045c00, 80460a8, 8058b0e, ffff, 0) 
 main+0x933(804609c, fef786e8, 80460d8, 8054b5b, 4, 80460e4) 
 _start+0x83(4, 804658c, 80465a1, 80465a5, 8064b25, 0) 
 > ::status 
 debugging core file of ufsrestore (32-bit) from ganymede 
 file: /usr/lib/fs/ufs/ufsrestore 
 initial argv: /usr/sbin/ufsrestore rbf 512 /dev/rdsk/c1t5000C500563ED21Fd0s0 
 threading model: native threads 
 status: process terminated by SIGSEGV (Segmentation Fault), addr=8065dca 
 > 8064b25::dump 
            0 1 2 3    4\/ 6 7    8 9 a b    c d e f    01234v6789abcdef 
 8064b20:    2e2f002e 2e2e0063 6f727275 70746564    ./.....corrupted 
 > 8064b25/s 
 0x8064b25:        . 

 Testing done: ufsrestore appears to list (t) or restore (x) files.