search for: rdsk

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

...something to brighten everyone''s Friday. This is just a heads up since I suspect others will run into it. bob Consider the possibilities of a device named star. I added devices from the global zone to the bug zone in the usual way and rebooted the zone: <device match="/dev/zvol/rdsk/bug/devices/*"/> And I got this device: root at bug-[16:06]-> ls -l /dev/zvol/rdsk/bug/devices total 0 crw------- 1 root sys 256, 204 Nov 9 16:03 * root at bug-[16:06]-> Just to be sure the devices were there .... root at xenon-[16:07]-> ls /dev/zvol/rdsk/bug/devices...

Experts, I''m installing Oracle 9i on Solaris 10 11/06(update 3),I created some zfs volumes which will be used by oracle data file,as: # zfs create -V 200m ora_pool/controlfile01_200m # zfs create -V 800m ora_pool/system_800m ... # ls -l /dev/zvol/rdsk/ora_pool lrwxrwxrwx 1 root root 39 Apr 11 12:23 controlfile01_200m -> ../../../../devices/pseudo/zfs at 0:1c,raw lrwxrwxrwx 1 root root 39 Apr 11 13:34 system_800m -> ../../../../devices/pseudo/zfs at 0:7c,raw (Please note above,it''s just a link file!)...

...t: false pool: inherit-pkg-dir: dir: /lib inherit-pkg-dir: dir: /platform inherit-pkg-dir: dir: /sbin inherit-pkg-dir: dir: /usr inherit-pkg-dir: dir: /opt net: address: 10.1.33.91 physical: hme0 device match: /dev/zvol/rdsk/d1000pool/biscotti-vols/* device match: /dev/zvol/dsk/d1000pool/biscotti-vols/* There are 4 volumes in the dataset [/] root at tofu# zfs list -r d1000pool/biscotti-vols NAME USED AVAIL REFER MOUNTPOINT d1000pool/biscotti-vols 400M 197G 49K...

I have a system that I''m trying to bring up with a mirrored rpool. I''m using DarkStar''s ZFS Root Mirror blog post as a guide (http://darkstar-solaris.blogspot.com/2008/09/zfs-root-mirror.html). When I get to step 3 I execute: pfexec prtvtoc /dev/rdsk/c7d0s2 | fmthard -s - /dev/rdsk/c7d1s2 I get: fmthard: Cannot open device /dev/rdsk/c7d1s2 - Permission denied Any ideas as to what i might be doing wrong here? Thanks, Brian -- This message posted from opensolaris.org

...e dd to copy the first meg from the first disk to the second disk... Unfortunately there is no "d0" device name for these two disks... I''m able to make the "d0" appear on the second disk, just by adding the second disk to a zpool... sudo ls -l /dev/rdsk/c0t5000C5002637311Fd0 ls: cannot access /dev/rdsk/c0t5000C5002637311Fd0: No such file or directory sudo zpool create junk c0t5000C5002637311Fd0 sudo ls -l /dev/rdsk/c0t5000C5002637311Fd0 lrwxrwxrwx 1 root root 53 2011-07-22 14:0...

The `lofiadm'' man page describes how to export a file as a block device and then use `mkfs -F pcfs'' to create a FAT filesystem on it. Can''t I do the same thing by first creating a zvol and then creating a FAT filesystem on it? Nothing I''ve tried seems to work. Isn''t the zvol just another block device? -- -Gary Mills- -Unix Group-

Well this is a new one.... Illumos/Openindiana let me add a device as a hot spare that evidently has a different sector alignment than all of the other drives in the array. So now I''m at the point that I /need/ a hot spare and it doesn''t look like I have it. And, worse, the other spares I have are all the same model as said hot spare. Is there anything I can do with this or

OK, I''ve been putting off this question for a while now, but it eating at me, so I can''t hold off any more. I have a nice 8 gig memory stick I''ve formated with the ZFS file system. Works great on all my Solaris PC''s, but refuses to work on my Sparc processor. So I''ve formated it on my Sparc machine (Blade 2500), works great there now, but not on

I''ve hsut bought second drive for my hope PC and decided to do mirror. I''ve made pfexec zpool attach rpool c9d0s0 c13d0s0 waited for scrub and tried to install grub on second disk: $ pfexec installgrub /boot/grub/stage1 /boot/grub/stage2 /dev/rdsk/c13d0s0 cannot open/stat device /dev/rdsk/c13d0s2 $ pfexec installgrub /boot/grub/stage1 /boot/grub/stage2 /dev/rdsk/c13d0 raw device must be a root slice (not s2) What am I doing wrong? I believe that new device is SMI-labeled (I formated it and set SMI label), however I don''t know how...

Folks, I am learning more about zfs storage. It appears, zfs pool can be created on a raw disk. There is no need to create any partitions, etc. on the disk. Does this mean there is no need to run "format" on a raw disk? I have added a new disk to my system. It shows up as /dev/rdsk/c8t1d0s0. Do I need to format it before I convert it to zfs storage? Or, can I simply use it as: # zfs create MyData /dev/rdsk/c8t1d0s0 Thank you in advance for your help. Regards, Peter -- This message posted from opensolaris.org

...annot remove device links for ''exchbk/exchbk-2'': dataset is busy this is a zvol used for a comstar iscsi backend: -bash-3.2# stmfadm list-lu -v LU Name: 600144F0EAC0090000004A0A4F410001 Operational Status: Offline Provider Name : sbd Alias : /dev/zvol/rdsk/exchbk/exchbk-1 View Entry Count : 1 LU Name: 600144F0EAC0090000004A1307D20001 Operational Status: Offline Provider Name : sbd Alias : /dev/zvol/rdsk/exchbk/exchbk-2 View Entry Count : 1 i offlined everything. it''s driving me nuts.

...more drives to offer, that are not used at the moment. So I''d like to add in a mirror of c1t1d0 and c1t4d0 : # zpool add -f neptune_rpool c1t1d0 cannot label ''c1t1d0'': EFI labeled devices are not supported on root pools. OKay .. I can live with that. # prtvtoc -h /dev/rdsk/c1t0d0s0 | fmthard -s - /dev/rdsk/c1t1d0s0 fmthard: New volume table of contents now in place. # prtvtoc -h /dev/rdsk/c1t0d0s0 | fmthard -s - /dev/rdsk/c1t4d0s0 fmthard: New volume table of contents now in place. # zpool add -f neptune_rpool c1t1d0s0 cannot add to ''neptune_rpool'...

OK, I''ve got a proble I can''t solve by myself. I''ve installed solaris 11 using just one drive. Now I want to create a mirror by attached a second one tot the rpool. However, the first one has NO partition 9 but the second one does. This way the sizes differ if I create a partiotion 0 (needed because it''s a boot disk).. How can I get the second disk look

Hi all One of the rpool drives on this server died the other day, so I got a replacement that was 1 cylinder larger (60798 vs 60797). Still, I tried prtvtoc /dev/rdsk/c7d0s2 | fmthard -s - /dev/rdsk/c6d0s2 zpool replace worked and the pool resilvered within a few minutes. Now, installing grub fails. root at prv-backup:~# installgrub /boot/grub/stage1 /boot/grub/stage2 /dev/rdsk/c6d0s0 Partition 0 of the disk has an incorrect offset Unable to gather device info...

...create the test from scratch, you would notice that on the very first pass of write I/Os from ''dd'', there would be no reads. This is an artifact of using zvols as backing store for iSCSI Targets. The iSCSI Target software supports raw SCSI disks, Solaris raw devices (/dev/rdsk/....), Solaris block devices (/dev/dsk/...), zvols, SVM volumes, files in file systems, including temps. > > Simple write workload (from T2000): > > # time dd if=/dev/zero of=/dev/rdsk/ > c6t010000144F210ECC00002A004675E957d0 \ > bs=64k count=1000000 A couple of things, ma...

...h command: boot Boot device: /pci at 1c,600000/scsi at 2/disk at 0,0:a File and args: | seek failed Warning: Fcode sequence resulted in a net stack depth change of 1 Evaluating: Evaluating: The file just loaded does not appear to be executable. |1} ok | ############################### fsck /dev/rdsk/c0t0d0s0 doesn''t find any problems. So mounted this slice on /tmp/a, and # find /tmp/a/boot /tmp/a/boot /tmp/a/boot/solaris /tmp/a/boot/solaris/bin /tmp/a/boot/solaris/bin/extract_boot_filelist /tmp/a/boot/solaris/bin/create_ramdisk /tmp/a/boot/solaris/bin/root_archive /tmp/a/boot/solaris...

...om/io_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. V...

...ERR=true root at arc:~# beadm activate opensolaris-snv127 be_do_installgrub: installgrub failed for device c2t0d0s0. Unable to activate opensolaris-snv127. Unknown external error. So I tried the installgrub manually and get this: root at arc:~# installgrub /boot/grub/stage1 /boot/grub/stage2 /dev/rdsk/c2t0d0s0 cannot open/stat device /dev/rdsk/c2t0d0s2 OK, wtf? The rpool status shows both of my USB sticks alive and well at c2t0d0s0 and c1t0d0s0... But when I run "format -e" I see this: root at arc:/# format -e Searching for disks...done AVAILABLE DISK SELECTIONS: 0. c7t1d0...

IF you run solaris and opensolaris ?for example you my use c0t0d0 (for scsi disk) or c0d0 (for ide /SATA disk ) as the system disk. In default ,solaris x86 and opensolaris will use RAW driver : c0t0d0s0 (/dev/rdsk/c0t0d0s0) as the member driver of rpool. Infact, solaris2 partition can be more then one in each Hard Disk, so we also can use the RAW driver like : c0t0d0p1 (/dev/rdsk/c0t0d0p1) ,c0t0d0p2 (/dev/rdsk/c0t0d0p2) as the member driver to create a new zpool : Morpho at egoodbrac1:~# zpool create dpool...