- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Re: mount option using JFS
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
Discussions
Discussions
Forums
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
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
тАО10-26-2001 10:01 AM
тАО10-26-2001 10:01 AM
mount -F vxfs -o delaylog,mincache=direct,convosync=direct,nodatainlog
While reading the archives , somebody was suggesting to mount only datafiles . I am confused now and needs your opinion.
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-26-2001 10:08 AM
тАО10-26-2001 10:08 AM
Re: mount option using JFS
datafiles ,indexes , redo log , archive logs etc...
Most importantly, seperate your these: Datafiles, indexes from the archive and redo logs.
live free or die
harry
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-26-2001 10:11 AM
тАО10-26-2001 10:11 AM
Re: mount option using JFS
I would use those option on data files and indices. I would fallback to the more conventional options delaylog, nodatainlog and thus use buffer cache for archive and redo logs.
If all your Oracle data is going to an array, I tend to put both data and indices in the same filesystem and put the archive and redo logs in a another and that's it. I know the DBA's have a heart attack when I do that but send it to the array and let it sort the plater stuff out. That's why I bought it. Now I do stripe each logical volume across multilple I/O channels. If I have three channels, each VG will consist of 3 equally sized LUN's and each LVOL within that VG will be stripped across all three LUN's. The idea is to get data in and out of the array as fast as possible. Doing it this way eliminates the guesswork involved in trying to figure out how busy any particular data file is and where I should put it.
My 3 cents, Clay
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-26-2001 10:31 AM
тАО10-26-2001 10:31 AM
Re: mount option using JFS
rw,nosuid,mincache=direct,convosync=direct,nodatainlog
and how it is differ from my previous mount option. Is it going to work for both datafiles and indexes as well.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-26-2001 11:24 AM
тАО10-26-2001 11:24 AM
Re: mount option using JFS
I believe 'rw' is default. 'nosuid' won't let programs get other ids even if suid-ed.
Yes :)
E.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-26-2001 11:33 AM
тАО10-26-2001 11:33 AM
SolutionData files and indices:
rw,suid,delaylog,nodatainlog,convosync=direct,mincahce=direct
Archives and redo logs:
rw,suid,delaylog,nodatainlog
If you run the =direct options, you should probably greatly reduce your buffer cache and use the space for SGA buffers.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-26-2001 11:49 AM
тАО10-26-2001 11:49 AM
Re: mount option using JFS
I would certainly use "datainlog, convosync=direct, mincahce=direct " for all oracle data/index files.
As far I know "datainlog" is default option and is faster in performance than "nodatainlog".
Take a look at following link for details on different options to mount related to VxFS
http://docs.hp.com/hpux/onlinedocs/B3929-90011/B3929-90011.html
Thanks.
Prashant.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-26-2001 12:24 PM
тАО10-26-2001 12:24 PM
Re: mount option using JFS
Here is qoute from JFS document.
"A nodatainlog mode file system should be approximately 50 percent slower than a standard mode VxFS file system for synchronous writes"
Any final thoughts of using nodatainlog v/s datainlog.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-26-2001 12:43 PM
тАО10-26-2001 12:43 PM
Re: mount option using JFS
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-26-2001 12:58 PM
тАО10-26-2001 12:58 PM
Re: mount option using JFS
The nodatainlog is certainly true for most cases. The idea is that the filesystem changes AND the data is written to a log within the filesystem then then data is written into the filesystem blocks at a later time. This is great for integrity when filesystem internal values are changing - like new files being created or files removed or new blocks added to an existing files and the last written data in also in the log. In most cases, this is a good thing, we have to write to the log and while the head is correctly positioned we can write data to the log and return. The transfer to the actual file takes place a bit later. However, database file are pre-allocated; the filesystem doesn't need to be updated. Now ask yourself, how many times does the data get wriiten with nodatainlog - once. With datainlog - twice.
However, the real test is to simply change the mount options and measure; always ask the box about the best method.