Oracle® Database

4.10.1 Migrating Single Instance Database from Linux x86 to Linux x86-64

To migrate Oracle 10g release 2 single instance database from Linux x86 to Linux x86-64, complete the following procedure:

1. To protect the existing database 10g release 2 against any failures during the migration, ensure that you take a complete backup of the database on Linux x86-64 system.

2. To create a control file that helps file after the migration, run the following SQL command from the SQL prompt on the Linux x86 system:

   SQL> ALTER DATABASE BACKUP CONTROLFILE TO TRACE;
   

   This command saves the control file information to a trace file in the UDUMP directory. The control file information is similar to the following where ia32lnx_path is the location of the Linux x86 Oracle home:

   CREATE CONTROLFILE REUSE DATABASE "SAMPLE" NORESETLOGS
   NOARCHIVELOG
   MAXLOGFILES 32
   MAXLOGMEMBERS 2
   MAXDATAFILES 32
   MAXINSTANCES 1
   MAXLOGHISTORY 112
   LOGFILE GROUP 1 '/ia32lnx_path/oradata/eegp22/redo01.log' 25M,
           GROUP 2 '/ia32lnx_path/oradata/eegp22/redo02.log' 25M
   DATAFILE '/ia32lnx_path/oradata/eegp22/system01.dbf',
   '/ia32lnx_path/oradata/eegp22/sysaux01.dbf',
   '/ia32lnx_path/oradata/eegp22/users01.dbf',
   '/ia32lnx_path/oradata/eegp22/undotbs01.dbf'
   CHARACTER SET WE8DEC;
   

3. Perform a clean Oracle database shutdown.

   SQL> SHUTDOWN IMMEDIATE
   

4. Copy the database files to the Linux x86-64 system.

5. In a new Oracle home, install the Oracle 10g release 2 software for Linux x86-64.

6. Copy the Oracle initialization parameter file (initsid.ora) to the new Oracle home. Change any Oracle home path references to use the new Oracle home path on the Linux x86-64 system.

7. Start up the database using SQL commands similar to the following example where lnx_x86-64_path is the location of the Linux x86-64 Oracle home:

   SQL> STARTUP NOMOUNT;
   CREATE CONTROLFILE REUSE DATABASE "EEGP102" NORESETLOGS
   MAXLOGFILES 32
   MAXLOGMEMBERS 2
   MAXDATAFILES 32
   MAXINSTANCES 1
   MAXLOGHISTORY 112
   LOGFILE GROUP 1 '/lnx_x86-64_path/oradata/eegp22/redo01.log'size 25M,
           GROUP 2 '/lnx_x86-64_path/oradata/eegp22/redo02.log'size 25M
   DATAFILE '/lnx_x86-64_path/oradata/eegp22/system01.dbf',
    '/lnx_x86-64_path/eegp22/sysaux01.dbf',
    '/lnx_x86-64_path/eegp22/users01.dbf',
    '/lnx_x86-64_path/eegp22/undotbs01.dbf'
   CHARACTER SET WE8DEC
   ALTER DATABASE OPEN ;
   

   Note:

   In the preceding example, the path value changes as per the system.

8. To change the word size of the release, run the following commands:

   SQL> STARTUP UPGRADE;
   SQL> @$ORACLE_HOME/rdbms/admin/utlirp.sql
   

9. Run the utlrp.sql script to recompile all PL/SQL packages now instead of when the packages are accessed for the first time. This step is optional but recommended.

   SQL> @$ORACLE_HOME/rdbms/admin/utlrp.sql
   

10. Perform a clean shutdown of the database.

    SQL> SHUTDOWN IMMEDIATE
    

11. Take a complete backup of the database.

    See Also:

    • Oracle Database Backup and Recovery Basics

    • Oracle Database Backup and Recovery Advanced User's Guide

    • Oracle Database Backup and Recovery Reference

    • Oracle Database Backup and Recovery Quick Start Guide

4.10.2 Migrating Oracle RAC Database from Linux x86 to Linux x86-64

To migrate Oracle RAC 10g release 2 from Linux x86 to Linux x86-64, complete the following procedure:

1. Complete steps 1 to 5 of the "Migrating Single Instance Database from Linux x86 to Linux x86-64" section.

2. Use the following command to ensure that gsd is running:

   $ ps -elf | grep gsd
   

3. Use the $ORACLE_HOME/bin/srvctl utility to add the database name and the cluster node names in Linux x86-64. To create a database, use a command similar to the following command:

   $ srvctl add database -d 10gdb -o ORACLE_HOME -m us.oracle.com \-s /dev/raw/raw2
   

   To create an instance, use a command similar to the following command:

   $ srvctl add instance -d 10gdb -i 10gdb1 -n pl-adc.amd15
   

4. Set the ORACLE_SID environment variable for one of the database instances in the environment.

   For the Bash or Korn shell:

   $ ORACLE_SID=10gdb1; export ORACLE_SID
   

   For the C shell:

   % setenv ORACLE_SID 10gdb1
   

5. Export the server parameter file (SPFILE) to a text initialization parameter file as follows:

   SQL> CREATE PFILE = '$ORACLE_HOME/dbs/init10gdb1.ora' FROM SPFILE = '/dev/raw/raw2';
   

6. Edit the text initialization parameter file to update path names to point to the Linux x86-64 Oracle home directory along with any other required changes. Then re-create the SPFILE as follows:

   SQL> CREATE SPFILE = '/dev/raw/raw2' FROM PFILE = '$ORACLE_HOME/dbs/init10gdb1.ora';
   

   Note:

   If the cluster database does not start in EXCLIUSIVE MODE, mark all the entries with cluster-database as comments in the SPFILE.

7. Directories listed in the SPFILE must exist before you start the database. Create these directories, ensuring that they have write permissions for the oracle user and dba groups.

