Sponsored Content
Top Forums UNIX for Advanced & Expert Users Physical disk IO size smaller than fragment block filesystem size ? Post 302769399 by Praveen_218 on Tuesday 12th of February 2013 06:15:49 AM
Old 02-12-2013
Quote:
Originally Posted by rarino2
Hi Jim! Thanks for your time.

I'm not sure to understand you well. When you say "blocks" in your post, are you speaking about physical (disk) blocks (sectors)?

!
A block is still (on most FS) refers to 4K of data only.

On most system the page-cache is still of this fix sizes. Hence on all block I/O is of 4K or less. The file systems on such system utilizes the maximum size which is 4k.

However, if you see the disk architecture, they have been under trial by various vendors with various sector sizes; with 512bytes sector disk supported by most of the File system and storage product vendors (they however support various other size disks too -but 512b sector disk is in most common use probably because windows/DOS/UNIX FS supported them).

In order to support various disk architecture and FS supporting them use fragmentation which of course let you divide the 4k of page size into various fragments of 1, 2, ... 8 fragments per page.

8-fragments per page is the lowest value which translate into the size of a sector. You can of course not use a sector half of it. For I/O of 1 to full 512 byte of data a full sector gets used in one disk write.

Can you post here the steps you used to test this figures :
1) On UFS, how you saw the fragment size of 1 KB?
2) How did you looked at the 512kb I/O ?
 

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

vol group - physical partition size

Hi Everyone, Can someone tell me the effect of the pp size of the volume group created for Oracle data. It would seem that creating small pp's will cause more overhead. What if you make the pp to large? What should I base this size on? Thanks, (4 Replies)
Discussion started by: kburrows
4 Replies

2. AIX

How can I find the filesystem block size?

How can I find the filesystem block size in AIX? I need to check if it is the same as my DB block size. (4 Replies)
Discussion started by: progressdll
4 Replies

3. HP-UX

determine the physical size of the hard disk

Hi is there a cmd in hpux 11 to determine the physical size of the hard disk. not bdf command. i have searched the other threads here but cant find an answer. thank you guys (4 Replies)
Discussion started by: hoffies
4 Replies

4. IP Networking

IPMI - Get physical memory size

Hi, Does anybody know how to get the RAM size of a powerless server (OS off), with a network hardware management protocol like IPMI ??? Thx (0 Replies)
Discussion started by: sncr24
0 Replies

5. UNIX Desktop Questions & Answers

block group size of a filesystem

How can I determine the block group size of my filesystem, in case I would like to determine where my backup superblocks are? Or how can I determine the location of my backup superblock? If usually, for the block group size of 1k, the alternate superblock will be at block 8193. Thanks, (2 Replies)
Discussion started by: Pouchie1
2 Replies

6. Shell Programming and Scripting

Script to Compare file size and delete the smaller

I am pretty new to scripting, so I appreciate your advice in advance. The problem: 100 directories each containing 2 files that have the same extension with random names. The only attribute that discriminates the files is size. I would like to write a script that compares the files for size... (6 Replies)
Discussion started by: JC_1
6 Replies

7. Solaris

ZFS : Can arc size value exceed Physical RAM ?

Hi, kstat -p -m zfs -n arcstats -s size returns zfs:0:arcstats:size 8177310584 this values is approx (7.61 GB) but my Physical Memory size is only 6144 Megabytes. Can this happen ? if yes, then how can I find free memory on the system. BTW, I ran the kstat commands from a Non... (2 Replies)
Discussion started by: sapre_amit
2 Replies

8. Shell Programming and Scripting

Compress a tar file to smaller size

I have a tar file with name DTT012_GP_20140207.tar and many more with different names of different sizes ranging from 1GB to 4GB. Now my requirement is to extract/not extract these files and then divide it into various parts of size 500MB and save it with different names and then compress... (5 Replies)
Discussion started by: Shaibal_bp
5 Replies

9. HP-UX

About Block Size and Fragment Size

Accordingly a lot of manuals - if you have block size 8KB and trying to write a 1KB file to the block, as result you waste 7KB of the block space. But recently I noticed about Fragments of File Block. In same case if you have File Block 8KB and Fragment size 1KB - you can save your block space,... (6 Replies)
Discussion started by: jess_t03
6 Replies

10. Solaris

Changing physical block size in ssd.conf Solaris

Close (0 Replies)
Discussion started by: gull05
0 Replies
NEWFS(8)						    BSD System Manager's Manual 						  NEWFS(8)

