Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Failed tests in ioctl.c #86

Closed
Shwetha-Acharya opened this issue Jul 2, 2024 · 2 comments
Closed

Failed tests in ioctl.c #86

Shwetha-Acharya opened this issue Jul 2, 2024 · 2 comments
Assignees

Comments

@Shwetha-Acharya
Copy link
Collaborator

Shwetha-Acharya commented Jul 2, 2024

This test is enabled to verify the shadow copy related tests.
Shadow copy related tests are passing however, 4 tests are showing unexpected behaviour in cephFS.

Need to check if the failed tests are of any important consequence or they are expected to be ignored.

Successful Tests:

shadow_copy
req_resume_key
req_two_resume_keys
copy_chunk_simple
copy_chunk_multi
copy_chunk_tiny
copy_chunk_overwrite
copy_chunk_append
copy_chunk_limits
copy_chunk_src_lock
copy_chunk_dest_lock
copy_chunk_bad_key
copy_chunk_bug15644
copy_chunk_src_is_dest
copy_chunk_src_is_dest_overlap
copy_chunk_bad_access
copy_chunk_write_access
copy_chunk_src_exceed
copy_chunk_src_exceed_multi
copy_chunk_sparse_dest
copy_chunk_max_output_sz
copy_chunk_zero_length
copy_chunk_across_shares
copy_chunk_across_shares2
copy_chunk_across_shares3
compress_notsup_get
compress_notsup_set
network_interface_info
sparse_file_flag
sparse_file_attr
sparse_dir_flag
sparse_set_nobuf
sparse_set_oversize
sparse_qar
sparse_qar_malformed
sparse_hole_dealloc
sparse_perms
sparse_lock
sparse_qar_multi
sparse_qar_overflow

Failures :
copy-chunk streams
sparse_punch
sparse_qar_ob1

Unexpected Success (uxsuccess):
sparse_punch_invalid

Skipped Tests (skip) as dependencies unsupported by the machine or the storage:

compress_file_flag
compress_dir_inherit
compress_invalid_format
compress_invalid_buf
compress_query_file_attr
compress_create_with_attr
compress_inherit_disable
compress_set_file_attr
compress_perms
sparse_compressed
sparse_copy_chunk
trim_simple
dup_extents_simple
dup_extents_len_beyond_dest
dup_extents_len_beyond_src
dup_extents_len_zero
dup_extents_sparse_src
dup_extents_sparse_dest
dup_extents_sparse_both

CI runs of the same can be obsereved here: #82

@Shwetha-Acharya
Copy link
Collaborator Author

Additional Info:

failure: samba3.smb2.ioctl.sparse_punch [
Exception: ../../source4/torture/smb2/ioctl.c:4138: far_count was 1 (0x1), expected 0 (0x0): unexpected response len
time: 2024-07-02 15:03:33.009611Z
]

failure: samba3.smb2.ioctl.copy-chunk streams [
Exception: ../../source4/torture/smb2/ioctl.c:2041: Expression `ok == 1' failed: copy_one_stream failed

]
failure: samba3.smb2.ioctl.sparse_qar_ob1 [
Exception: ../../source4/torture/smb2/ioctl.c:5308: far_rsp[0].len was 65537 (0x10001), expected 65536 (0x10000): unexpected far len

@Shwetha-Acharya Shwetha-Acharya self-assigned this Aug 6, 2024
@Shwetha-Acharya
Copy link
Collaborator Author

Shwetha-Acharya commented Aug 6, 2024

These tests are failing with cephFS because, CephFS does not accurately support sparse files:

Refer: https://docs.ceph.com/en/latest/cephfs/posix/#differences-from-posix

Sparse files propagate incorrectly to the stat(2) st_blocks field. Because CephFS does not explicitly track which parts of a file are allocated/written, 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.)

Following warning during the test run also signifies the imcompatibilty with File System and the expected behavior with the sparse files:

WARNING!: ../../source4/torture/smb2/ioctl.c:1929: Expression `ok == 1' failed: setup copy chunk error

F...sssssssss..........Fstrange, this FS never deallocateszeroed ranges in sparse files
.ss...Fthis FS doesn't deallocate 64Kzeroed ranges in sparse files
..sector size info: lb/s=512, pb/sA=512, pb/sP=512, fse/sA=512, flags=0x3, bosa=0, bopa=0
sssssssssssssss..ss`

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant