Linux-BTRFS Archive on lore.kernel.org
 help / color / Atom feed
* mke2fs accepts block size not mentioned in its man page
@ 2019-07-05  5:35 Qu Wenruo
  2019-08-09  1:00 ` Darrick J. Wong
  0 siblings, 1 reply; 2+ messages in thread
From: Qu Wenruo @ 2019-07-05  5:35 UTC (permalink / raw)
  To: linux-ext4; +Cc: linux-btrfs

[-- Attachment #1.1: Type: text/plain, Size: 842 bytes --]

Hi,

Just doing some tests on aarch64 with 64K page size.

Man page of mke2fs only mentions 3 valid block size: 1k, 2k, 4k.
But in real world, we can pass 64K as block size for it without any problem:

  $mke2fs -F -t ext3 -b 65536 /dev/loop1
  Warning: blocksize 65536 not usable on most systems.
  mke2fs 1.45.2 (27-May-2019)
  /dev/loop1 contains a btrfs file system
  Discarding device blocks: done
  Creating filesystem with 81920 64k blocks and 81920 inodes
  Filesystem UUID: 311bb224-6d2d-44a7-9790-92c4878d6549
  [...]

It's great to see mke2fs accepts 64K as nodesize, which allows
btrfs-convert to work.
(If blocksize is default to 4K or doesn't accept 64K page size,
btrfs-convert can work but can't be mounted on system with 64K page size)

Shouldn't the man page mention all valid values?

Thanks,
Qu


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

^ permalink raw reply	[flat|nested] 2+ messages in thread

* Re: mke2fs accepts block size not mentioned in its man page
  2019-07-05  5:35 mke2fs accepts block size not mentioned in its man page Qu Wenruo
@ 2019-08-09  1:00 ` Darrick J. Wong
  0 siblings, 0 replies; 2+ messages in thread
From: Darrick J. Wong @ 2019-08-09  1:00 UTC (permalink / raw)
  To: Qu Wenruo; +Cc: linux-ext4, linux-btrfs

On Fri, Jul 05, 2019 at 01:35:02PM +0800, Qu Wenruo wrote:
> Hi,
> 
> Just doing some tests on aarch64 with 64K page size.
> 
> Man page of mke2fs only mentions 3 valid block size: 1k, 2k, 4k.
> But in real world, we can pass 64K as block size for it without any problem:
> 
>   $mke2fs -F -t ext3 -b 65536 /dev/loop1
>   Warning: blocksize 65536 not usable on most systems.
>   mke2fs 1.45.2 (27-May-2019)
>   /dev/loop1 contains a btrfs file system
>   Discarding device blocks: done
>   Creating filesystem with 81920 64k blocks and 81920 inodes
>   Filesystem UUID: 311bb224-6d2d-44a7-9790-92c4878d6549
>   [...]
> 
> It's great to see mke2fs accepts 64K as nodesize, which allows
> btrfs-convert to work.
> (If blocksize is default to 4K or doesn't accept 64K page size,
> btrfs-convert can work but can't be mounted on system with 64K page size)
> 
> Shouldn't the man page mention all valid values?

You'd think so, but 64k blocks only works on machines with 64k pages,
so that's why it doesn't mention anything beyond the lowest common
denominator. :/

--D

> Thanks,
> Qu
> 




^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, back to index

Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2019-07-05  5:35 mke2fs accepts block size not mentioned in its man page Qu Wenruo
2019-08-09  1:00 ` Darrick J. Wong

Linux-BTRFS Archive on lore.kernel.org

Archives are clonable:
	git clone --mirror https://lore.kernel.org/linux-btrfs/0 linux-btrfs/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 linux-btrfs linux-btrfs/ https://lore.kernel.org/linux-btrfs \
		linux-btrfs@vger.kernel.org linux-btrfs@archiver.kernel.org
	public-inbox-index linux-btrfs


Newsgroup available over NNTP:
	nntp://nntp.lore.kernel.org/org.kernel.vger.linux-btrfs


AGPL code for this site: git clone https://public-inbox.org/ public-inbox