search for: dsk

...herwise restore the entire pool from backup. see: http://www.sun.com/msg/ZFS-8000-8A scrub: scrub completed with 66 errors on Fri Mar 23 12:52:36 2007 config: NAME STATE READ WRITE CKSUM test ONLINE 0 0 134 /dev/md/dsk/d100 ONLINE 0 0 134 errors: 66 data errors, use ''-v'' for a list bash-3.00# Disks are from Clariion CX3-40 with FC 15K disks using MPxIO (2x 4Gb links). I was changing watermarks for cache on the array and now I wonder - the array or SVM+ZFS? I''m a little...

...have a problem confusing me. I hope someone can help me with it. I followed a "best practise" - I think - using dedicated zfs filesystems for my virtual machines. Commands (for completion): [i]zfs create rpool/vms[/i] [i]zfs create rpool/vms/vm1[/i] [i] zfs create -V 10G rpool/vms/vm1/vm1-dsk[/i] This command creates the file system [i]/rpool/vms/vm1/vm1-dsk[/i] and the according [i]/dev/zvol/dsk/rpool/vms/vm1/vm1-dsk[/i]. If I delete a VM i set up using this filesystem via[i] virsh undefine vm1[/i] the [i]/rpool/vms/vm1/vm1-dsk[/i] gets also deleted, but the [i]/dev/zvol/dsk/rpool/vm...

All, The attached script is causing the following error message ... bash-3.00# ./zmon_bug.d dtrace: error on enabled probe ID 2 (ID 4394: fbt:genunix:copen:entry): invalid address (0xfd91747f) in predicate at DIF offset 120 dtrace: error on enabled probe ID 2 (ID 4394: fbt:genunix:copen:entry): invalid address (0xfef81a3f) in predicate at DIF offset 120 Any ideas? thxs Joe --

...ause the number is to large for perl so it returns a negative number. meh wasnt important enough to try to figure out. (the info below has NOTHING to do with my disk problem above, its a happy and health server that i wrote the tool on) - find newest tgx number bash-3.00# /tmp/findUberBlock /dev/dsk/c0t1d0 -n block=148 (0025000) transaction=15980419 - print verbose output bash-3.00# /tmp/findUberBlock /dev/dsk/c0t1d0 -n -v block=148 (0025000) zfs_ver=3 (0003 0000 0000 0000) transaction=15980419 (d783 00f3 0000 0000) guid_sum=-148614...

...ready was a partition on the installation disk. An old dataset that I deleted since i gave it a slightly different name than I intended is not removed under /dev. I should not have used that name, but two device links should perhaps not point to the same device ether.... zfs list |grep xvm/dsk zpool01/xvm/dsk 25.0G 2.63T 24.0K /zpool01/xvm/dsk zpool01/xvm/dsk/osol01-dsk01 10G 2.64T 2.53G - zpool01/xvm/dsk/ubuntu01-dsk01 10G 2.64T 21.3K - # ls -l /dev/zvol/dsk/zpool01/xvm/dsk total 3 lrwxrwxrwx 1 root root 41 Feb 10 18:19 osol01-dsk01 - &...

...Sorry I couldn't be of more help and I hope someone chimes in with the correct solution soon. On Wed, Jan 3, 2018 at 4:48 PM, Son Tuan VU <sontuan.vu119 at gmail.com> wrote: > Hello again, > > After digging a little deeper to this, I guess this is the reason: > > lit.py: /dsk/l1/misc/vusontuan/llvm/projects/libcxxabi/test/lit.cfg:58: > note: Using configuration variant: libcxxabi > lit.py: /dsk/l1/misc/vusontuan/llvm/projects/libcxx/utils/libcxx/test/config.py:297: > note: inferred use_system_cxx_lib as: None > lit.py: /dsk/l1/misc/vusontuan/llvm/projects/li...

