From: "Martin K. Petersen" <martin.petersen@oracle.com>
To: Randy Dunlap <rdunlap@infradead.org>
Cc: JPT <j-p-t@gmx.net>,
linux-kernel@vger.kernel.org, linux-block@vger.kernel.org
Subject: Re: blocksize 4096 even for floppy and CDROM?
Date: Tue, 22 Feb 2022 23:00:07 -0500 [thread overview]
Message-ID: <yq1fsoab5n0.fsf@ca-mkp.ca.oracle.com> (raw)
In-Reply-To: <f94fc06e-c0ff-103b-789a-87af52c53e11@infradead.org> (Randy Dunlap's message of "Tue, 22 Feb 2022 15:24:13 -0800")
Randy,
>> I wonder why safecopy always says
>> Reported hw blocksize: 4096
>> Reported low level blocksize: 4096
>>
>> even if the medium is floppy (512) or CDROM (2048)
>>
>> is this a kernel issue always assuming min 4k block size?
Not sure how safecopy queries the block size. The kernel supports
devices with 512, 1024, 2048, and 4096-byte logical blocks.
--
Martin K. Petersen Oracle Linux Engineering
prev parent reply other threads:[~2022-02-23 4:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-22 20:08 blocksize 4096 even for floppy and CDROM? JPT
2022-02-22 23:24 ` Randy Dunlap
2022-02-23 4:00 ` Martin K. Petersen [this message]
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=yq1fsoab5n0.fsf@ca-mkp.ca.oracle.com \
--to=martin.petersen@oracle.com \
--cc=j-p-t@gmx.net \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rdunlap@infradead.org \
/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