NAME
newfs -- construct a new file system SYNOPSIS
newfs [-NO] [-S sector-size] [-T disktype] [-a maxcontig] [-b block-size] [-c cylinders] [-d rotdelay] [-e maxbpg] [-f frag-size] [-i bytes] [-k skew] [-l interleave] [-m free space] [-n rotational positions] [-o optimization] [-p sectors] [-r revolutions] [-s size] [-t tracks] [-u sectors] [-x sectors] special DESCRIPTION
Newfs replaces the more obtuse mkfs(8) program. Before running newfs the disk must be labeled using disklabel(8). Newfs builds a file sys- tem on the specified special device basing its defaults on the information in the disk label. Typically the defaults are reasonable, however newfs has numerous options to allow the defaults to be selectively overridden. The following options define the general layout policies. -N Causes the file system parameters to be printed out without really creating the file system. -O Creates a 4.3BSD format filesystem. This options is primarily used to build root filesystems that can be understood by older boot ROMs. -T Uses information for the specified disk from /etc/disktab instead of trying to get the information from a disklabel. -a maxcontig This specifies the maximum number of contiguous blocks that will be laid out before forcing a rotational delay (see the -d option). The default value is one. See tunefs(8) for more details on how to set this option. -b block-size The block size of the file system, in bytes. -c #cylinders/group The number of cylinders per cylinder group in a file system. The default value is 16. -d rotdelay This specifies the expected time (in milliseconds) to service a transfer completion interrupt and initiate a new transfer on the same disk. The default is 4 milliseconds. See tunefs(8) for more details on how to set this option. -e maxbpg This indicates the maximum number of blocks any single file can allocate out of a cylinder group before it is forced to begin allocating blocks from another cylinder group. The default is about one quarter of the total blocks in a cylinder group. See tunefs(8) for more details on how to set this option. -f frag-size The fragment size of the file system in bytes. -i number of bytes per inode This specifies the density of inodes in the file system. The default is to create an inode for each 2048 bytes of data space. If fewer inodes are desired, a larger number should be used; to create more inodes a smaller number should be given. -m free space % The percentage of space reserved from normal users; the minimum free space threshold. The default value used is 10%. See tunefs(8) for more details on how to set this option. -n rotational positions Determines how many rotational time slots there are in one revolution of the disk. -o optimization preference (``space'' or ``time'') The file system can either be instructed to try to minimize the time spent allocating blocks, or to try to minimize the space fragmentation on the disk. If the value of minfree (see above) is less than 10%, the default is to opti- mize for space; if the value of minfree is greater than or equal to 10%, the default is to optimize for time. See tunefs(8) for more details on how to set this option. -s size The size of the file system in sectors. The following options override the standard sizes for the disk geometry. Their default values are taken from the disk label. Changing these defaults is useful only when using newfs to build a file system whose raw image will eventually be used on a different type of disk than the one on which it is initially created (for example on a write-once disk). Note that changing any of these values from their defaults will make it impossible for fsck to find the alternate superblocks if the standard superblock is lost. -S sector-size The size of a sector in bytes (almost never anything but 512). -k sector 0 skew, per track Used to describe perturbations in the media format to compensate for a slow controller. Track skew is the offset of sector 0 on track N relative to sector 0 on track N-1 on the same cylinder. -l hardware sector interleave Used to describe perturbations in the media format to compensate for a slow controller. Interleave is physical sector interleave on each track, specified as the denominator of the ratio: sectors read/sectors passed over Thus an interleave of 1/1 implies contiguous layout, while 1/2 implies logical sector 0 is separated by one sector from logical sector 1. -p spare sectors per track Spare sectors (bad sector replacements) are physical sectors that occupy space at the end of each track. They are not counted as part of the sectors/track (-u) since they are not available to the file system for data allocation. -r revolutions/minute The speed of the disk in revolutions per minute. -t #tracks/cylinder The number of tracks/cylinder available for data allocation by the file system. -u sectors/track The number of sectors per track available for data allocation by the file system. This does not include sectors reserved at the end of each track for bad block replacement (see the -p option.) -x spare sectors per cylinder Spare sectors (bad sector replacements) are physical sectors that occupy space at the end of the last track in the cylinder. They are deducted from the sectors/track (-u) of the last track of each cylinder since they are not available to the file system for data allocation. SEE ALSO
fs(5), dumpfs(8), fdisk(8), fsck(8), mount(8), pdisk(8), tunefs(8) M. McKusick, W. Joy, S. Leffler, and R. Fabry, "A Fast File System for UNIX,", ACM Transactions on Computer Systems 2, 3, pp 181-197, August 1984, (reprinted in the BSD System Manager's Manual). HISTORY
The newfs command appeared in 4.2BSD. 4.2 Berkeley Distribution May 3, 1995 4.2 Berkeley Distribution
All times are GMT -4. The time now is 11:10 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy