search for: c1t0d0s2

...eted after 0h48m with 15 errors on Mon Jul 12 15:41:50 2010 config: NAME STATE READ WRITE CKSUM zroot DEGRADED 18 0 0 mirror DEGRADED 44 0 23 c1t1d0s2 DEGRADED 74 0 23 too many errors c1t0d0s2 ONLINE 0 0 67 29.8G resilvered errors: Permanent errors have been detected in the following files: zroot/packages:<0xad58> zroot/packages:<0x11477> zroot/packages:<0x2531d> <0x6e>:<0xc0f2> <0x6e>:<0...

Hi All, ZPOOL / ZFS commands writes EFI label on a device if we create ZPOOL/ZFS fs on it. Is it true ? I formatted a device with VTOC lable and I created a ZFS file system on it. Now which label the ZFS device has ? is it old VTOC or EFI ? After creating the ZFS file system on a VTOC labeled disk, I am seeing the following warning messages. Feb 3 07:47:00 scoobyb

..._technologies/USB-Faq.html Is this information still valid ? Under ZFS FAQ there is no mention of this topic, a good idea is to add a section about ZFS on mobile devices. Thanks, Stefan # rmformat Looking for devices... 1. Volmgt Node: /vol/dev/aliases/cdrom0 Logical Node: /dev/rdsk/c1t0d0s2 Physical Node: /pci at 0,0/pci-ide at 1f,2/ide at 1/sd at 0,0 Connected Device: MATSHITA UJDA765 DVD/CDRW 1.70 Device Type: DVD Reader Bus: IDE Size: <Unknown> Label: <Unknown> Access permissions: <Unknown> 2. Volmgt Nod...

Banging my head against a Seagate 3TB USB3 drive. Its marketing name is: Seagate Expansion 3 TB USB 3.0 Desktop External Hard Drive STAY3000102 format(1M) shows it identify itself as: Seagate-External-SG11-2.73TB Under both Solaris 10 and Solaris 11x, I receive the evil message: | I/O request is not aligned with 4096 disk sector size. | It is handled through Read Modify Write but the performance

...;'m running this from my user (not root) account. I''m using qemu-img to create my hard drive images. Here''s the cut and paste from gnome-terminal: bash-3.2$ uname -a SunOS pacifica 5.11 snv_87 i86pc i386 i86xpv bash-3.2$ virt-install --name Vista1 -r 1024 --location /dev/dsk/c1t0d0s2 --file $HOME/guests/Vista1.img --vnc Traceback (most recent call last): File "/usr/bin/virt-install", line 657, in ? main() File "/usr/bin/virt-install", line 509, in main conn = libvirt.open(options.connect) File "/usr/lib/python2.4/vendor-packages/libvirt.py...

...cover from this or are they SOL? Thanks in advance # zpool status no pools available # zpool import # ls /etc/zfs # ls /dev/dsk c0t0d0s0 c0t0d0s3 c0t0d0s6 c1t0d0s1 c1t0d0s4 c1t0d0s7 c1t1d0s2 c1t1d0s5 c1t2d0 c1t2d0s2 c1t2d0s5 c1t3d0s0 c1t3d0s3 c1t3d0s6 c0t0d0s1 c0t0d0s4 c0t0d0s7 c1t0d0s2 c1t0d0s5 c1t1d0s0 c1t1d0s3 c1t1d0s6 c1t2d0s0 c1t2d0s3 c1t2d0s6 c1t3d0s1 c1t3d0s4 c0t0d0s2 c0t0d0s5 c1t0d0s0 c1t0d0s3 c1t0d0s6 c1t1d0s1 c1t1d0s4 c1t1d0s7 c1t2d0s1 c1t2d0s4 c1t3d0 c1t3d0s2 c1t3d0s5 # format Searching for disks...done AVAILABLE DISK SELECTIONS: 0. c1t0...

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 --

I am trying to create a DomU guest domain to run snv77 over an a snv77 host, following the instructions and example in http://opensolaris.org/os/community/xen/docs/virt-install.html. I booted the xVM partition (selected xVM from the grub menu). virt-install spends 2 or 3 minutes after "Starting install ..." then fails. here''s what I get: bash-3.2# virt-install --name

Hi All, I had a slice with zfs file system which I want to mirror, I followed the procedure mentioned in the amin guide I am getting this error. Can you tell me what I did wrong? root # zpool list NAME SIZE USED AVAIL CAP HEALTH ALTROOT export 254G 230K 254G 0% ONLINE - root # echo |format Searching for disks...done

As mentioned last night, we''ve been reviewing a proposal for hot spare support in ZFS. Below you can find a current draft of the proposed interfaces. This has not yet been submitted for ARC review, but comments are welcome. Note that this does not include any enhanced FMA diagnosis to determine when a device is "faulted". This will come in a follow-on project, of which some