Bug 192262 - the -S flag of newfs do not take effective,sector size always set to 512
Summary: the -S flag of newfs do not take effective,sector size always set to 512
Status: Closed Works As Intended
Alias: None
Product: Base System
Classification: Unclassified
Component: bin (show other bugs)
Version: 10.0-RELEASE
Hardware: amd64 Any
: --- Affects Only Me
Assignee: freebsd-bugs (Nobody)
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-07-30 00:46 UTC by Jov
Modified: 2014-08-02 05:30 UTC (History)
1 user (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Jov 2014-07-30 00:46:49 UTC
newfs -S 4k -U /dev/da1p2 
/dev/da1p2: 544268.7MB (1114662280 sectors) block size 32768, fragment size 4096
	using 870 cylinder groups of 626.09MB, 20035 blks, 80256 inodes.
	with soft updates
....

newfs -N -U /dev/da1p2
/dev/da1p2: 544268.7MB (1114662280 sectors) block size 32768, fragment size 4096
	using 870 cylinder groups of 626.09MB, 20035 blks, 80256 inodes.
	with soft updates

while the sector size always 512 (544268.7MB / 1114662280 ).But My disk' phys sector size is 4k,I want to set the ufs sector to 4k.
Comment 1 Xin LI freebsd_committer freebsd_triage 2014-07-30 01:07:38 UTC
This doesn't really matter.  By default, the minimal allocation unit ('fragment size') on FreeBSD UFS is 4K on modern systems (used to be 2K), which means it's always 4K ready regardless the underlying disk hardware.
Comment 2 Jov 2014-07-30 01:36:27 UTC
I see.Thank you Xin.
May be this message should be added to the newfs man page?

(In reply to Xin LI from comment #1)
> This doesn't really matter.  By default, the minimal allocation unit
> ('fragment size') on FreeBSD UFS is 4K on modern systems (used to be 2K),
> which means it's always 4K ready regardless the underlying disk hardware.