similar to: kernel: blk_cloned_rq_check_limits: over max segments limit., Device Mapper Multipath, iBFT, iSCSI COMSTAR

Hi, What's the correct way to change configuration parameters for an iSCSI device? For example I/O scheduler, max_sectors_kb, etc... I could add commands to the S99local script: echo noop > /sys/block/sdb/queue/scheduler echo 64 > /sys/block/sdb/queue/max_hw_sectors_kb Unfortunately, iSCSI device names might change from sdb to, say, sdc (server reboot, iSCSI target reconnection).

(switched to email. Please respond via emailed reply-to-all, not via the bugzilla web interface). On Thu, 17 Feb 2011 13:20:20 GMT bugzilla-daemon@bugzilla.kernel.org wrote: > https://bugzilla.kernel.org/show_bug.cgi?id=29302 > > Summary: Null pointer dereference with large max_sectors_kb > Product: IO/Storage > Version: 2.5 > Kernel

Hi all, We have been using SuSE7.2 and samba (client and server) without any problems for a few months. Now, we migrated some workstations (samba clients) to SuSE8.0 and we get segfaults while accessing files mounted through samba. The segfault happens on the CLIENT side. Here is our network configuration: - SuSE7.2 server with default samba server package. - Few SuSE7.2 workstations

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

Convert the S_<FOO> symbolic permissions to their octal equivalents as using octal and not symbolic permissions is preferred by many as more readable. see: https://lkml.org/lkml/2016/8/2/1945 Done with automated conversion via: $ ./scripts/checkpatch.pl -f --types=SYMBOLIC_PERMS --fix-inplace <files...> Miscellanea: o Wrapped modified multi-line calls to a single line where

Convert the S_<FOO> symbolic permissions to their octal equivalents as using octal and not symbolic permissions is preferred by many as more readable. see: https://lkml.org/lkml/2016/8/2/1945 Done with automated conversion via: $ ./scripts/checkpatch.pl -f --types=SYMBOLIC_PERMS --fix-inplace <files...> Miscellanea: o Wrapped modified multi-line calls to a single line where

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

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

I created a multi-device btrfs filesystem across two drives: 80 GB SATA 2.5 inch drive (sdb) 120 GB PATA 3.5 inch drive (sdd) If I copy a decent-sized file to the filesystem, there are "bio too big" messages in dmesg, and I get read errors (along with ''btrfs csum failed'') when trying to read them again. The process writing the files is unaware the data was not

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

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:

Hello fellow sysadmins! I've assembled a whitebox system with a SuperMicro motherboard, case, 8GB of memory and a single quad core Xeon processor. I have two 9650SE-8LPML cards (8 ports each) in each server with 12 1TB SATA drives total. Three drives per "lane" on each card. CentOS 5.2 x86_64. I'm looking for advice on tuning this thing for performance. Especially for the

On 03/06/2019 15:17, Nico wrote: > Sorry, I forgot to precise : It's on a Samba AD DC (v4.10.3 and CentOS > 7). > > My smb.conf : > > [global] >     server role = active directory domain controller >     netbios name = server_name >     realm = DOMAIN.LAN >     workgroup = DOMAIN > >     server services = -dns > >     idmap_ldb:use rfc2307 = yes >