similar to: Adjusting the volblocksize for iscsi VMFS backing stores

Hi, I am trying to understand the use of volblocksize in emulated volumes. If I create a volume in pool and I want a database engine to read and write, say 16K blocks. Should I then set volblocksize to 16K ? Regards, Patrik This message posted from opensolaris.org

Hi all! First off, if this has been discussed, please point me in that direction. I have searched high and low and really can''t find much info on the subject. We have a large-ish (200gb) UFS file system on a Sun Enterprise 250 that is being shared with samba (lots of files, mostly random IO). OS is Solaris 10u3. Disk set is 7x36gb 10k scsi, 4 internal 3 external. For several

Author: eschrock Repository: /hg/zfs-crypto/gate Revision: 8c1e3b54454c3c995f38d9fbb614dfef27d153e9 Log message: 6347421 Trying to set volblocksize on existing volume gives an unexpected error 6347492 snapshots should not pretend to have real properties Files: update: usr/src/common/zfs/zfs_prop.c

I always used IET on CentOS but I have a quick server to setup to backup some VM's, then migrate to DAS on another server and the easiest way for me will be to accomplish this via iSCSI vmfs stores. I figured I would just use the ini that ships with CentOS but have never used it against ESX, anyone do this and have experiences they care to share? Should it be trivial or are there any non

Dear all, Background: I have a ZFS volume with the incorrect volume blocksize for the filesystem (NTFS) that it is supporting. This volume contains important data that is proving impossible to copy using Windows XP Xen HVM that "owns" the data. The disparity in volume blocksize (current set to 512bytes!!) is causing significant performance problems. Question : Is there a way to

Hi, Could you help me? i have a problem with file on disperse volume. When i try to read this from mount point i recieve error, # md5sum /mnt/glfs/vmfs/slake-test-bck-m1-d1.qcow2 md5sum: /mnt/glfs/vmfs/slake-test-bck-m1-d1.qcow2: Input/output error Configuration and status of volume is: # gluster volume info vol1 Volume Name: vol1 Type: Disperse Volume ID:

Just installed Nexenta and I''ve been playing around with zfs. root at hzsilo:/tank# uname -a SunOS hzsilo 5.11 NexentaOS_20070105 i86pc i386 i86pc Solaris root at hzsilo:/tank# zfs list NAME USED AVAIL REFER MOUNTPOINT home 89.5K 219G 32K /export/home tank 330K 1.78T 51.9K /tank tank/iscsi_luns 147K

Running a zpool scrub on our production pool is showing a scrub rate of about 400K/s. (When this pool was first set up we saw rates in the MB/s range during a scrub). Both zpool iostat and an iostat -Xn show lots of idle disk times, no above average service times, no abnormally high busy percentages. Load on the box is .59. 8 x 3GHz, 32GB ram, 96 spindles arranged into raidz zdevs on OI 147.

2013/8/12 varun bhatnagar <varun292006@gmail.com>: > Hi, > > Today I was trying to start a node using libvirt on ESX (esxi-5.1) > hypervisor and I got the following error message: > > virsh # define /local/myNode/esxdomain.xml > Domain testNode defined from /local/myNode/esxdomain.xml > virsh # start testNode > error: Failed to start domain testNode > error:

Hi, Today I was trying to start a node using libvirt on ESX (esxi-5.1) hypervisor and I got the following error message: *virsh # define /local/myNode/esxdomain.xml* *Domain testNode defined from /local/myNode/esxdomain.xml* *virsh # start testNode* *error: Failed to start domain testNode* *error: internal error: Could not start domain: GenericVmConfigFault - Cannot open the disk

Thanks a ton for the reply Matthias. I am little confused here. How to add volume on my esx server using virsh? I did SCP and copied my vmdk image to [datastore1] testNode/cluster.vmdk and also modified my xml file as you suggested. Now when I tried starting the node it gave me an error message saying: "error: Failed to start testNode error: internal error: Could not start domain:

To Whom It May concern: I found that the following error is caused by adding a scsi disk to install the os, I remove the scsi disk and the error remove but still report 'out of memory': virsh # dumpxml win2003_122 internal error Invalid or not yet handled value '/vmfs/devices/genscsi/mp x.vmhba0:C0:T1:L0' for VMX entry 'scsi0:1.fileName' virsh # list --all Id Name

To Whom It May Concern: I use virsh windows 0.9.3 to connect an esx server 4.0 with no_verify=1. The Esx server is intel 2 x 3.19 GHZ CPU, 8G memroy and 2 TB hard disk. following is my execute commands and results. virsh -c esx://xxx.xxx.xxx.x?no_verify=1 virsh # list all Id Name State ---------------------------------- 80 win2003_122 running virsh # nodeinfo error:

Updates commit 1d38216d20141cef9ce83ca4ddbe9c79f5da4f39. --- v2v/virt-v2v.pod | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/v2v/virt-v2v.pod b/v2v/virt-v2v.pod index d39609cf8..b2face339 100644 --- a/v2v/virt-v2v.pod +++ b/v2v/virt-v2v.pod @@ -126,7 +126,7 @@ a local file. virt-v2v \ -i vmx -it ssh \ -

On Mon, Apr 19, 2010 at 10:17:07PM +0800, Wilkinson, Alex wrote: > The aforementioned article says that libguestfs supports VMware's > VMDKs. This is partly true. We rely on qemu's support for VMDK which is rather sketchy. In particular, qemu cannot handle some VMDKs from ESX 4.0. However ... > So if these VMDKs live on a vmfs on an ESX server, what do > you recomend as

I''m looking to move our file storage from Windows to Opensolaris/zfs. The windows box will be connected through 10g for iscsi to the storage. The windows box will continue to serve the windows clients and will be hosting approximately 4TB of data. The physical box is a sunfire x4240, single AMD 2435 processor, 16G ram, LSI 3801E HBA, ixgbe 10g card. I''m looking for suggestions

On Friday, 8 December 2017 17:02:30 CET Richard W.M. Jones wrote: > This enhances the existing VMX input support allowing it to be > used over SSH to the ESXi server. > > The original command (for local .vmx files) was: > > $ virt-v2v -i vmx guest.vmx -o local -os /var/tmp > > Adding ‘-it ssh’ and using an SSH remote path gives the new syntax: > > $ virt-v2v \

Hello All, The version of R I am using is as follows > version _ platform x86_64-pc-linux-gnu arch x86_64 os linux-gnu system x86_64, linux-gnu status major 2 minor 14.1 year 2011 month 12 day 22 svn rev 57956 language R version.string R version 2.14.1 (2011-12-22) I just few days

This enhances the existing VMX input support allowing it to be used over SSH to the ESXi server. The original command (for local .vmx files) was: $ virt-v2v -i vmx guest.vmx -o local -os /var/tmp Adding ‘-it ssh’ and using an SSH remote path gives the new syntax: $ virt-v2v \ -i vmx -it ssh \ "root@esxi.example.com:/vmfs/volumes/datastore1/guest/guest.vmx" \ -o local

https://bugzilla.samba.org/show_bug.cgi?id=8177 Summary: Problems with big sparsed files Product: rsync Version: 3.0.8 Platform: x64 OS/Version: Linux Status: NEW Severity: normal Priority: P5 Component: core AssignedTo: wayned at samba.org ReportedBy: joluinfante at gmail.com