similar to: why is zpool import still hanging in opensolaris 2009.06 ??? no fix yet ???

Hi, I am posting my question to both storage-discuss and zfs-discuss as I am not quite sure what is causing the messages I am receiving. I have recently migrated my zfs volume from b104 to b134 and upgraded it from zfs version 14 to 22. It consist of two zvol''s ''vol01/zvol01'' and ''vol01/zvol02''. During zpool import I am getting a non-zero exit code,

I have a number of systems running solaris10 and i see the package and binary for dtrace installed however whenever we try to run anything we get this error dtrace: failed to initialize dtrace: DTrace device not available on system the only system in which i dont have this error is the development server that has the full solaris 10 install while others are minimized, do i need additional

Is there a card for OpenSolaris 2009.06 SPARC that will do SATA correctly yet? Need it for a super cheapie, low expectations, SunBlade 100 filer, so I think it has to be notched for 5v PCI slot, iirc. I''m OK with slow -- main goals here are power saving (sleep all 4 disks) and 1TB+ space. Oh, and I hate to be an old head, but I don''t want a peecee. They still scare me :)

Hi all, I moved from Sol 10 Update4 to update 6. Before doing this I exported both of my zpools, and replace the discs containing the ufs root on with two new discs (these discs did not have any zpool /zfs info and are raid mirrored in hardware) Once I had installed update6 I did a zpool import, but it only shows (and was able to) import one of the two pools. Looking at dmesg it appears as

Hi, We are seeing more long delays in zpool import, say, 4~5 or even 25~30 minutes, especially when backup jobs are going on in the FC SAN the LUNs resides (no iSCSI LUNs yet). On the same node for the LUNs of the same array, some pools takes a few seconds, but minutes for some. the pattern seems random to me so far. It''s first noticed soon after being upgraded to Solaris 10 U6

Hello, on a v20z, we have as DOM 0 a Solaris XEN on snv44 64bits and we have as DOM U a Solaris XEN on snv44 64 bits. We then install a pseudo driver in the Solaris DOM 1 XEN snv44: installation is ok and driver works as expected. But on reboot of DOM 1, the driver is no more there (in modinfo, driver not found). Is there something special to do after a pseudo driver installation in a Solaris

Hello, Due to a power outage our file server running FreeBSD 8.0p2 will no longer come up due to zpool corruption. I get the following output when trying to import the ZFS pool using either a FreeBSD 8.0p2 cd or the latest OpenSolaris snv_143 cd: FreeBSD mfsbsd 8.0-RELEASE-p2.vx.sk:/usr/obj/usr/src/sys/GENERIC amd64 mfsbsd# zpool import pool: tank id: 1998957762692994918 state: FAULTED

Apparently with zfs boot, if the zpool is a version grub doesn''t recognize, it merely ignores any zfs entries in menu.lst, and apparently instead boots the first entry it thinks it can boot. I ran into this myself due to some boneheaded mistakes while doing a very manual zfs / install at the summit. Shouldn''t it at least spit out a warning? If so, I have no issues filing a

Hey all, I''m setting up a ZFS based fileserver to use both as a shared network drive and separately to have an iSCSI target to be used as the "Hard disk" of a windows based VM runninf on another machine. I''ve built the machine, installed the OS, created the RAIDZ pool and now have a couple of questions (I''m pretty much new to Solaris by the way but have been

Solaris and/or ZFS are badly confused about drive IDs. The "c5t0d0" names are very far removed from the real world, and possibly they''ve gotten screwed up somehow. Is devfsadm supposed to fix those, or does it only delete excess? Reason I believe it''s confused: zpool status shows mirror-0 on c9t3d0, c9t2d0, and c9t5d0. But format shows the one remaining Seagate

I have a Sony lib-162 tape library hooked up to an adaptec 39160 scsi controller. I''m running OpenSolaris / Indiana snv_98 with the CADP160 driver installed from a SXCE dvd (snv_99). When I boot without xvm, I can run "mt config" and see the configuration information for the first drive in the library. Under xvm, some scsi operations still work - I can access the changer, move

Does opensolaris iSCSI target support SCSI-3 PGR reservation ? My goal is to use the iSCSI LUN created by [1] or [2] as a quorum device for a 3-node suncluster. [1] zfs set shareiscsi=on <storage-pool/zfs volume name> [2] iscsitadm create target ..... Thanks, -- leon This message posted from opensolaris.org

Hi, On Fri, Oct 30, 2009 at 8:41 AM, Gopi Desaboyina <gopidesaboyina at yahoo.com> wrote: > I think your system might be over heating. I observed this kind of behaviour in laptops when they get overheated. check if FAN is working or not. How frequent it gets rebooted. you could boot from opensolaris LiveCD and keep it for a day like that. if it reboots that means there could be h/w

Hi All, First time caller - tried WINE today for the very first time, on OpenSolaris no less. Good news - was shocked and stunned how easy it was to get an old copy of Unreal up and running - everything (almost...) "just worked" with practically no configuration, got lovely smooth rendering using my crappy built-in Intel X3100 adaptor. However, I cannot get any audio output

Thanks all - apparently Opensound was integrated into b115 of SXCE (running b118 at the moment), so I understand assuming the application can be built successfully I guess everything should be rocking and rolling. Doesn't look as if this process is entirely straightforward gathering by the activity of another forumite who seems to be determined to nut this out! 8) Cheers, Dave

I want to import my zpool''s from FreeBSD 8.0 in OpenSolaris 2009.06. After reading the few posts (links below) I was able to find on the subject, it seems like it there is a differences between FreeBSD and Solaris. FreeBSD operates on directly on the disk and Solaris creates a partion and uses that... is that right? Is it impossible for OpenSolaris to use zpool''s from FreeBSD?

Hello, Has anyone encountered the following error message, running Solaris 10 u8 in an LDom. bash-3.00# devfsadm devfsadm: write failed for /dev/.devfsadm_dev.lock: Bad exchange descriptor bash-3.00# zpool status -v rpool pool: rpool state: DEGRADED status: One or more devices has experienced an error resulting in data corruption. Applications may be affected. action: Restore the file in

Andy, OSOL 2009.06 been installed in stub domain (hvm domain) at mentioned Dom0 with 2.6.30 xenified kernel via xen-patches-2.6.30-2.tar.bz2 refuse to activate PV drivers. When same Dom0 starts with 2.6.29.4 xenified kernel (xen-patches-2.6.29-6.tar.bz2) kernel OSOL 2009.06 in stub (hvm) domain does activate PV drivers for xdf, xnf . Boris

I''ve installed Open Solaris 2009.06 on a machine with 5 identical 1TB wd green drives to create a ZFS nas. The intended install is one drive dedicated to the OS and the remaining 4 drives in a raidz1 configuration. The install is working fine, but creating the raidz1 pool and rebooting is causing the machine report "Cannot find active partition" upon reboot. Below is command

Hello all, I am trying to set up my brother's UPS (remotely over internet) on an OpenIndiana-based storage box. According to him, the UPS is probably an Ippon Back Power Pro 600 dated around 2003 (battery recently replaced), and it has an USB connection. Sorry for a relatively long post with a log of my successes and failures, in the hopes that someone would point out what I did wrong.