smbtorture: Add Shadow Copy related tests

- Some of the sparse file related tests are expected to fail due
  to limitations in CephFS, mark the same
- Make sure that ioctl tests are expected to strictly pass against
  CephFS and CephFS.vfs only.

Signed-off-by: Shwetha K Acharya <[email protected]>

testcases/smbtorture/selftest/flapping.glusterfs

@@ -10,3 +10,6 @@
 
 #https://github.com/gluster/samba-integration/issues/241
 ^samba3.smb2.deny.*
+
+# Strictly checking ioctl tests against cephFS only
+^samba3.smb2.ioctl.*

testcases/smbtorture/selftest/flapping.gpfs

@@ -5,3 +5,6 @@
 # Ignore due to lack of proper multichannel setup.
 ^samba3.smb2.session.bind2
 ^samba3.smb2.session.two_logoff
+
+# Strictly checking ioctl tests against cephFS only
+^samba3.smb2.ioctl.*

testcases/smbtorture/selftest/flapping.xfs

@@ -8,3 +8,6 @@
 
 # https://github.com/samba-in-kubernetes/sit-environment/pull/109
 samba3.smb2.session.reauth4
+
+# Strictly checking ioctl tests against cephFS only
+^samba3.smb2.ioctl.*

testcases/smbtorture/selftest/knownfail.d/sparse_files

@@ -0,0 +1,10 @@
+# CephFS does not explicitly track which parts of a file are allocated/written with sparse files,
+# the st_blocks field is always populated by the file size divided by the block size.
+# This will cause tools like du(1) to overestimate consumed space.
+# (The recursive size field, maintained by CephFS, also includes file “holes” in its count.)
+
+# Refer: https://github.com/samba-in-kubernetes/sit-test-cases/issues/86
+^samba3.smb2.ioctl.sparse_punch
+^samba3.smb2.ioctl.sparse_qar_ob1
+^samba3.smb2.ioctl.sparse_punch_invalid
+^samba3.smb2.ioctl.copy-chunk streams

testcases/smbtorture/smbtorture-tests-info.yml

@@ -31,3 +31,4 @@
 - smb2.bench
 - smb2.winattr2
 - smb2.charset
+- smb2.ioctl