About iSCSI storage in ROSEHA cluster
2012-11-22 21:24
288 查看
This will discuss the share storage of iscsi in RoseHA cluster.When I configured the service of the volume settings, I add the path and mount point in the configuration tool:
![](http://img1.51cto.com/attachment/201211/212030971.jpg)
As we can see above, I configured multipath service and LVM for this lun. So it came across with the multipath service and lvm service , and of course the iscsi .
When I tried to bring the database service, it can’t mount the lun and throw out many errors on I/O. that’s tricky.
![](http://img1.51cto.com/attachment/201211/212118959.jpg)
![](http://img1.51cto.com/attachment/201211/212156407.jpg)
Every time when I run the script it generates this error.
As we know, iscsi storage needs to first be DISCOVERED, then LOGIN the target. So if we use iscsi for shared storage, we should bear in mind of this. So I prefer to FC storage not only for performance but also for ease of deploying.
It says I can’t mount the lun:
![](http://img1.51cto.com/attachment/201211/212257140.jpg)
For RoseHA cluster, if you want to switch the service to another server, then you should first mount the shared lun, then the script will start the service.
My problem on this issue is that every time when I switch the service, it didn’t first mount the lun, but run the start script, I put the DISCOVER and LOGIN command in this script, so when the cluster can’t determine the shared lun with the monitor script, of course, every time it runs the stop script, so never made it successful.
After knowing this, I know I have to make some changes on the strategy on mounting the shared lun.
Firstly, delete the “volume setting” entry, make the cluster not to check the shared lun when it check the resource when take over cluster service, but put it in the script,
Let the script itself to manage such resource as IP resource, shared lun resource, script resource etc.
![](http://img1.51cto.com/attachment/201211/212351673.jpg)
In the start script, I first discover and login the target, then to restart the multipath service, and followed with scan the lvms, and active the lun, finally , I mount it here but not in the following script. This works out!
With FC storage, I could get rid of so many troubles!
![](http://img1.51cto.com/attachment/201211/212030971.jpg)
As we can see above, I configured multipath service and LVM for this lun. So it came across with the multipath service and lvm service , and of course the iscsi .
When I tried to bring the database service, it can’t mount the lun and throw out many errors on I/O. that’s tricky.
![](http://img1.51cto.com/attachment/201211/212118959.jpg)
![](http://img1.51cto.com/attachment/201211/212156407.jpg)
Every time when I run the script it generates this error.
As we know, iscsi storage needs to first be DISCOVERED, then LOGIN the target. So if we use iscsi for shared storage, we should bear in mind of this. So I prefer to FC storage not only for performance but also for ease of deploying.
It says I can’t mount the lun:
![](http://img1.51cto.com/attachment/201211/212257140.jpg)
For RoseHA cluster, if you want to switch the service to another server, then you should first mount the shared lun, then the script will start the service.
My problem on this issue is that every time when I switch the service, it didn’t first mount the lun, but run the start script, I put the DISCOVER and LOGIN command in this script, so when the cluster can’t determine the shared lun with the monitor script, of course, every time it runs the stop script, so never made it successful.
After knowing this, I know I have to make some changes on the strategy on mounting the shared lun.
Firstly, delete the “volume setting” entry, make the cluster not to check the shared lun when it check the resource when take over cluster service, but put it in the script,
Let the script itself to manage such resource as IP resource, shared lun resource, script resource etc.
![](http://img1.51cto.com/attachment/201211/212351673.jpg)
In the start script, I first discover and login the target, then to restart the multipath service, and followed with scan the lvms, and active the lun, finally , I mount it here but not in the following script. This works out!
With FC storage, I could get rid of so many troubles!
相关文章推荐
- Configure Netbackup 7.1 HA In Solaris Cluster
- About iSCSI Storage
- 配置Windows Cluster with windows storage service and iSCSI
- More about “PartitionKey”&"RowKey” in windows azure table storage
- oVirt guest | VM & HOST HA in one Cluster
- About Oracle Cluster Registry
- [MST] Store Store in Local Storage
- There is an obvious Error in npp src. ( About FORTRAN Syntax Highlighting And Fold )
- Interview with Dustin Kirkland, Ubuntu Core Developer about encryption in Ubuntu
- MariaDB Galera Cluster with HA Proxy and Keepalived on Cents 6
- ClusterId read in ZooKeeper is null 处理
- PL/SQL Scripts Used in Migrating to ASM Storage
- An article about Equals and GetHashCode functions in C#
- VMware HA Admission Control Policy: Percentage of Cluster Resources Reserved 设置
- Item 14: Think carefully about copying behavior in resource-managing classes.(Effective C++)
- add new node in hadoop without restarting the cluster
- This file is about changes in Emacs version 24.
- 关于PHP浮点数你应该知道的(All ‘bogus’ about the float in PHP)
- Step-by-step for Storage Spaces Tiering in Windows Server 2012 R2
- Considerations for Multi Site Cluster in Windows server 2012 (Part 2)