I created an iSCSI volume in Openfiler.
Volume name Volume description Volume size File system type File system size FS used space FS free space Delete Properties Snapshots
backup Backup Storage 3717536 MB iSCSI Not applicable Not applicable Not applicable In use Edit Create
When I create the partition in VMware, it sets the size of the partition to 1.55TB even t
Let me start by saying I am somewhat of a Vmware novice, I know just enought to manage and create servers at a basic level from the vSphere client.
I have a VMWare server, ESX 4.0 connected over iSCSI to a SAN. The SAN is being used as storage for both RDMs and VMFS volumes.
The SAN has died and I ordered a new one.
We have a Hyper-V 3.0 Failover Cluster (2 servers) each running Windows Server 2012 RC. We have Shared Storage (HP P4300) which is reporting no errors and is working just fine as either a standalone disk or witness disk within the cluster.
I'm setting up a new file server using the same storage configuration as my existing server, but the procedure is failing and i cannot figure out why. my goal is to create a TrueCrypt volume on top of a RAID 10 volume. however, when i start truecrypt -c, it destroys the RAID volume.
I added a Volume group in Proxmox VE as Storage for KVM VMs. A new Logical Volume will be created for each VM, but in Proxmox VE under The Defined Storage which shows list of created Logical Volumes I see my Logical Volume marked as RAW format. Is this a RAW image or a Logical Volume (LVM)?
I will admit that my understanding of the following is a little hazy, however, it seems that if I create a new logical volume as follows
Code:
sudo lvcreate -L1G -s -n livesnapshots /dev/kvm-server/vm-storage
It creates successfully. I then mount this to /mnt/snapshots and sure enough I can see the file system as existing in the original volume.
This article takes you through the necessary steps to extend a raw libvirt storage volume that is part of a libvirt storage pool on a Debian Squeeze GNU/Linux system. A libvirt storage volume is essentially a virtual raw hard-disk image that is used by a virtual machine.
I don't know if I'm missing something but when I'm mounting additional iSCSI volumes to a said server to add additional storage to a server I'm not seeing a way to mount the volume after running a discovery command.
The reasoning I want to be able to do this is that we're running an application that would require downtime everytime we add additional iSCSI volumes to this server.
ya so my fn+vol moves the volume scale up and down but does not actually change the volume
all the other fn's work like skipping songs stopping, pausing, wi-fi on and off.... just my volume doesn't change....
i have to use alsamixer in terminal to adjust my volume...
what should i do??
Email this page