Hello, I have just built LLVM with CMake by following these instructions https://llvm.org/docs/GettingStarted.html#getting-started-quickly-a-summary and I am trying to run the regression tests using "make check-all" but there are some unexpected failures in libcxx and libcxxabi. Here's the test log: Expected Passes : 40745 Expected Failures : 258 Unsupported Tests : 1594

...rom=/root/bkup_excludes -avz --delete -e "ssh -i /root/cron/aebkup-rsync-key" --link-dest=/aeprodbk/current root@aeprod:/ /aeprodbk/$d >>$d.logdate > /aeprodbk/$d/bkupdate rm -f /aeprodbk/current ln -s /aeprodbk/$d /aeprodbk/current 2nd script with no storage saving d=`date +%d` dsk=/media/disk cd $dsk date > /usb$d.log rsync --exclude-from=/root/bkup_excludes -av --delete --link-dest=$dsk/current /aeprodbk/$d $dsk >> /usb$d.log date>$dsk/$d/bkupdate date>$dsk/bkupdate rm -f $dsk/current ln -s $dsk/$d $dsk/current -- View this message in context: http://www.n...

Hello, I am trying to configure ZFS with IBM sdd. IBM sdd is like powerpath, MPXIO or VxDMP. Here is the error message when I try to create my pool: bash-3.00# zpool create tank /dev/dsk/vpath1a warning: device in use checking failed: No such device internal error: unexpected error 22 at line 446 of ../common/libzfs_pool.c bash-3.00# zpool create tank /dev/dsk/vpath1c cannot open ''/dev/dsk/vpath1c'': I/O error bash-3.00# zpool create tank vpath1 cannot open '...

...exporting a vmdk 1.1 optimized stream file. Thanks, Susan ------------------------------ Examples: Here are the interfaces for import/export/convert: # vdiskadm help import import - import a zvol, raw file, or virtual disk USAGE: vdiskadm import [-fnpqm] [-x <type>] -d <file|zvol|dsk> [-t <type[:opt]>] vdname EXAMPLE: vdiskadm import -d /downloads/image.vmdk /export/new_guests/disk1 ---- The [-fnpqm] flags are unchanged from the original vdiskadm import and are used mostly by virt-convert. -x gives the optional vdisk import file or block device type (vmdk, raw, vh...

