similar to: Which zfs options are replicated

Hi, WARNING: Long post ahead I have an issue when starting multipathd. The kernel complains about "blk_cloned_rq_check_limits: over max segments limit". The server in question is configured for KVM hosting. It boots via iBFT to an iSCSI volume. Target is COMSTAR and underlying that is a ZFS volume (100GB). The server also has two infiniband cards providing four (4) more paths over SRP

Hello all, I am running an OpenSolaris server running 06/09. I installed comstar and enabled it. I have an ESXi 4.0 server connecting to Comstar via iscsi on its own switch. (There are two esxi servers), both of which do this regardless of whether one is on or off. The error I see is on esxi "Lost connectivity to storage device naa.600144f030bc450000004a9806980003. Path vmhba33:C0:T0:L0 is

Hi, I have a zfs volume that''s exported via iscsi for my wife''s Mac to use for Time Machine. I''ve just built a new machine to house my "big" pool, and installed build 129 on it. I''d like to start using COMSTAR for exporting the iscsi targets, rather than the older iscsi infrastructure. I''ve seen quite a few tutorials on how to use

I''ve been experimenting with a two system setup in snv_134 where each system exports a zvol via COMSTAR iSCSI. One system imports both its own zvol and the one from the other system and puts them together in a ZFS mirror. I manually faulted the zvol on one system by physically removing some drives. What I expect to happen is that ZFS will fault the zvol pool and the iSCSI stack will

root at cs6:~# zpool import pool: content3 id: 14184872052409584084 state: FAULTED status: The pool metadata is corrupted. action: The pool cannot be imported due to damaged devices or data. The pool may be active on another system, but can be imported using the ''-f'' flag. see: http://www.sun.com/msg/ZFS-8000-72 config: content3

The earlier post with the Dtrace probes definition (sent on April 23) was only to solicit feedback from all prospective users of iSCSI DTrace probes. I will follow up shortly with an updated document requesting approval from the community. thanks Priya -------- Original Message -------- Subject: Dtrace provider for the COMSTAR iscsi Target Port Provider - Review Request Date: Thu, 23 Apr

I apologize if this has been covered before. I have not seen a blow-by-blow installation guide for Ubuntu onto an iSCSI target. The install guides I have seen assume that you can make a target visible to all, which is a problem if you want multiple iSCSI installations on the same COMSTAR target. During install Ubuntu generates three random initiators and you have to deal with them to get things

Can anyone confirm my action plan is the proper way to do this? The reason I''m doing this is I want to create 2xraidz2 pools instead of expanding my current 2xraidz1 pool. So I''ll create a 1xraidz2 vdev, migrate my current 2xraidz1 pool over, destroy that pool and then add it as a 1xraidz2 vdev to the new pool. I''m running b130, sharing both with CIFS and ISCSI (not

We are looking into the possibility of adding a dedicated ZIL and/or L2ARC devices to our pool. We are looking into getting 4 ? 32GB Intel X25-E SSD drives. Would this be a good solution to slow write speeds? We are currently sharing out different slices of the pool to windows servers using comstar and fibrechannel. We are currently getting around 300MB/sec performance with 70-100% disk busy.

Hello All, One of our user is facing java.lang.OutOfMemoryError: PermGen space issue on a Windows 2003 32 bit xVM domU with 4GB RAM. He is able to successfully do these tests on equivalent physical system with Windows 2003 OS and 4GB RAM. Another user is facing issues with Tomcat running out of heap space on a Win2008 64bit xvM domU Our xVM hypervisor server is X4150 server with 64GB RAM

I have added a specification of probes for the fibre channel COMSTAR port provider to the DTrace section of wikis.sun.com. The proposal may be found here: http://wikis.sun.com/display/DTrace/fibre+channel+Provider I welcome feedback regarding this proposal. Thanks, Sam

Hello list, while following this list for more then 1 year, I feel that this list was a great way to get insights into ZFS. Thank you all for contributing. Over the last month''s I was writing a little "whitepaper" trying to consolidate the knowledge collected here. It has now reached a "beta" state and I would like to share the result with you. I call it -

The iscsit_dtrace_draftv5.txt describes the Dtrace probes definition for the COMSTAR iSCSI target port provider. For all those interested in iSCSI, please take a look and send me your feedback/questions/suggestions etc by Thursday, April 20, 2009 thanks Priya -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: iscsit_dtrace_draftv5.txt URL:

sbdadm can be used with a regular ZFS file or a ZFS block device. Is there an advatage to using a ZFS block device and exporting it to comstar via sbdadm as opposed to using a file and exporting it? (e.g. performance or manageability?) Also- let''s say you have a 5G block device called pool/test You can resize it by doing: zfs set volsize=10G pool/test However if the device was already

Hi all, Using "old" way of sharing volumes over iscsi in zfs (zfs set shareiscsi=on) i can see i/o stats per iscsi volume running a command iscsitadm show stats -I 1 volume. However i couldn''t find something similar in new framework,comstar. Probably i''m missing something, so if anyone has some tips please share it :) Thanks in advance, Bruno -------------- next part

Hi, Nexenta CP and NexentaStor has integrated COMSTAR with ZFS, which provides 2-3x performance gain over userland SCSI target daemon. I;ve blogged in more detail at http://www.gulecha.org/2009/03/03/nexenta-iscsi-with-comstarzfs-integration/ Cheers, Anil http://www.gulecha.org

I would like to request approval of the the DTrace proposal for the COMSTAR iSCSI target port provider. I have updated the specification of the iscsi provider at http://wikis.sun.com/display/DTrace/iscsi+Provider. Your feedback is appreciated. thanks Priya -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: iscsit_dtrace_draftv8.txt URL:

Building with --enable-llvm failed latter on when compiling libojc: configure:5099: checking for exception model to use configure:5131: /home/rafael/dev/gcc/build/gcc/xgcc -B/home/rafael/dev/gcc/build/gcc/ -B/i686-pc-linux-gnu/bin/ -B/i686-pc-linux-gnu/lib/ -isystem /i686-pc-linux-gnu/include -isystem /i686-pc-linux-gnu/sys-include -c -xobjecti ve-c -fgnu-runtime -fobjc-exceptions -S conftest.c

On Fri, 21 Apr 2006, [UTF-8] Rafael Esp?ndola wrote: > To work aroud the problem I edited gcc/objc/config-lang.in and removed > the comment from the line > #target_libs=target-libobjc > > With this change it is again possible to build without objc. The > complete configure line was > > ../llvm-gcc4-1.7.source/configure --prefix=$CFEINSTALL > --enable-languages=c,c++

Hi, I recently bootstrapped gcc4 frontend on a i686-linux-gnu too. As I notice, if the llvm "tools-only " was build with srcdir != objdir , the building of llvm-gcc4-1.7.source encountered mistakes of unable to find some header files. So I just edited llvm-gcc4-1.7.source/gcc/Makefile.in and a line like this: INCLUDES += -I$(LLVMOBJDIR)/include With this change, the building errors