From: Eric Sandeen <sandeen@sandeen.net>
To: Hyunchul Lee <hyc.lee@gmail.com>
Cc: Namjae Jeon <namjae.jeon@samsung.com>,
Namjae Jeon <linkinjeon@kernel.org>,
linux-fsdevel <linux-fsdevel@vger.kernel.org>,
Pavel Reichl <preichl@redhat.com>,
chritophe.vu-brugier@seagate.com
Subject: Re: problem with exfat on 4k logical sector devices
Date: Wed, 12 May 2021 12:56:57 -0500 [thread overview]
Message-ID: <39726442-efd9-2c7a-c52e-04b1d7f14985@sandeen.net> (raw)
In-Reply-To: <35b5967f-dc19-f77f-f7d1-bf1d6e2b73e8@sandeen.net>
On 5/12/21 11:44 AM, Eric Sandeen wrote:
> I also wonder about:
>
> bd->num_sectors = blk_dev_size / DEFAULT_SECTOR_SIZE;
> bd->num_clusters = blk_dev_size / ui->cluster_size;
>
> is it really correct that this should always be in terms of 512-byte sectors?
It does look like this causes problems as well:
# dump/dump.exfat /root/test.img
exfatprogs version : 1.1.1
-------------- Dump Boot sector region --------------
Volume Length(sectors): 65536 <<<<<<
FAT Offset(sector offset): 256
FAT Length(sectors): 64
Cluster Heap Offset (sector offset): 512
Cluster Count: 65024
Root Cluster (cluster offset): 6
Volume Serial: 0x1234
Sector Size Bits: 12 <<<<<<<
Sector per Cluster bits: 0
...
# tune/tune.exfat -v /root/test.img
exfatprogs version : 1.1.1
[exfat_get_blk_dev_info: 202] Block device name : /root/test.img
[exfat_get_blk_dev_info: 203] Block device offset : 0
[exfat_get_blk_dev_info: 204] Block device size : 268435456
[exfat_get_blk_dev_info: 205] Block sector size : 512 <<<<<<<
[exfat_get_blk_dev_info: 206] Number of the sectors : 524288 <<<<<<<
[exfat_get_blk_dev_info: 208] Number of the clusters : 65536
next prev parent reply other threads:[~2021-05-12 19:44 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-11 17:28 problem with exfat on 4k logical sector devices Eric Sandeen
2021-05-11 21:21 ` Namjae Jeon
2021-05-11 23:33 ` Eric Sandeen
2021-05-11 23:53 ` Namjae Jeon
2021-05-11 23:57 ` Eric Sandeen
2021-05-12 14:09 ` Hyunchul Lee
2021-05-12 16:44 ` Eric Sandeen
2021-05-12 17:56 ` Eric Sandeen [this message]
2021-05-13 6:53 ` Namjae Jeon
2021-05-13 6:52 ` Namjae Jeon
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=39726442-efd9-2c7a-c52e-04b1d7f14985@sandeen.net \
--to=sandeen@sandeen.net \
--cc=chritophe.vu-brugier@seagate.com \
--cc=hyc.lee@gmail.com \
--cc=linkinjeon@kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=namjae.jeon@samsung.com \
--cc=preichl@redhat.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.