Andrew Bartlett reported the following unit test failures: I get it in the Catalyst Cloud when running make test on git master, building on Ubuntu 12.04. We only see it there, and not on 14.04. We are backed by Ceph RBD volumes, if that helps. [1(0)/3 at 0s] samba3.smb2.ioctl fs_specific(nt4_dc) UNEXPECTED(failure): samba3.smb2.ioctl fs_specific.sparse_punch(nt4_dc) REASON: Exception: Exception: ../source4/torture/smb2/ioctl.c:3308: far_count was 1 (0x1), expected 0 (0x0): unexpected response len UNEXPECTED(failure): samba3.smb2.ioctl fs_specific.sparse_qar_ob1(nt4_dc) REASON: Exception: Exception: ../source4/torture/smb2/ioctl.c:4477: far_rsp[0].len was 65537 (0x10001), expected 65536 (0x10000): unexpected far len envlog: SMBD LOG of: LOCALNT4DC2 [2(34)/3 at 11s, 1 errors] samba3.smb2.ioctl(nt4_dc) UNEXPECTED(failure): samba3.smb2.ioctl.sparse_punch(nt4_dc) REASON: Exception: Exception: ../source4/torture/smb2/ioctl.c:3308: far_count was 1 (0x1), expected 0 (0x0): unexpected response len UNEXPECTED(failure): samba3.smb2.ioctl.sparse_qar_ob1(nt4_dc) REASON: Exception: Exception: ../source4/torture/smb2/ioctl.c:4477: far_rsp[0].len was 65537 (0x10001), expected 65536 (0x10000): unexpected far len
@Andrew, can you confirm that you see "strange, this FS never deallocates zeroed ranges in sparse files" in your selftest subunit output?
on opensuse 13.1 I'm seeing: test: samba3.smb2.ioctl.sparse_qar_ob1(ad_dc) time: 2015-03-25 07:46:59.881086Z time: 2015-03-25 07:47:00.082730Z failure: samba3.smb2.ioctl.sparse_qar_ob1(ad_dc) [ Exception: Exception: ../source4/torture/smb2/ioctl.c:4500: status was NT_STATUS_OBJECT_NAME_COLLISION, expe cted NT_STATUS_OK: FSCTL_QUERY_ALLOCATED_RANGES req failed ]
Created attachment 10949 [details] subunit file from ubuntu 12.04 (In reply to David Disseldorp from comment #1) No, I don't see "strange, this FS never deallocates zeroed ranges in sparse files" in the subunit.
[revisiting some old tickets] @Andrew, do you still see this parse_qar_ob1() failure in your Catalyst Cloud environment?
no feedback, please reopen if this is still an issue with recent OS and samba releases