- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Difference between HFS vs. VxFS
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Forums
Discussions
Discussions
Discussions
Forums
Discussions
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
Community
Resources
Forums
Blogs
- 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
06-25-2001 10:26 AM
06-25-2001 10:26 AM
What does that really mean? Is there any reason why you wouldn't want to create a new filesystem as VxFS under HP-UX 11.0 for use for a database application?
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-25-2001 10:39 AM
06-25-2001 10:39 AM
SolutionAlso, vxfs allocates inodes on the fly whereas hfs has a fixed number of inodes. If you run out of indes you have to rebuild the file system and specify more inodes.
See: http://docs.hp.com/hpux/onlinedocs/B2355-90672/B2355-90672.html for more information. Hope this helps.
Rob
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-25-2001 10:49 AM
06-25-2001 10:49 AM
Re: Difference between HFS vs. VxFS
"Journaled File Systems" ('JFS', a.k.a. 'vxfs') are the standard type with 11.0. JFS filesytstems can be extended or shrunk dynamically without having to unmount them (with the Online-JFS component). JFS filesystems also provide a variety of mount options which when used appropriately can boost filesystem performance (see: 'man 1m mount_vxfs').
Following a crash, the time to verify the integrity of a filesystem (and to repair it) is greatly reduced for JFS ones over the older HFS filesystem. This is because JFS filesystems keep an "intent log" for replaying the changes made to a filesystem. Thus the entire structure doesn't need to be verified and/or repaired.
...JRF...
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-25-2001 10:50 AM
06-25-2001 10:50 AM
Re: Difference between HFS vs. VxFS
One great feature of VxFS is the OnlineJFS product. It is a separately licensed product, but I don't think I could live without it.
OnlineJFS lets you do things such as resize filesystems while mounted. You can also defrag a FS. I would consider it a must for a production database environment that requires significant uptime.
Hope this helps,
Jared
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-25-2001 11:08 AM
06-25-2001 11:08 AM
Re: Difference between HFS vs. VxFS
If you are using OnlineJFS for databases you have another option which will result in a noticeable performance increase (I've observed 18%):
use the vxfs -o convosync=direct,mincache=direct,nodatainlog mount options.
Use these for the data and indexes and the normal options for archive/redo logs. The above options bypass the unix file buffers and only use the buffers in the SGA. This gives you all the performance on raw disk while still using conventional cooked files. This also means that you can reduce the unix buffer size and increase the SGA size.
Regards, Clay