similar to: Resizing ZFS block devices and sbdadm

-bash-3.2# zpool export exchbk cannot 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:

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

Is it possible to modify the GUID associated with a ZFS volume imported into STMF? To clarify- I have a ZFS volume I have imported into STMF and export via iscsi. I have a number of snapshots of this volume. I need to temporarily go back to an older snapshot without removing all the more recent ones. I can delete the current sbd LU, clone the snapshot I want to test, and then bring that back in

I am confused, because I would have expected a 1-to-1 mapping, if you create an iscsi target on some system, you would have to specify which LUN it connects to. But that is not the case... I read the man pages for sbdadm, stmfadm, itadm, and iscsiadm. I read some online examples, where you first "sbdadm create-lu" which gives you a GUID for a specific device in the system, and then

Hello, Im new to this discussion lists so i hope im posting in the right place. I started using zfs not too long ago. Im trying to figure out the ISCSI and NFS sharing for the moment. For the ISCSI sharing at the moment im using COMSTAR. A created the appropriate target, also a LU corespondent to the zvol with sbdadm, then created a view attached to this. Im wondering is there a way to actually

> I tried to copy a 8GB Xen domU disk image from a zvol device > to an image file on an ufs filesystem, and was surprised that > reading from the zvol character device doesn''t detect "EOF". > > On snv_66 (sparc) and snv_73 (x86) I can reproduce it, like this: > > # zfs create -V 1440k tank/floppy-img > > # dd if=/dev/zvol/dsk/tank/floppy-img

What does it mean for the reported value of a zvol volsize to be less than the product of used and compressratio? For example, # zfs get -p all home1/home1mm01 NAME PROPERTY VALUE SOURCE home1/home1mm01 type volume - home1/home1mm01 creation 1254440045 - home1/home1mm01 used 14902492672

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

ever since going from flac 1.1.2 to 1.1.4 on cygwin I've encountered an issue where I can't use metaflac on certain path specifications (see examples below). I tried again with 1.2.1 and it still doesn't work (I can't recall but I think it is from the cygwin dist, not the windows installed version) not sure if this is a flac issue, or a cygwin one, but thougt i'ld start here.

Hey all I''ve created a Xen DomU on snv_134 , its Debian Lenny. For the disk, I''ve used a ZFS volume, which I accidentally set to 1GB. I''ve tried setting the volsize of the volume to 3GB and rebooting the domain, but this still only sees the initial 1GB disk. I''ve read about rebooting for volsize to take effect, but this seems to be in the context of either

Hi, a zfs create -V 1M pool/foo dd if=/dev/random of=/dev/zvol/rdsk/pool/foo bs=1k count=1k (using Nevada b94) yields zfs get all pool/foo pool/foo used 1,09M - pool/foo referenced 1,09M - pool/foo volsize 1M - pool/foo refreservation 1M local Why is ''referenced'' bigger

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

Hello list, I started playing aroud with Comstar in snv_134. In snv_116 version of ZFS, a new hidden property for the Comstar MetaData has been intoduced (stmf_sbd_lu). This makes it possible to migrate from legacy (iscsi target daemon) to Comstar without data loss, which is great. Before this property you always lost the first 64k of your zvol data where comstar wrote it''s metadata -

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

On 13/10/12 17:24, Sean Silva wrote: > Another question: What kind of documentation you are planning to > produce for this feature? > > -- Sean Silva > > On Fri, Oct 12, 2012 at 4:36 PM, Jim Grosbach<grosbach at apple.com> wrote: >> >> On Oct 12, 2012, at 1:07 PM, Sean Silva<silvas at purdue.edu> wrote: >> >>> Hi Jim, thanks for the

CentOS Errata and Bugfix Advisory 2019:0502 Upstream details at : https://access.redhat.com/errata/RHBA-2019:0502 The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) x86_64: efc201c7a2126f9a65bf98e3e6a395f0d8e9fcc8657946b99af5460f00ede18c sbd-1.3.1-8.2.el7_6.1.x86_64.rpm Source:

CentOS Errata and Bugfix Advisory 2019:3053 Upstream details at : https://access.redhat.com/errata/RHBA-2019:3053 The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) x86_64: a13baf42f6bdc2eea91ea5e641d3dd85955b64ef2d75a522e494b85341ed4524 sbd-1.4.0-4.el7_7.3.x86_64.rpm Source:

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

Hi, I have a CentOS 6.4 fileserver running SerNet Samba 4.0.9 with these global settings (not overridden): read only = No force create mode = 0777 force directory mode = 0777 inherit acls = yes inherit owner = yes inherit permissions = yes On a Windows client, I have Thunderbird 24.0 storing its profile and mail on the Samba share. The