- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- filesystem blksize - "mkfs -m" and "fstyp -v" disa...
Operating System - HP-UX
1753349
Members
5162
Online
108792
Solutions
Forums
Categories
Company
Local Language
юдл
back
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Forums
Discussions
юдл
back
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Go to solution
Topic Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО09-15-2006 09:03 AM
тАО09-15-2006 09:03 AM
On a test server, I did the following command.
newfs -F vxfs -b 1024 -o largefiles /dev/vg10/rlvol1
MKFS looks like it created a filesystem with a blocksize of 1k.
# mkfs -m /dev/vg10/lvol1
mkfs: /etc/default/fs is used for determining the file system type
mkfs -F vxfs -o ninode=unlimited,bsize=1024,version=6,inosize=256,logsize=16384,
largefiles /dev/vg10/lvol1 71114752
But FSTYP, sayas f_bsize is 8,192 ???
# fstyp -v /dev/vg10/lvol1
vxfs
version: 6
f_bsize: 8192
f_frsize: 1024
f_blocks: 71114752
f_bfree: 71080235
f_bavail: 66637721
f_files: 17770088
f_ffree: 17770056
f_favail: 17770056
f_fsid: 1073872897
f_basetype: vxfs
f_namemax: 254
f_magic: a501fcf5
f_featurebits: 0
f_flag: 16
f_fsindex: 9
f_fsize: 71114752
refrcsk1:[/root]
Shouldn't they match ?
newfs -F vxfs -b 1024 -o largefiles /dev/vg10/rlvol1
MKFS looks like it created a filesystem with a blocksize of 1k.
# mkfs -m /dev/vg10/lvol1
mkfs: /etc/default/fs is used for determining the file system type
mkfs -F vxfs -o ninode=unlimited,bsize=1024,version=6,inosize=256,logsize=16384,
largefiles /dev/vg10/lvol1 71114752
But FSTYP, sayas f_bsize is 8,192 ???
# fstyp -v /dev/vg10/lvol1
vxfs
version: 6
f_bsize: 8192
f_frsize: 1024
f_blocks: 71114752
f_bfree: 71080235
f_bavail: 66637721
f_files: 17770088
f_ffree: 17770056
f_favail: 17770056
f_fsid: 1073872897
f_basetype: vxfs
f_namemax: 254
f_magic: a501fcf5
f_featurebits: 0
f_flag: 16
f_fsindex: 9
f_fsize: 71114752
refrcsk1:
Shouldn't they match ?
Ride Boldly Ride, but watch out for El Dorado's
Solved! Go to Solution.
2 REPLIES 2
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО09-15-2006 09:19 AM
тАО09-15-2006 09:19 AM
Solution
If you do a "man 2 statvfs" you will find that f_bsize is the preferred block size whereas f_frsize is the fundamental block size so the display is quite correct. Now, why do you care? I know you were told in Oracle class that matching the filesystem block size to the database blocksize (or some integral multiple thereof) is vitally important. In vxfs filesystems, it doesn't matter at all. Unlike hfs/ufs filesystems which are block-based, vxfs filesystems are extent-based which means that they attempt to write in large chunks. Blocksize has no impact upon performance at all; it merely represents the smallest chunk of disk space that a file will actually occupy.
If it ain't broke, I can fix that.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО09-15-2006 09:39 AM
тАО09-15-2006 09:39 AM
Re: filesystem blksize - "mkfs -m" and "fstyp -v" disagree
The customer had some HP consultants come in and examine their system, and give them a list of recommendations. They recommended changing the filesystem block size for the oracle redo logs filesystems, and some other stuff like using the Distributed Allocation Policy with PVG's. I see your point (I had actually see it earlier searching the forum for similar questions) and I agree with you, but it's sometimes easier to just make the change that the customer is requesting.
Thanks for explaining the difference between bsize and frsize. I appreciate it.
Well it's 5:30 on a Friday, time to go riding. 8-)
Thanks for explaining the difference between bsize and frsize. I appreciate it.
Well it's 5:30 on a Friday, time to go riding. 8-)
Ride Boldly Ride, but watch out for El Dorado's
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
News and Events
Support
© Copyright 2024 Hewlett Packard Enterprise Development LP