Hi, im trying to attach another volume aka disk to win HVM, however it doesn''t seem to work: + xm block-attach win2008ss phy:/dev/zvol/dsk/pool1/win2008ss.dsk2 \ hdd:disk w 0 results in: elkner.sol ~ > + xm block-list win2008ss --long (0 (vbd (uuid 7cb8fadf-619d-dde6-bda9-dcc18023c7d5) (bootable 1) (devid 768) (driver paravirtualised) (dev hda:disk) (uname phy:/dev/zvol/dsk/poo...

After multiple power outages caused by storms coming through, I can no longer access /dev/zvol/dsk/poolname, which are hold l2arc and slog devices in another pool I don''t think this is related, since I the pools are ofline pending access to the volumes. I tried running find /dev/zvol/dsk/poolname -type f and here is the stack, hopefully this someone a hint at what the issue is, I have...

...idays, and back on this issue. I've learned a lot. > > I've learned how to use the blockcopy command to create a local copy in a > simple disk file: > > virsh dumpxml my_domain > my_domain.xml > virsh undefine my_domain > virsh blockcopy --domain my_domain vda $PWD/dsk.copy.qcow2 --wait --verbose > --finish > virsh define my_domain.xml Yes, that's correct. > and the resulting copy in dsk.copy.qcow2 is, indeed, bootable. It appears to > be a perfect copy, as I expect it to be. Good, this time you find it bootable, compared to your previous test....

...post holidays. Back from the holidays, and back on this issue. I've learned a lot. I've learned how to use the blockcopy command to create a local copy in a simple disk file: virsh dumpxml my_domain > my_domain.xml virsh undefine my_domain virsh blockcopy --domain my_domain vda $PWD/dsk.copy.qcow2 --wait --verbose --finish virsh define my_domain.xml and the resulting copy in dsk.copy.qcow2 is, indeed, bootable. It appears to be a perfect copy, as I expect it to be. But while I see (per Kashyap's article, etc) that it can be useful in certain scenarios, it's not inter...

I am experimenting with the blockcopy command, and after figuring out how to integrate qemu-nbd, nbd-client and dumpxml/undefine/blockcopy/define/et. al. I have one remaining question: What's the point? The "replication" disk file is not, from what I can ascertain, bootable. I expect this operation to create a pristine copy of my source qcow2 file (at a given point in time)

...add more. It is easy to add for vm but how can i update fs in os? I cannot use autoexpand because it doesn''t implemented in my system: $ uname -a SunOS sopen 5.11 snv_111b i86pc i386 i86pc If it was 171 it would be grate, right? Doing following: o added new virtual HDD (it becomes /dev/rdsk/c7d1s0) o run format, write label # zpool status pool: rpool state: ONLINE scrub: scrub completed after 0h10m with 0 errors on Fri May 28 16:47:05 2010 config: NAME STATE READ WRITE CKSUM rpool ONLINE 0 0 0 c7d0s0 ONLINE 0 0 0 err...

...7 ????????????????ashift=9 ????????????????asize=20914156863488 ????????????????is_log=0 ????????????????children[0] ????????????????????????type=''disk'' ????????????????????????id=0 ????????????????????????guid=640233961847538260 ????????????????????????path=''/dev/dsk/c2t3d0s0'' ????????????????????????devid=''id1,sd at t49455400000000000000000001000000cf1900000e000000/a'' ????????????????????????phys_path=''/iscsi/disk at 0000iqn.2006-03.com.domain-SAN10001,0:a'' ????????????????????????whole_disk=1 ??????????????????...

On 01/08/2015 12:44 PM, Gary R Hook wrote: > I've learned how to use the blockcopy command to create a local copy in > a simple disk file: > > virsh dumpxml my_domain > my_domain.xml > virsh undefine my_domain > virsh blockcopy --domain my_domain vda $PWD/dsk.copy.qcow2 --wait > --verbose --finish > virsh define my_domain.xml > > and the resulting copy in dsk.copy.qcow2 is, indeed, bootable. It > appears to be a perfect copy, as I expect it to be. > > But while I see (per Kashyap's article, etc) that it can be useful in >...

...ay to restore it. # cd /tmp # dd if=/dev/zero of=junk bs=1024k count=64 # zpool create junkpool /tmp/junk log your_new_log_device # zpool export junkpool ** Find your old disks ** You need one of your pool''s devices to read the vdev_label. It will generally look something like this /dev/rdsk/cXtXdXs0 (or cXdXs0). Check out the label with: # zdb -l /dev/rdsk/cXtXdXs0 (You can also find your old disks with zpool import on a livecd) ** Fix it up! ** For disk based log devices: # ./logfix /dev/rdsk/cXtXdXs0 /dev/rdsk/${your_new_log_device}s0 guid For file based log devices (this will be s...

...? version = 0x0 ??? ??? scheme = zfs ??? ??? pool = 0x4406b127a905c5be ??? ??? vdev = 0xe7dce33be87eeca7 ??? (end detector) ??? pool = rsgis ??? pool_guid = 0x4406b127a905c5be ??? pool_context = 1 ??? pool_failmode = wait ??? vdev_guid = 0xe7dce33be87eeca7 ??? vdev_type = disk ??? vdev_path = /dev/dsk/c9t0d0s0 ??? vdev_devid = id1,sd at AHITACHI_HDS7225SCSUN250G_0719BN9E3K=VFA100R1DN9E3K/a ??? parent_guid = 0xb89f3c5a72a22939 ??? parent_type = mirror ??? prev_state = 0x1 ??? __ttl = 0x1 ??? __tod = 0x4c40be67 0x272aef9b Jul 16 2010 15:17:43.657125080 ereport.fs.zfs.vdev.open_failed nvlist versi...