Sponsored Content
Top Forums UNIX for Advanced & Expert Users Physical disk IO size smaller than fragment block filesystem size ? Post 302770619 by rarino2 on Sunday 17th of February 2013 01:21:40 PM
Old 02-17-2013
Hello Praveen,
I'm not sure if you are mixing FS layer and phisical (disk driver) layer. I was speaking about FS layer (and block device driver layer) in my first post.

mcnamara answer was right.

Quote:
Originally Posted by Praveen_218
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 ?
1) fstype
2) dtrace script from DTrace Toolkit (bitesize.d)
 

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
DISKPART(8)						    BSD System Manager's Manual 					       DISKPART(8)

NAME
diskpart -- calculate default disk partition sizes SYNOPSIS
diskpart [-d] [-p] [-s size] disk-type DESCRIPTION
diskpart is used to calculate the disk partition sizes based on the default rules used at Berkeley. Available options and operands: -d An entry suitable for inclusion in the disk description file /etc/disktab is generated; for example, disktab(5). -p Tables suitable for inclusion in a device driver are produced. -s size The size of the disk may be limited to size with the -s option. On disks that use bad144(8) type of bad-sector forwarding, space is normally left in the last partition on the disk for a bad sector forward- ing table, although this space is not reflected in the tables produced. The space reserved is one track for the replicated copies of the ta- ble and sufficient tracks to hold a pool of 126 sectors to which bad sectors are mapped. For more information, see bad144(8). The -s option is intended for other controllers which reserve some space at the end of the disk for bad-sector replacements or other control areas, even if not a multiple of cylinders. The disk partition sizes are based on the total amount of space on the disk as given in the table below (all values are supplied in units of sectors). The 'c' partition is, by convention, used to access the entire physical disk. The device driver tables include the space reserved for the bad sector forwarding table in the 'c' partition; those used in the disktab and default formats exclude reserved tracks. In normal operation, either the 'g' partition is used, or the 'd', 'e', and 'f' partitions are used. The 'g' and 'f' partitions are variable-sized, occupying whatever space remains after allocation of the fixed sized partitions. If the disk is smaller than 20 Megabytes, then diskpart aborts with the message ``disk too small, calculate by hand''. Partition 20-60 MB 61-205 MB 206-355 MB 356+ MB a 15884 15884 15884 15884 b 10032 33440 33440 66880 d 15884 15884 15884 15884 e unused 55936 55936 307200 h unused unused 291346 291346 If an unknown disk type is specified, diskpart will prompt for the required disk geometry information. SEE ALSO
disktab(5), bad144(8) HISTORY
The diskpart command appeared in 4.2BSD. BUGS
Most default partition sizes are based on historical artifacts (like the RP06), and may result in unsatisfactory layouts. When using the -d flag, alternative disk names are not included in the output. BSD
June 6, 1993 BSD
All times are GMT -4. The time now is 07:41 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy