Subscribe

SMO Unknown block device handler "device-mapper" for device

[ Edited ]

Has anyone else run into the "Unknown block device handler" when trying to add a profile in SMO? 

SnapManager for Oracle version: 3.2

snapdrive Version 5.0P1

Snapdrive Daemon Version 5.0P1

oracleasm version 2.1.5

Oracle Linux 6.2 running UEK kernel:  2.6.39-200.24

[root@test1 smo]# smo profile create -profile DEVEL2 -profile-password oracle -repository  -port 1523 -dbname grid -host grid1 -login  -username snapmanager -database  -dbname devel -host test1 -sid devel1 -osaccount oc -osgroup db -retain  -daily  -count 0 -duration 7 -hourly  -count 4 -duration 0 -monthly  -count 0 -duration 12 -weekly  -count 0 -duration 4 -snapname-pattern smo_{profile}_{db-sid}_{scope}_{mode}_{smid} -verbose

[ INFO] SMO-20020: Set password for profile "DEVEL2" in user credentials for "snapmanager".

[ INFO] SMO-13036: Starting operation Profile Create on host test1

[ INFO] SMO-13046: Operation GUID 2c948216395974ed01395974efbc0009 starting on Profile DEVEL2

[ INFO] SMO-13505: SnapDrive environment verification passed.

[ INFO] SMO-13507: JDBC verification for "OS authenticated: devel1/test1" passed.

[ INFO] SMO-13506: SQLPlus verification for database SID "devel1" passed.  Environment: [ORACLE_HOME=/u01/app/oracle/product/10.2.0/db_1]

[ INFO] SMO-07431: Saving starting state of the database: devel1(OPEN).

[ INFO] SMO-07431: Saving starting state of the database: devel1(OPEN), devel2(OPEN).

[ INFO] ORACLE-20024: Spooling control file for database devel to trace as /tmp/SM_6655651329132886243.

[ INFO] SMO-07153: Fetching archivelogs

[ WARN] SMO-07148: Archived log files are not available.

[ERROR] PLAT-00013: Unknown block device handler "device-mapper" for device (252,34)

[ERROR] FLOW-11019: Failure in Discover: PLAT-00013: Unknown block device handler "device-mapper" for device (252,34)

[ERROR] FLOW-11008: Operation failed: PLAT-00013: Unknown block device handler "device-mapper" for device (252,34)

[ERROR] SMO-05075: Profile create failed: SMO-13527: Error performing fast restore check: PLAT-00013: Unknown block device handler "device-mapper" for device (252,34).

[ INFO] SMO-20022: Deleted credentials and repository mapping for profile "DEVEL2" in user credentials for "root".

Operation Id [2c948216395974ed01395974efbc0009] failed. Error: Error performing fast restore check: PLAT-00013: Unknown block device handler "device-mapper" for device (252,34).


Re: SMO Unknown block device handler "device-mapper" for device

Hello,

Oracle Linux 6.2 is not yet supported by SDU/SMO.

Thanks,

Himanshu

Re: SMO Unknown block device handler "device-mapper" for device

According to the IMT it looks as though FC isn't a supported protocol under SMO and RH/OL 6.x.   Is there anyway to find out when or if FC will ever be supported with SMO+RHEL/OL 6.x?  dNFS on Oracle 11G seems as the way to go though haven't had much buy in from seasoned DBA's. 

Re: SMO Unknown block device handler "device-mapper" for device

It's amazing you got as far as you did given the versions of software you're running.  

Are you certain the database control file, data files, and your archive log destination all reside on a NetApp controller?

Also, do ALL the following commands work?

sanlun lun show

sanlun lun show -p

sanlun fcp show adapter all

snapdrive storage show -all

snapdrive storage show -dev

Did you provide a rescan script in /root/dynamic-lun-rescan.sh  ???

Re: SMO Unknown block device handler "device-mapper" for device

All of the commands below work except for "sanlun fcp show adapter all" and this results in an immediate segfault.

sanlun lun show

sanlun lun show -p

sanlun fcp show adapter all

snapdrive storage show -all

snapdrive storage show -dev

To give a little more background  we're trying to we're trying to run all this on Cisco UCS B200 M2 servers and the M81KR virtual interface card.  To get this hardware to work with SnapDrive I ended up patching libhbalinux to recognize the HBAs correctly. Unfortunately the patch resulted in a segfault when running the "sanlun fcp show adapter all" command though every other snapdrive command worked successfully.  I've attached the patch to this post as it doesn't look like issue had been addressed in the current lport.c source.

http://www.open-fcoe.org/git/?p=fcoe/libhbalinux.git;a=summary

To answer your question about providing a re-scan script this was never done.  The only reference to /root/dynamic-lun-rescan.sh that I was able to find was in the SDU 4.1.1 Installation and Administration Guide for Solaris.