8. Add a listener name for the database that listens on all cluster nodes to the $ORACLE_HOME/network/admin/tnsnames.ora file. Also add an entry for each instance. The following is an example of the entries:

   LISTENERS_10gdb.US.ORACLE.COM =
   (ADDRESS_LIST =
   (ADDRESS = (PROTOCOL = TCP) (HOST = server1-vip) (PORT = 1521)
   (ADDRESS = (PROTOCOL = TCP) (HOST = server2-vip) (PORT = 1521)
   LISTENERS_10gdb1.US.ORACLE.COM = 
   (ADDRESS = (PROTOCOL = TCP) (HOST = server1-vip) (PORT = 1521)
   LISTENERS_10gdb2.US.ORACLE.COM = 
   (ADDRESS = (PROTOCOL = TCP) (HOST = server2-vip) (PORT = 1521)
   

9. Create the password file using the orapwd utility. Use a command similar to the following:

   $ orapwd file=$ORACLE_HOME/dbs/orapwd10gdb1 entries=10 password=manager
   

10. Start the database without mounting it, using SQL commands similar to the following where lnx_x86-64_path is the location of the Linux x86-64 Oracle home:

    SQL> STARTUP NOMOUNT;
    CREATE CONTROLFILE REUSE DATABASE "SAMPLE" NORESETLOGS
    MAXLOGFILES 32
    MAXLOGMEMBERS 2
    MAXDATAFILES 32
    MAXINSTANCES 1
    MAXLOGHISTORY 112
    LOGFILE
    GROUP 1 '/lnx_x86-64_path/oracle/dbs/t_log1.dbf' size 25M
    GROUP 2 '/lnx_x86-64_path/oracle/dbs/t_log2.dbf' size 25M
    DATAFILE
    '/lnx_x86-64_path/oracle/dbs/t_db1.dbf'
    CHARACTER SET WE8DEC
    ALTER DATABASE OPEN
    

11. Shut down the database.

    SQL> SHUTDOWN IMMEDIATE
    

12. Before changing the word size of your release, you must edit the initialization parameter file (pfile) by adding the following line:

    _system_trig_enabled=false
    

13. Use the following command to start the database:

    SQL> STARTUP PFILE = '$ORACLE_HOME/dbs/init-10gdb1.ora'
    

14. Check the amount of free space in the SYSTEM tablespace. Ensure there is enough room for SYSTEM tablespace to increase its size by 50%.

    SQL> SELECT SUM (df.bytes) AS total,
    SUM (fs.bytes) AS free,
    (SUM (fs,bytes)/SUM(df.bytes) * 100) AS percent_free
    FROM dba_data_files df,
    DBA_FREE_SPACE fs
    WHERE df.tablespace_name = 'SYSTEM'
    AND
    df.tablespace_name = fs.tablespace_name
    GROUP BY df.tablespace_name
    

    If you get a percent_free value less than 33%, then you must add a new raw device data file to SYSTEM tablespace, for example:

    SQL> ALTER TABLESPACE SYSTEM ADD DATAFILE '/dev/raw/raw108' SIZE 200M;
    

15. Use the following commands to restart the database in upgrade mode:

    SQL> SHUTDOWN IMMEDIATE;
    SQL> STARTUP UPGRADE
    

16. To change the word size of your release, enter the following command:

    SQL> @$ORACLE_HOME/rdbms/admin/utlirp.sql
    

17. Run the utlrp.sql script to recompile all PL/SQL packages now instead of when the packages are accessed for the first time. This step is optional but recommended.

    SQL> @$ORACLE_HOME/rdbms/admin/utlrp.sql
    

    Note:

    You need to shutdown the database and start it in upgrade mode.

18. Edit the text initialization parameter file to remove the following line:

    _system_trig_enabled=false
    

19. To restart the database, use the following command:

    ./srvctl start database -d 10gdb -o pfile=$USR_ORA_PFILE
    

    Ensure that the USR_ORA_PFILE variable is set to the location of pfile. Alternately, you can specify the complete path of pfile in the command.

20. To create instances on the other cluster nodes, complete the following steps:

    1. Copy the $ORACLE_HOME/network/admin/tnsnames.ora file to the same location on each node.

    2. Create the dump directories listed in the initialization parameter file (pfile) in the Oracle home directory.

    3. Copy the initialization parameter file (pfile) from the original node to the $ORACLE_HOME/dbs directory, changing its name to reflect the instance name on the current node.

    4. Create a password file in the $ORACLE_HOME/dbs directory, ensuring its name includes the instance name for the node.

    5. Start up the instance.

4.13.1 Overview of Device Naming Persistence Changes

With the Linux 2.6 kernel, support for raw devices is deprecated. The preferred storage access is direct input/output to block devices using O_DIRECT. As a result of this change, the RHEL4 and OEL4 file /etc/sysconfig/rawdevice and the RHEL5 and OEL5 file /etc/udev/rules.d/60-raw.rules are deprecated. For details, refer to the Linux documentation for your 2.6 kernel.

The 2.4 kernel device file naming scheme devlabel maintained persistent device file names between server restarts. By default, the 2.6 kernel device file naming scheme udev dynamically creates device file names when the server is started, and assigns ownership of them to root. If udev applies default settings, then it changes device file names and owners for voting disks or Oracle Cluster Registry partitions, corrupting them when the server is restarted. For example, a voting disk on a device named /dev/sdd owned by the user crs may be on a device named /dev/sdf owned by root after restarting the server.

To prevent corruption, you need to create a custom rules file. When udev is started, it sequentially carries out rules (configuration directives) defined in rule files. These files are in the path /etc/udev/rules.d/. Rules files are read in lexical order. For example, rules in file 10-wacom.rules are parsed and carried out before rules in rule file 90-ib.rules. Where rules files describe the same devices, on Asianux, Red Hat, and Oracle Enterprise Linux, the last file read is the one that is applied. (On SUSE 2.6 kernels, it is the first file read).

4.13.2 Configuring Raw Devices for Clusterware on Red Hat and Oracle Enterprise Linux 5

This section contains the following topics:

• Configure SCSI_ID to Return Unique Device Identifiers

• Configure Udev for Persistent Naming of Clusterware Devices

• Bind Raw Devices Using Udev

• Verify Persistent Clusterware Storage Devices

Configure SCSI_ID to Return Unique Device Identifiers

Before you can configure udev to name devices, you must first configure scsi_id to return device identifiers, and then ensure that these devices are visible and accessible on all cluster nodes. To do this, complete the following task:

1. Modify the /etc/scsi_id.config file by adding or replacing the 'option=-b' parameter/value pair (if it exists) with 'option=-g'. For example:

   # cd /etc
   # cp scsi_id.config scsi_id.config.orig
   # grep -v ^# /etc/scsi_id.config
   vendor="ATA",options=-p 0x80
   options=-g
   

2. Run the command fdisk (/sbin/fdisk) to ensure that Clusterware devices are visible. For example:

   # /sbin/fdisk -l /dev/sdb1 /dev/sde1
    
   Disk /dev/sdb1: 261 MB, 261890048 bytes
   9 heads, 56 sectors/track, 1014 cylinders
   Units = cylinders of 504 * 512 = 258048 bytes
    
   Disk /dev/sdb1 doesn't contain a valid partition table
    
   Disk /dev/sde1: 52 MB, 52403200 bytes
   2 heads, 50 sectors/track, 1023 cylinders
   Units = cylinders of 100 * 512 = 51200 bytes
    
   Disk /dev/sde1 doesn't contain a valid partition table
   

   In some cases, to see newly provisioned or modified) devices on shared storage, you may need to update cluster node operating systems. Do this either by restarting the nodes, or by using commands such as /sbin/partprobe device, or sfdisk -r device. Resolve any issues preventing cluster nodes from correctly seeing or accessing storage devices you intend to use for Clusterware files before proceeding.

   Note:

   At this point, cluster nodes may refer to the devices using different device file names. This is expected.

3. Run the command scsi_id (/sbin/scsi_id) on storage devices from one cluster node to obtain their unique device identifiers. When running the scsi_id command with the -s argument, the device path and name passed should be that relative to the sysfs directory /sys (for example, /block/device) when referring to /sys/block/device. For example:

   # /sbin/scsi_id -g -s /block/sdb/sdb1
   360a98000686f6959684a453333524174
    
   # /sbin/scsi_id -g -s /block/sde/sde1
   360a98000686f6959684a453333524179
   

   Record the unique SCSI identifiers of Clusterware devices, so you can provide them when required in the following section, Configure Udev for Persistent Naming of Clusterware Devices.

   Note:

   The command scsi_id should return the same device identifier value for a given device, regardless of which node the command is run from.

Configure Udev for Persistent Naming of Clusterware Devices

Configure persistent user-defined naming of Clusterware device file names in a udev rules file. This step is optional, but recommended.

The default rule files affecting storage devices are rule files 50 and 51. So create a custom rules file using the format [number]-[name][.rules] with a number value greater than 51 to ensure that the device settings you provide are the ones applied. For example:

55-oracle-naming.rules

To do this, complete the following tasks:

1. Create a custom udev device naming rule file. For example:

   # touch /etc/udev/rules.d/55-oracle-naming.rules
   

2. Using the a text editor such as vi, add to the custom device naming rule file the device-matching rules for the storage devices you intend to use with Oracle Clusterware, matching them to the unique SCSI identifiers you determined in the preceding section. For example:

   # Configure persistent, user-defined Oracle Clusterware device file names
   KERNEL=="sd*", BUS=="scsi", PROGRAM=="/sbin/scsi_id", 
   RESULT=="360a98000686f6959684a453333524174", NAME="ocr1", OWNER="root", 
   GROUP="oinstall", MODE="0640"
   KERNEL=="sd*", BUS=="scsi", PROGRAM=="/sbin/scsi_id", RESULT=="360a98000686f6959684a453333524179", NAME="vote1", OWNER="oracle", GROUP="oinstall", MODE="0640"
   

   For each rule, if all specified keys (KERNEL, BUS, PROGRAM, RESULT) are matched, then the rule is applied and the specified assignments (NAME, OWNER, GROUP, MODE) are assigned to the device file name. However, if one or more keys are unmatched, then the rule is completely ignored and the default (arbitrary) kernel-assigned device file names are assigned to devices.

   Note:

   In the example rules files shown, Oracle Clusterware devices are created with oraInventory group (oinstall). Oracle recommends that you do this to ensure that you can run Cluster Verification Utility during installation.

3. Run the command udevtest (/sbin/udevtest) to test the udev rules configuration you have created. The output should indicate that the block devices are available and the rules are applied as expected. For example:

   # udevtest /block/sdb/sdb1
   main: looking at device '/block/sdb/sdb1' from subsystem 'block'
   udev_rules_get_name: add symlink
   'disk/by-id/scsi-360a98000686f6959684a453333524174-part1'
   udev_rules_get_name: add symlink
   'disk/by-path/ip-192.168.1.1:3260-iscsi-iqn.1992-08.com.netapp:sn.887085-part1'
   udev_node_mknod: preserve file '/dev/.tmp-8-17', because it has correct dev_t
   run_program: '/lib/udev/vol_id --export /dev/.tmp-8-17'
   run_program: '/lib/udev/vol_id' returned with status 4
   run_program: '/sbin/scsi_id'
   run_program: '/sbin/scsi_id' (stdout) '360a98000686f6959684a453333524174'
   run_program: '/sbin/scsi_id' returned with status 0
   udev_rules_get_name: rule applied, 'sdb1' becomes 'ocr1'
   udev_device_event: device '/block/sdb/sdb1' validate currently present symlinks
   udev_node_add: creating device node '/dev/ocr1', major = '8', minor = '17', 
   mode = '0640', uid = '0', gid = '500'
   udev_node_add: creating symlink
   '/dev/disk/by-id/scsi-360a98000686f6959684a453333524174-part1' to '../../ocr1'
   udev_node_add: creating symlink
   '/dev/disk/by-path/ip-192.168.1.1:3260-iscsi-iqn.1992-08.com.netapp:sn.84187085
   -part1' to '../../ocr1'
   main: run: 'socket:/org/kernel/udev/monitor'
   main: run: '/lib/udev/udev_run_devd'
   main: run: 'socket:/org/freedesktop/hal/udev_event'
   main: run: '/sbin/pam_console_apply /dev/ocr1
   /dev/disk/by-id/scsi-360a98000686f6959684a453333524174-part1
   /dev/disk/by-path/ip-192.168.1.1:3260-iscsi-iqn.1992-08.com.netapp:sn.84187085-
   part1'
   

   In the example output, note that applying the rules renames OCR device /dev/sdb1 to /dev/ocr1.

4. Restart the udev service by running the command start_udev (/sbin/start_udev). Restarting udev applies the udev rules to the devices, including the device file rules you have created. Use the command ls -l command to ensure that the rules file has applied the new device names the rules file has applied. For example:

   # start_udev
    
   # ls -l /dev | grep -e 'ocr1\|vote1'
   brw-r----- 1 root   oinstall 8, 17 Oct 29 15:31 ocr1
   brw-rw---- 1 oracle oinstall 8, 65 Oct 29 15:31 vote1
   

Bind Raw Devices Using Udev

1. If the file /etc/udev/rules.d/60-raw.rules does not exist, then create it. If it does exist, then create a rules file for raw devices used with Oracle installations. For example:

   # touch /etc/udev/rules.d/60-raw.rules
   

   or

   # touch /etc/udev/rules.d/61-oracleraw.rules
   

2. Add the udev raw binding rules to the raw devices rules file you created. For example:

   vi /etc/udev/rules.d/61-oracleraw.rules
   # Raw bind to Oracle Clusterware devices
   ACTION=="add", KERNEL=="sd*", PROGRAM=="/sbin/scsi_id",
    RESULT=="360a98000686f6959684a453333524174", RUN+="/bin/raw /dev/raw/raw1 %N"
   ACTION=="add", KERNEL=="sd*", PROGRAM=="/sbin/scsi_id",
    RESULT=="360a98000686f6959684a453333524179", RUN+="/bin/raw /dev/raw/raw2 %N"
    t 29 15:31 vote1
   

3. Create a udev raw permissions file /etc/udev/rules.d/65-raw-permissions.rules. For example:

   # touch /etc/udev/rules.d/65-raw-permissions.rules
   

4. Using a text editor, add the udev raw permission rules to the file /etc/udev/rules.d/65-raw-permissions.rules. For example:

   # Set permissions of raw bindings to Oracle Clusterware devices
   KERNEL=="raw1", OWNER="root", GROUP="oinstall", MODE="640"
   KERNEL=="raw2", OWNER="oracle", GROUP="oinstall", MODE="640"
   

5. Test the udev rules by running the udevtest command (/sbin/udevtest) again to ensure that the rules are applied, and that they create proper permissions for Oracle Clusterware devices. For example:

   # udevtest /block/sdb/sdb1
   main: looking at device '/block/sdb/sdb1' from subsystem 'block'
   udev_rules_get_name: add symlink 'disk/by-id/scsi-360a98000686f69
   59684a453333524174-part1'
   udev_rules_get_name: add symlink 'disk/by-path/ip-192.168.1.1:3260
   -iscsi-iqn.1992-08.com.netapp:sn.84187085-part1'
   udev_node_mknod: preserve file '/dev/.tmp-8-17', because it has 
   correct dev_t
   run_program: '/lib/udev/vol_id --export /dev/.tmp-8-17'
   run_program: '/lib/udev/vol_id' returned with status 4
   run_program: '/sbin/scsi_id'
   run_program: '/sbin/scsi_id' (stdout) '360a98000686f6959684a45333
   3524174'
   run_program: '/sbin/scsi_id' returned with status 0
   udev_rules_get_name: rule applied, 'sdb1' becomes 'ocr1'
   udev_device_event: device '/block/sdb/sdb1' validate currently 
   present symlinks
   udev_node_add: creating device node '/dev/ocr1', major = '8', 
   minor = '17', mode = '0640', uid = '0', gid = '500'
   udev_node_add: creating symlink '/dev/disk/by-id/scsi-360a9800068
   6f6959684a453333524174-part1' to '../../ocr1'
   udev_node_add: creating symlink '/dev/disk/by-path/ip-192.168.1.1
   :3260-iscsi-iqn.1992-08.com.netapp:sn.84187085-part1' to '../../ocr1'
   main: run: 'socket:/org/kernel/udev/monitor'
   main: run: '/lib/udev/udev_run_devd'
   main: run: 'socket:/org/freedesktop/hal/udev_event'
   main: run: '/sbin/pam_console_apply /dev/ocr1 /dev/disk/by-id/scsi-36
   0a98000686f6959684a453333524174-part1 /dev/disk/by-path/ip-192.168.1.
   1:3260-iscsi-iqn.1992-08.com.netapp:sn.84187085-part1'
   main: run: '/bin/raw /dev/raw/raw1 /dev/.tmp-8-17'
   

6. Restart udev to implement the rules you have created and tested. For example:

   # start_udev
   

Verify Persistent Clusterware Storage Devices

1. Use the fdisk command to check device naming. For example:

   # fdisk -l /dev/ocr1 /dev/vote1
    
   Disk /dev/ocr1: 261 MB, 261890048 bytes
   9 heads, 56 sectors/track, 1014 cylinders
   Units = cylinders of 504 * 512 = 258048 bytes
    
   Disk /dev/ocr1 doesn't contain a valid partition table
    
   Disk /dev/vote1: 52 MB, 52403200 bytes
   2 heads, 50 sectors/track, 1023 cylinders
   Units = cylinders of 100 * 512 = 51200 bytes
    
   Disk /dev/vote1 doesn't contain a valid partition table
   

2. Use the ls command to check device ownership. For example:

   # ls -l /dev | grep -ie 'ocr\|vote'
   brw-r----- 1   root dba  8, 17 Oct 29 15:31 ocr1
   brw-rw---- 1 oracle dba  8, 65 Oct 29 15:31 vote1
   

3. Use the udevinfo command to confirm unique SCSI device identifier mappings. For example:

   # udevinfo -q all -n /dev/ocr1
   P: /block/sdb/sdb1
   N: ocr1
   S: disk/by-id/scsi-360a98000686f6959684a453333524174-part1
   S: disk/by-path/ip-192.168.1.1:3260-iscsi-iqn.1992-08.com.netapp:sn.87085-part1
   E: ID_VENDOR=NETAPP
   E: ID_MODEL=LUN
   E: ID_REVISION=0.2
   E: ID_SERIAL=360a98000686f6959684a453333524174
   E: ID_TYPE=disk
   E: ID_BUS=scsi
   E: ID_PATH=ip-192.168.1.1:3260-iscsi-iqn.1992-08.com.netapp:sn.84187085
   

4. Use the raw and ls commands to confirm raw devices are bound. For example:

   # raw -qa
   /dev/raw/raw1: bound to major 8, minor 17
   /dev/raw/raw2: bound to major 8, minor 65
   
   # ls -l /dev/raw/raw*
   crw-r----- 1 root   oinstall 162, 11 Oct 30 12:54 /dev/raw/raw1
   crw-r----- 1 oracle oinstall 162, 21 Oct 30 14:26 /dev/raw/raw2
   

After you have completed configuring and checking raw storage devices, you can proceed to install Oracle Clusterware and Oracle Real Application Clusters.

4.13.3 Relocate Oracle Clusterware Files from Raw to Block Devices

Oracle recommends that you move Oracle Clusterware files from raw devices to block devices.