Forum
Welcome, Guest
Username: Password: Remember me
  • Page:
  • 1
  • 2

TOPIC: Different sized storage

Different sized storage 1 year 4 months ago #1347

We're about to install HA lizard. 1 of our servers have 4tb WD whereas the other is a 3tb seagate.

What happens to the other 1tb of storage and more importantly, what would be the steps we need to take someday if we wish to replace the 3tb drives with the same 4tb drives? Will we be able to make use of additional storage as time goes on?
The administrator has disabled public write access.

Different sized storage 1 year 4 months ago #1348

You should verify this with DRBD. There are some risks associated with different size block devices. First, you should introduce the smaller one to DRBD first, otherwise you will have problems when introducing a 4TB drive first and then connecting a 3TB drive.

Not sure whether the drbd metadata can be changed after the drives have been initialized. This would be required to introduce a larger drive in the future.
The administrator has disabled public write access.

Different sized storage 1 year 4 months ago #1350

Hi Salvatore, thank you for your feedback! We're more than content with having only the 3gb storage available to us for now. I also understand the reasoning for then first setting up the 3tb server as master.

I am however a little worried with your remark to the risk associated? If you don't mind me asking, can you elaborate or give me a resource I can view to understand this better? We most certainly do not want to put any data in danger (not sure if this is part of the risk associated)?
The administrator has disabled public write access.

Different sized storage 1 year 4 months ago #1351

The comment regarding risk was related to the order that disks are introduced. Since we use DRBD for replication, you should take a look at DRBD's documentation for more clarity on the issue.
The administrator has disabled public write access.

Different sized storage 1 year 4 months ago #1354

I've gone to the DC today and noticed some strange behaviour. I decided to not let Xen create the SR's but created them manually afterwards via gdisk (GTP partition) as a LVM filesystem partition.

During installion on the first server I made mistake and pressed CTRL+c after it asked me to press enter to continue when it asked me to confirm deleting the strorage repository. When I tried to do the installation again it said that it could not find the SR and when I entered /dev/sda4 manually it kept saying it was busy or could not access the SR.

As I was unsure what to do next I figured I'd reinstall on the same server but this time chose that Xenserver create the SR - After I went through all of the steps and was prompted if I wanted to delete the local SR I said yes but it indicated there was no storage. This was on a complete clean installation of Xenserver 7.2 and I opted for XS to create the SR.

I'm going back to the datacenter tomorrow but curious why this would be happening? Also, is there a better way to recover from a broken installation than redoing the entire fresh install of Xen?
The administrator has disabled public write access.

Different sized storage 1 year 4 months ago #1355

By making use of the uninstaller I was able to remove HALizard and start the installation afresh. I again reinstalled xenserver, chose that it creates the storage and again during installation got a message that there is no local storage. Again the installation was completed on the slave perfectly (it picked up the storage etc).

Here is the installation output for the master (the one which indicates that there is no storage):

Select replication inerface
Enter 0 for interface xapi1
Enter 1 for interface xapi2
Enter 2 for interface xapi3
Enter 3 for interface xapi4
Enter 0 - 3 for the desired Replication Interface
2
Interface xapi3 selected
Local temp folder /tmp/halizard_tmp_ found
Downloading the latest stable version of HA-Lizard to /tmp/halizard_tmp_
Downloading the latest stable version of iSCSI-HA to /tmp/halizard_tmp_
Unpacking iSCSI-HA
Unpacking HA-Lizard
Updating Firewall Rules
iptables: Saving firewall rules to /etc/sysconfig/iptables:[ OK ]
Redirecting to /bin/systemctl restart iptables.service
Installing DRBD packages
Note: Forwarding request to 'systemctl disable drbd.service'.
Installing HA-Lizard High Availability Component
Installing iSCSI-HA Storage High Availability Component
Installing iSCSI Target Framework
| Convert local storage to iSCSI-HA storage? <yes or no> |
yes
Failed to locate SR for local storage
| Error converting local SR to usable block device |
| Enter full path to backing block device to be |
| used for HA storage and press <Enter> (ex. /dev/sdb) |
/dev/sda7
Backing block device set to /dev/sda7

