<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: RAW device in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/raw-device/m-p/3549837#M224701</link>
    <description>Our Informix databases use raw volumes because of the caching issue with LVM. This was a problem a while back when we wanted to use LVM to perform split mirror backups but were worried about data loss because of the caching. &lt;BR /&gt;&lt;BR /&gt;However I have since found at that LVM volumes can be mounted with caching turned off (one of the -o options I believe).</description>
    <pubDate>Mon, 23 May 2005 06:35:39 GMT</pubDate>
    <dc:creator>Nick Wickens</dc:creator>
    <dc:date>2005-05-23T06:35:39Z</dc:date>
    <item>
      <title>RAW device</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/raw-device/m-p/3549833#M224697</link>
      <description>what is the function of raw device and how its works.</description>
      <pubDate>Mon, 23 May 2005 06:14:31 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/raw-device/m-p/3549833#M224697</guid>
      <dc:creator>Anit</dc:creator>
      <dc:date>2005-05-23T06:14:31Z</dc:date>
    </item>
    <item>
      <title>Re: RAW device</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/raw-device/m-p/3549834#M224698</link>
      <description>Hi Anit,&lt;BR /&gt;Raw device is the raw partition on the disk. System communicate with this partition using character device which is faster than block device. &lt;BR /&gt;Raw devices are normally used for configuring SWAP Space and Database files on the Systems.&lt;BR /&gt;&lt;BR /&gt;When you format the partition or create PV,LV and then create FileSystem on the top of it then it becomes a block device and follow the filesystem architecture.&lt;BR /&gt;Due to FS overhead it becomes bit slower as compared to RAW device.&lt;BR /&gt;&lt;BR /&gt;For more details you may visit &lt;A href="http://docs.hp.com" target="_blank"&gt;http://docs.hp.com&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;Hope that helps.&lt;BR /&gt;Regards,&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Mon, 23 May 2005 06:21:17 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/raw-device/m-p/3549834#M224698</guid>
      <dc:creator>Bharat Katkar</dc:creator>
      <dc:date>2005-05-23T06:21:17Z</dc:date>
    </item>
    <item>
      <title>Re: RAW device</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/raw-device/m-p/3549835#M224699</link>
      <description>When a process sends requests to a rdsk type special file, it is talking directly to the driver. A read or a write goes directly to or from device.&lt;BR /&gt;&lt;BR /&gt;When a process sends requests to a dsk type special file, it is talking to high level os routines. A read or write goes to or from the buffer cache. If needed, the os will read new data into the buffer cache. There are no alignment restrictions. You can read or write any collection of bytes anywhere on the device. The os will send aligned requests to the driver, but this is hidden from the process. I/O requests that arise from accesses to a dsk type special file enter the driver via its strategy entry point, not the read and write entry points. The driver may resequence the requests to optimize overall performance.&lt;BR /&gt;</description>
      <pubDate>Mon, 23 May 2005 06:27:23 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/raw-device/m-p/3549835#M224699</guid>
      <dc:creator>Suraj Singh_1</dc:creator>
      <dc:date>2005-05-23T06:27:23Z</dc:date>
    </item>
    <item>
      <title>Re: RAW device</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/raw-device/m-p/3549836#M224700</link>
      <description>Hi Anit,&lt;BR /&gt;   If you are using raw device file for data transfer, ur data will be directly written to the disk device. It won't use buffer cache for data transfer, while the block device files use buffer cache for data transfer. The data transfer will be byte by byte in raw, while the block device file is block by block....&lt;BR /&gt;  If the power fails while the data transfer is taking place, in the case of block device the data that are in buffer(the data that are modified) will be lost.. But, in case of raw device, there is no loss of modified data since it's not using buffer for writing.. That's why most of the databases are using raw device file for data manipulation... &lt;BR /&gt;     Hope this will give you an idea about raw devices...&lt;BR /&gt;Regards,&lt;BR /&gt;Saravanan M&lt;BR /&gt;</description>
      <pubDate>Mon, 23 May 2005 06:30:53 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/raw-device/m-p/3549836#M224700</guid>
      <dc:creator>Saravanan_15</dc:creator>
      <dc:date>2005-05-23T06:30:53Z</dc:date>
    </item>
    <item>
      <title>Re: RAW device</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/raw-device/m-p/3549837#M224701</link>
      <description>Our Informix databases use raw volumes because of the caching issue with LVM. This was a problem a while back when we wanted to use LVM to perform split mirror backups but were worried about data loss because of the caching. &lt;BR /&gt;&lt;BR /&gt;However I have since found at that LVM volumes can be mounted with caching turned off (one of the -o options I believe).</description>
      <pubDate>Mon, 23 May 2005 06:35:39 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/raw-device/m-p/3549837#M224701</guid>
      <dc:creator>Nick Wickens</dc:creator>
      <dc:date>2005-05-23T06:35:39Z</dc:date>
    </item>
    <item>
      <title>Re: RAW device</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/raw-device/m-p/3549838#M224702</link>
      <description>In OS (hp-ux) perspective,&lt;BR /&gt;  All low level operations on disk devices has to be done using the raw device files. for example, we've to use raw devices for creating PV and filesystems. For Ex:&lt;BR /&gt;&lt;BR /&gt;To Initialize PV&lt;BR /&gt;#pvcreate /dev/rdsk/c0t2d0&lt;BR /&gt;&lt;BR /&gt;To create a filesystem on lvol1 of vg02&lt;BR /&gt;#newfs -F vxfs /dev/vg02/rlovl1&lt;BR /&gt;&lt;BR /&gt;Regards,&lt;BR /&gt;Saravanan M</description>
      <pubDate>Mon, 23 May 2005 06:40:02 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/raw-device/m-p/3549838#M224702</guid>
      <dc:creator>Saravanan_15</dc:creator>
      <dc:date>2005-05-23T06:40:02Z</dc:date>
    </item>
  </channel>
</rss>

