I agree with Christof, don't do anything ZFS-specific here. But I was trying to encourage you to think more broadly about the situation, and hopefully find a compatible solution. Sector size is mostly about application compatibility. If you don't return anything, the app may break. For example, I bet SQL Server issues that info req, and SQL supports running over SMB. So that's one reason. Tom. Mar 30, 2022 7:37:20 PM Namjae Jeon <linkinjeon@xxxxxxxxxx>: > 2022-03-30 21:09 GMT+09:00, Tom Talpey <tom@xxxxxxxxxx>: >> On 3/30/2022 3:53 AM, Namjae Jeon wrote: >>> zfs block size is 128KB, and there is a problem when ksmbd responds to >>> this value as a sector size to the windows client. >>> This seems to judge as an error when a Windows client requests sector >>> size information from the server and receives a value larger than 4KB. >>> >>> If the logical/physical_block_size is obtained from the block layer in >>> ksmbd, You might think of this as a layer violation. >>> e.g. i_sb->s_bdev->bd_disk->queue->limits.logical_block_size. >>> >>> So I am confused as to how to fix this issue. and I'd like to hear >>> your thoughts on how to fix this correctly. >> This sounds like a problem common to any LVM or RAID layering. >> What does a Windows server return for a volume on a Storage Space? > I'm not sure if windows server & ZFS share is possible. samba & ZFS > respond 512Bytes sector size to client. I don't know why SMB client > need the disk sector size information from server... >> Look to that for guidance. > Okay:) > > Thanks! >> >> Tom. >>