| Enter LUN to be used for exposing iSCSI storage and press <Enter> |
| (Leave blank to accept default value of 10) |

LUN set to 10

Backing up LVM configuration file /etc/lvm/lvm.conf to /etc/lvm/lvm.conf.halizard_restore
Backing up LVM configuration file /etc/lvm/master/lvm.conf to /etc/lvm/master/lvm.conf.halizard_restore
| Enter heuristic IP address used by HA-Lizard. |
| This can be any IP address reachable by this host |
| by traversing the XenServer management network and press <Enter> |
*****
Heuristic IP set to *****

Press <enter> to continue installation

Successfully updated FENCE_ENABLED to value: 1
Successfully updated FENCE_HEURISTICS_IPS to value: ********
Successfully updated FENCE_MIN_HOSTS to value: 2
Successfully updated FENCE_QUORUM_REQUIRED to value: 1
Successfully updated FENCE_USE_IP_HEURISTICS to value: 1
Successfully updated MONITOR_DELAY to value: 15
Successfully updated MONITOR_MAX_STARTS to value: 20
Successfully updated XAPI_COUNT to value: 2
Successfully updated XAPI_DELAY to value: 10
Sending ARP update on replication interface
ARP: send_network_bridge_arp: Processing ARP update for interface [ xapi3 ]
ARP: send_network_bridge_arp: IP address list for [ xapi3 ] = [ 10.4.0.1 ]
ARP: send_network_bridge_arp: Updating ARP for device [ xapi3 ] IP [ 10.4.0.1 ]
ARPING 10.4.0.1 from 10.4.0.1 xapi3
Sent 1 probes (1 broadcast(s))
Received 0 response(s)
| Initializing DRBD.. This host will wait until its peer connects. |
| Installation will resume after the DRBD peers connect |
1+0 records in
1+0 records out
1048576 bytes (1.0 MB) copied, 0.00151058 s, 694 MB/s
open(/dev/sda7) failed: Device or resource busy

Exclusive open failed. Do it anyways?
[need to type 'yes' to confirm] yes

open(/dev/sda7) failed: Device or resource busy

Exclusive open failed. Do it anyways?
[need to type 'yes' to confirm] yes

You want me to create a v08 style flexible-size internal meta data block.
There appears to be a v08 flexible-size internal meta data block
already in place on /dev/sda7 at byte offset 2955473297408

Do you really want to overwrite the existing meta-data?
[need to type 'yes' to confirm] yes

initializing activity log
NOT initializing bitmap
Writing meta data...
New drbd meta data block successfully created.
open(/dev/sda7) failed: Device or resource busy

Exclusive open failed. Do it anyways?
[need to type 'yes' to confirm] yes

Starting DRBD resources: [
create res: iscsi1
prepare disk: iscsi1
adjust disk: iscsi1Operation canceled.
:failed(apply-al:20)
adjust net: iscsi1
]
..........
***************************************************************
DRBD's startup script waits for the peer node(s) to appear.
- If this node was already a degraded cluster before the
reboot, the timeout is 0 seconds. [degr-wfc-timeout]
- If the peer was available before the reboot, the timeout
is 0 seconds. [wfc-timeout]
(These values are for resource 'iscsi1'; 0 sec -> wait forever)
To abort waiting enter 'yes' [ 117]:
.
Synchronizing storage with peer/slave host1: State change failed: (-2) Need access to UpToDate data
Command 'drbdsetup-84 primary 1 --overwrite-data-of-peer' terminated with exit code 17
Starting ha-lizard (via systemctl): [ OK ]
Starting iscsi-ha (via systemctl): [ OK ]
| The final step is to create a new storage repository of type iSCSI from XenCenter |
| targeted to 10.4.0.3 to complete the noSAN installation. |

Any ideas what might be going on here?
The administrator has disabled public write access.
  • Page:
  • 1
  • 2
Time to create page: 0.148 seconds