HPE GreenLake Administration
- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- use of raw volume
Operating System - HP-UX
1825723
Members
2900
Online
109687
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
Forums
Discussions
Discussions
Discussions
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
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
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
04-14-2011 09:02 AM
04-14-2011 09:02 AM
use of raw volume
what is the use of raw disk in lvm rather than block device file.
is there any disadvantage and advantage in it.
is there any disadvantage and advantage in it.
2 REPLIES 2
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-14-2011 10:17 AM
04-14-2011 10:17 AM
Re: use of raw volume
Hi,
Raw volumes are addressed in character mode. This is, generally speaking, faster then block mode. As block mode requires buffering and character mode does not. Raw volumes are usually used for database applications (Oracle).
ADVANTAGES RAW:
(+) generally faster (although the difference is not as big as it used to be)
DISADVANTAGES RAW:
(-) you cannot address files directly on a raw volume (you will need through a RDBMS interface)
(-) no fsck alternative (so always make sure to shutdown everything correctly)
sangilak
Raw volumes are addressed in character mode. This is, generally speaking, faster then block mode. As block mode requires buffering and character mode does not. Raw volumes are usually used for database applications (Oracle).
ADVANTAGES RAW:
(+) generally faster (although the difference is not as big as it used to be)
DISADVANTAGES RAW:
(-) you cannot address files directly on a raw volume (you will need through a RDBMS interface)
(-) no fsck alternative (so always make sure to shutdown everything correctly)
sangilak
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-14-2011 04:16 PM
04-14-2011 04:16 PM
Re: use of raw volume
The raw disk device file points to the same volume as the block or cooked device files. These lvols by themselves have no properties except a series of disk blocks. The block device file uses a different driver that is run through the buffer cache to help performance when the lvol contains a file system.
An lvol might have a filesystem created on it, or the raw device could be used as a swap device. But the most common application use of a raw lvol is for databases such as Sybase or Informix. Oracle can also be setup to use raw lvols, but in all cases, backup of these volumes will require specialized software. There are no files -- just a series of bytes that are only meaningful to the programs that created them.
From a sysadmin perspective, these can be tgricky to manage. There is nothing to prevent destroying the database volumes with newfs, so it is always a good idea NOT to use default lvol names (like lvol1, lvol2, etc). Using a different VG name like /dev/rawstuff is also useful.
But in the end, your database administrator will probably make the decision whether to use raw volumes or not.
Bill Hassell, sysadmin
An lvol might have a filesystem created on it, or the raw device could be used as a swap device. But the most common application use of a raw lvol is for databases such as Sybase or Informix. Oracle can also be setup to use raw lvols, but in all cases, backup of these volumes will require specialized software. There are no files -- just a series of bytes that are only meaningful to the programs that created them.
From a sysadmin perspective, these can be tgricky to manage. There is nothing to prevent destroying the database volumes with newfs, so it is always a good idea NOT to use default lvol names (like lvol1, lvol2, etc). Using a different VG name like /dev/rawstuff is also useful.
But in the end, your database administrator will probably make the decision whether to use raw volumes or not.
Bill Hassell, sysadmin
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.
Company
Support
Events and news
Customer resources
© Copyright 2025 Hewlett Packard Enterprise Development LP