linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Pali Rohár" <pali.rohar@gmail.com>
To: OGAWA Hirofumi <hirofumi@mail.parknet.co.jp>
Cc: linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org
Subject: Re: [PATCH] fat: Relax checks for sector size and media type
Date: Wed, 12 Sep 2018 12:17:50 +0200	[thread overview]
Message-ID: <20180912101750.6slpi3puoww72xsj@pali> (raw)
In-Reply-To: <87zhwzro1o.fsf@mail.parknet.co.jp>

On Monday 03 September 2018 17:19:15 OGAWA Hirofumi wrote:
> Pali Rohár <pali.rohar@gmail.com> writes:
> 
> >> That source seems to check power_of_2(size) and 128 <= size <=
> >> 4096. Rather why do you want to support larger than 4096? Or I'm missing
> >> something?
> >
> > I looked into (Linux) mkfs.fat and it supports formatting disk also with
> > sector size > 4096. Therefore I thought it may be good idea for ability
> > to mount and use it (on Linux).
> >
> > I could check what other operating system would do with FAT sector size
> > larger then 4096.
> 
> If there is real user to use that, I'm ok though (of course, need
> serious tests). However, FAT would be for exchange data with other
> devices, and there is "cluster per sector", and spec recommends sector
> size == device sector size. So I suspect this format is not useful.

I looked into OpenBSD, FreeBSD and NetBSD source code and there is no
explicit upper limit for sector size. Just that sector size must be
power of two.

I have not did tests yet, but you are right that some testing should be
done.

As FAT operates with clusters and cluster size is defined by sector
size, then sectors per cluster and sector size defines cluster size. And
cluster size itself implies maximal size of FAT filesystem.

So increasing sector size could be useful to create larger FAT32
filesystems as current limit hit by sector size = 512 bytes.

What do you think, which operating systems should be tested?

-- 
Pali Rohár
pali.rohar@gmail.com

  reply	other threads:[~2018-09-12 15:21 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-09-02 13:19 [PATCH] fat: Relax checks for sector size and media type Pali Rohár
2018-09-03  7:17 ` OGAWA Hirofumi
2018-09-03  7:40   ` Pali Rohár
2018-09-03  8:01     ` OGAWA Hirofumi
2018-09-03  8:04       ` Pali Rohár
2018-09-03  8:19         ` OGAWA Hirofumi
2018-09-12 10:17           ` Pali Rohár [this message]
2018-09-12 10:36             ` OGAWA Hirofumi

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=20180912101750.6slpi3puoww72xsj@pali \
    --to=pali.rohar@gmail.com \
    --cc=hirofumi@mail.parknet.co.jp \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).