From: Tom Talpey <tom@talpey.com>
To: Namjae Jeon <linkinjeon@kernel.org>,
Christoph Hellwig <hch@lst.de>,
Christoph Hellwig <hch@infradead.org>
Cc: Steve French <smfrench@gmail.com>,
CIFS <linux-cifs@vger.kernel.org>,
Hyeoncheol Lee <hyc.lee@gmail.com>,
Sergey Senozhatsky <senozhatsky@chromium.org>
Subject: Re: Regarding to how ksmbd handles sector size request from windows cllient
Date: Wed, 30 Mar 2022 08:09:07 -0400 [thread overview]
Message-ID: <63afe0cd-7151-45e6-a7c2-2eb9212d721b@talpey.com> (raw)
In-Reply-To: <CAKYAXd_XMW1-VSLwB=k3ypqgqjsux5OFNnr=Ri3B+-8w4aNHjw@mail.gmail.com>
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?
Look to that for guidance.
Tom.
next prev parent reply other threads:[~2022-03-30 12:18 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-30 7:53 Regarding to how ksmbd handles sector size request from windows cllient Namjae Jeon
2022-03-30 9:05 ` Christoph Hellwig
2022-03-30 13:46 ` Namjae Jeon
2022-03-30 12:09 ` Tom Talpey [this message]
2022-03-30 23:32 ` Namjae Jeon
2022-03-30 23:44 ` Tom Talpey
2022-03-31 4:06 ` Christoph Hellwig
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=63afe0cd-7151-45e6-a7c2-2eb9212d721b@talpey.com \
--to=tom@talpey.com \
--cc=hch@infradead.org \
--cc=hch@lst.de \
--cc=hyc.lee@gmail.com \
--cc=linkinjeon@kernel.org \
--cc=linux-cifs@vger.kernel.org \
--cc=senozhatsky@chromium.org \
--cc=smfrench@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox