From bugmaster at FreeBSD.org  Mon May  4 11:08:05 2009
From: bugmaster at FreeBSD.org (FreeBSD bugmaster)
Date: Mon May  4 11:09:49 2009
Subject: Current problem reports assigned to freebsd-scsi@FreeBSD.org
Message-ID: <200905041108.n44B83Ne098848@freefall.freebsd.org>

Note: to view an individual PR, use:
  http://www.freebsd.org/cgi/query-pr.cgi?pr=(number).

The following is a listing of current problems submitted by FreeBSD users.
These represent problem reports covering all versions including
experimental development code and obsolete releases.


S Tracker      Resp.      Description
--------------------------------------------------------------------------------
o amd64/132394 scsi       [isp] - bad underruns with QLogic qla2300 and amd64
o kern/132250  scsi       [ciss] ciss driver does not support more then 15 drive
o kern/132206  scsi       [mpt] system panics on boot when mirroring and 2nd dri
o kern/131032  scsi       [panic] hald causing panic in scsi_sg
o kern/130735  scsi       [cam] [patch] pass M_NOWAIT to the malloc() call insid
o kern/130621  scsi       [mpt] tranfer rate is inscrutable slow when use lsi213
o kern/129602  scsi       [ahd] ahd(4) gets confused and wedges SCSI bus
o kern/128452  scsi       [sa] [panic] Accessing SCSI tape drive randomly crashe
o kern/128245  scsi       [scsi] "inquiry data fails comparison at DV1 step" [re
o kern/127927  scsi       [isp] isp(4) target driver crashes kernel when set up 
o kern/126866  scsi       [isp] [panic] kernel panic on card initialization
o kern/124667  scsi       [amd] [panic] FreeBSD-7 kernel page faults at amd-scsi
o kern/123674  scsi       [ahc] ahc driver dumping
o kern/123666  scsi       [aac] attach fails with Adaptec SAS RAID 3805 controll
o sparc/121676 scsi       [iscsi] iscontrol do not connect iscsi-target on sparc
o kern/120487  scsi       [sg] scsi_sg incompatible with scanners
o kern/120247  scsi       [mpt] FreeBSD 6.3 and LSI Logic 1030 = only 3.300MB/s 
o kern/119668  scsi       [cam] [patch] certain errors are too verbose comparing
o kern/114597  scsi       [sym] System hangs at SCSI bus reset with dual HBAs
o kern/110847  scsi       [ahd] Tyan U320 onboard problem with more than 3 disks
o kern/99954   scsi       [ahc] reading from DVD failes on 6.x [regression]
o kern/94838   scsi       Kernel panic while mounting SD card with lock switch o
o kern/92798   scsi       [ahc] SCSI problem with timeouts
o kern/90282   scsi       [sym] SCSI bus resets cause loss of ch device
o kern/76178   scsi       [ahd] Problem with ahd and large SCSI Raid system
o kern/74627   scsi       [ahc] [hang] Adaptec 2940U2W Can't boot 5.3
s kern/61165   scsi       [panic] kernel page fault after calling cam_send_ccb
o kern/60641   scsi       [sym] Sporadic SCSI bus resets with 53C810 under load
o kern/60598   scsi       wire down of scsi devices conflicts with config
s kern/57398   scsi       [mly] Current fails to install on mly(4) based RAID di
o kern/52638   scsi       [panic] SCSI U320 on SMP server won't run faster than 
o kern/44587   scsi       dev/dpt/dpt.h is missing defines required for DPT_HAND
o kern/40895   scsi       wierd kernel / device driver bug
o kern/39388   scsi       ncr/sym drivers fail with 53c810 and more than 256MB m
o kern/38828   scsi       [dpt] [request] DPT PM2012B/90 doesn't work
o kern/35234   scsi       World access to /dev/pass? (for scanner) requires acce

36 problems total.

From mitya at cavia.pp.ru  Thu May  7 12:24:43 2009
From: mitya at cavia.pp.ru (Dmitry Sivachenko)
Date: Thu May  7 12:24:50 2009
Subject: mpt0: QUEUE FULL EVENT annoying
Message-ID: <20090507120338.GA59717@m4-new.master-telecom.ru>

Hello!

I am using FreeBSD-7.2-STABLE. I have the following hardware:

mpt0: <LSILogic SAS/SATA Adapter> port 0xec00-0xecff mem 0xfc4fc000-0xfc4fffff,0xfc4e0000-0xfc4effff irq 16 at device 0.0 on pci1
mpt0: MPI Version=1.5.14.0

da0 at mpt0 bus 0 target 0 lun 0
da0: <SEAGATE ST9146802SS S229> Fixed Direct Access SCSI-5 device
da0: 300.000MB/s transfers
da0: Command Queueing Enabled
da0: 140014MB (286749480 512 byte sectors: 255H 63S/T 17849C)

(many similar disks).

In dmesg output I have a lot of
mpt0: QUEUE FULL EVENT: Bus 0x00 Target 0x00 Depth 58
(with different Target values).

After googleing a bit I got an impression that message is harmless
(see for instance Scott Long's post:
http://kerneltrap.org/mailarchive/freebsd-current/2007/10/11/334975

"The message can probably be put under bootverbose."
)


If it is still the case and these messages are indeed harmless, can we
please put them under bootverbose or do something similar?

They spam system logs and make it much more harder to notice
important events.

Thanks in advance.

From marius at alchemy.franken.de  Sun May 10 21:27:16 2009
From: marius at alchemy.franken.de (Marius Strobl)
Date: Sun May 10 21:27:22 2009
Subject: isp panic after printing the uptime
In-Reply-To: <49A2B464.4020409@kasimir.com>
References: <49A2B464.4020409@kasimir.com>
Message-ID: <20090510204959.GA27204@alchemy.franken.de>

On Mon, Feb 23, 2009 at 03:36:20PM +0100, Florian Smeets wrote:
> Hi,
> 
> i have a 100% reproducible panic on sparc64 with an isp controller.
> Every time i reboot/shutdown the machine it panics after printing
> "Uptime: XXXX". I'm not sure if this is more scsi or sparc64 related but
> as the trace includes isp_* functions i went for scsi@.
> 
> The controller used is:
> 
> isp0: <Qlogic ISP 2200 PCI FC-AL Adapter> port 0x300-0x3ff mem
> 0x100000-0x100fff at device 4.0 on pci2
> isp0: [ITHREAD]
> isp0: Board Type 2200, Chip Revision 0x5, loaded F/W Revision 2.2.6
> isp0: invalid NVRAM header
> isp0: invalid NVRAM header
> 
> The messages prior to the panic and the panic look like this:
> 
> Sayncing diisks, vnotdes remaiining...n2 g (max 60 seconds) for system
> process `syncer' to stop...2 1 0 1 0 0 done
> All buffers synced.
> zfs_umount:969[0]: Force unmount is not supported, removing FORCE flag.
> zfs_umount:969[0]: Force unmount is not supported, removing FORCE flag.
> zfs_umount:969[0]: Force unmount is not supported, removing FORCE flag.
> lock order reversal:
>  1st 0xfffff800038394e0 ufs (ufs) @ /usr/src/sys/kern/vfs_mount.c:1202
>  2nd 0xfffff80003839c40 devfs (devfs) @ /usr/src/sys/kern/vfs_subr.c:2092
> KDB: stack backtrace:
> _witness_debugger() at _witness_debugger+0x38
> witness_checkorder() at witness_checkorder+0xcf8
> __lockmgr_args() at __lockmgr_args+0x874
> vop_stdlock() at vop_stdlock+0x38
> VOP_LOCK1_APV() at VOP_LOCK1_APV+0x110
> _vn_lock() at _vn_lock+0x80
> vget() at vget+0x120
> devfs_allocv() at devfs_allocv+0x114
> devfs_root() at devfs_root+0x3c
> dounmount() at dounmount+0x490
> vfs_unmountall() at vfs_unmountall+0x3c
> boot() at boot+0x674
> reboot() at reboot+0x58
> syscall() at syscall+0x2bc
> -- syscall (55, FreeBSD ELF64, reboot) %o7=0x102a88 --
> userland() at 0x12b348
> user trace: trap %o7=0x102a88
> pc 0x12b348, sp 0x7fdffffdd91
> pc 0x101778, sp 0x7fdffffdf01
> pc 0x1001d0, sp 0x7fdffffe531
> pc 0, sp 0x7fdffffe5f1
> done
> Uptime: 6m9s
> panic: trap: fast data access mmu miss
> cpuid = 0
> KDB: enter: panic
> [thread pid 1 tid 100001 ]
> Stopped at      kdb_enter+0x80: ta              %xcc, 1
> db> where
> Tracing pid 1 tid 100001 td 0xfffff80002082000
> panic() at panic+0x20c
> trap() at trap+0x570
> -- fast data access mmu miss tar=0x1454156000 %o7=0xc040e7a4 --
> _mtx_lock_spin_flags() at _mtx_lock_spin_flags+0x5c
> callout_lock() at callout_lock+0x50
> untimeout() at untimeout+0xc
> isp_done() at isp_done+0x140
> isp_intr() at isp_intr+0x3eb8
> isp_poll() at isp_poll+0x38
> xpt_polled_action() at xpt_polled_action+0xf0
> dashutdown() at dashutdown+0x130
> boot() at boot+0x8ac
> reboot() at reboot+0x58
> syscall() at syscall+0x2bc
> -- syscall (55, FreeBSD ELF64, reboot) %o7=0x102a88 --
> userland() at 0x12b348
> user trace: trap %o7=0x102a88
> pc 0x12b348, sp 0x7fdffffdd91
> pc 0x101778, sp 0x7fdffffdf01
> pc 0x1001d0, sp 0x7fdffffe531
> pc 0, sp 0x7fdffffe5f1
> done
> db>
> 
> Anything i can do, aside from not rebooting the machine :-) ?
> 

For the records, this was fixed with r191979.

Marius

From bugmaster at FreeBSD.org  Mon May 11 11:07:04 2009
From: bugmaster at FreeBSD.org (FreeBSD bugmaster)
Date: Mon May 11 11:09:16 2009
Subject: Current problem reports assigned to freebsd-scsi@FreeBSD.org
Message-ID: <200905111107.n4BB73ip086092@freefall.freebsd.org>

Note: to view an individual PR, use:
  http://www.freebsd.org/cgi/query-pr.cgi?pr=(number).

The following is a listing of current problems submitted by FreeBSD users.
These represent problem reports covering all versions including
experimental development code and obsolete releases.


S Tracker      Resp.      Description
--------------------------------------------------------------------------------
o amd64/132394 scsi       [isp] - bad underruns with QLogic qla2300 and amd64
o kern/132250  scsi       [ciss] ciss driver does not support more then 15 drive
o kern/132206  scsi       [mpt] system panics on boot when mirroring and 2nd dri
o kern/131032  scsi       [panic] hald causing panic in scsi_sg
o kern/130735  scsi       [cam] [patch] pass M_NOWAIT to the malloc() call insid
o kern/130621  scsi       [mpt] tranfer rate is inscrutable slow when use lsi213
o kern/129602  scsi       [ahd] ahd(4) gets confused and wedges SCSI bus
o kern/128452  scsi       [sa] [panic] Accessing SCSI tape drive randomly crashe
o kern/128245  scsi       [scsi] "inquiry data fails comparison at DV1 step" [re
o kern/127927  scsi       [isp] isp(4) target driver crashes kernel when set up 
o kern/126866  scsi       [isp] [panic] kernel panic on card initialization
o kern/124667  scsi       [amd] [panic] FreeBSD-7 kernel page faults at amd-scsi
o kern/123674  scsi       [ahc] ahc driver dumping
o kern/123666  scsi       [aac] attach fails with Adaptec SAS RAID 3805 controll
o sparc/121676 scsi       [iscsi] iscontrol do not connect iscsi-target on sparc
o kern/120487  scsi       [sg] scsi_sg incompatible with scanners
o kern/120247  scsi       [mpt] FreeBSD 6.3 and LSI Logic 1030 = only 3.300MB/s 
o kern/119668  scsi       [cam] [patch] certain errors are too verbose comparing
o kern/114597  scsi       [sym] System hangs at SCSI bus reset with dual HBAs
o kern/110847  scsi       [ahd] Tyan U320 onboard problem with more than 3 disks
o kern/99954   scsi       [ahc] reading from DVD failes on 6.x [regression]
o kern/94838   scsi       Kernel panic while mounting SD card with lock switch o
o kern/92798   scsi       [ahc] SCSI problem with timeouts
o kern/90282   scsi       [sym] SCSI bus resets cause loss of ch device
o kern/76178   scsi       [ahd] Problem with ahd and large SCSI Raid system
o kern/74627   scsi       [ahc] [hang] Adaptec 2940U2W Can't boot 5.3
s kern/61165   scsi       [panic] kernel page fault after calling cam_send_ccb
o kern/60641   scsi       [sym] Sporadic SCSI bus resets with 53C810 under load
o kern/60598   scsi       wire down of scsi devices conflicts with config
s kern/57398   scsi       [mly] Current fails to install on mly(4) based RAID di
o kern/52638   scsi       [panic] SCSI U320 on SMP server won't run faster than 
o kern/44587   scsi       dev/dpt/dpt.h is missing defines required for DPT_HAND
o kern/40895   scsi       wierd kernel / device driver bug
o kern/39388   scsi       ncr/sym drivers fail with 53c810 and more than 256MB m
o kern/38828   scsi       [dpt] [request] DPT PM2012B/90 doesn't work
o kern/35234   scsi       World access to /dev/pass? (for scanner) requires acce

36 problems total.

From linimon at FreeBSD.org  Tue May 12 19:52:16 2009
From: linimon at FreeBSD.org (linimon@FreeBSD.org)
Date: Tue May 12 19:52:22 2009
Subject: kern/134488: [mpt] MPT SCSI driver probes max. 8 LUNs per device
Message-ID: <200905121952.n4CJqFpP097763@freefall.freebsd.org>

Old Synopsis: [SCSI] MPT SCSI driver probes max. 8 LUNs per device
New Synopsis: [mpt] MPT SCSI driver probes max. 8 LUNs per device

Responsible-Changed-From-To: freebsd-bugs->freebsd-scsi
Responsible-Changed-By: linimon
Responsible-Changed-When: Tue May 12 19:51:36 UTC 2009
Responsible-Changed-Why: 
Over to maintainer(s).

http://www.freebsd.org/cgi/query-pr.cgi?pr=134488
From scottl at samsco.org  Wed May 13 05:10:04 2009
From: scottl at samsco.org (Scott Long)
Date: Wed May 13 05:10:10 2009
Subject: kern/134488: [mpt] MPT SCSI driver probes max. 8 LUNs per device
Message-ID: <200905130510.n4D5A4NT042764@freefall.freebsd.org>

The following reply was made to PR kern/134488; it has been noted by GNATS.

From: Scott Long <scottl@samsco.org>
To: bug-followup@FreeBSD.org, michel.bouissou@bioclinica.com
Cc:  
Subject: Re: kern/134488: [mpt] MPT SCSI driver probes max. 8 LUNs per device
Date: Tue, 12 May 2009 22:59:42 -0600

 Increasing the max_lun number in the code is not the solution.  Which 
 arbitrary number should be chosen?  If it's increased to 32, what about 
 those who want 64?  What about the problems created for those with older
 hardware that can't handle high lun scanning?  The correct action 
 requires a significant amount of code to be written and tested; if it
 were trivial it would have been done already.  I know this response is
 unsatisfying and slightly aloof, and I apologize for that, but right now
 it's easier to ask that admins recompile for this situation than it is
 to tear up the core SCSI scanning code.
 
 Scott
From mbouissou at bioimaging.com  Wed May 13 15:00:36 2009
From: mbouissou at bioimaging.com (Michel Bouissou)
Date: Wed May 13 15:00:43 2009
Subject: kern/134488: [mpt] MPT SCSI driver probes max. 8 LUNs per device
Message-ID: <200905131500.n4DF0F4K079385@freefall.freebsd.org>

The following reply was made to PR kern/134488; it has been noted by GNATS.

From: Michel Bouissou <mbouissou@bioimaging.com>
To: Scott Long <scottl@samsco.org>
Cc: bug-followup@FreeBSD.org
Subject: Re: kern/134488: [mpt] MPT SCSI driver probes max. 8 LUNs per
	device
Date: Wed, 13 May 2009 16:24:31 +0200

 On mar, 2009-05-12 at 22:59 -0600, Scott Long wrote:
 > Increasing the max_lun number in the code is not the solution.  Which 
 > arbitrary number should be chosen?  If it's increased to 32, what about 
 > those who want 64?
 
 Well, 8 is as much arbitrary than 32 would be, but 32 would cover a
 wider use spectrum.
 
 SCSI disks enclosures holding 16 to 20 disks are quite commonplace, and
 some show each disk as a LUN on the same SCSI device (i.e. some SCSI to
 SATA enclosures, or some RAID bays with RAID turned off to use ZFS RAID
 instead).
 
 > What about the problems created for those with older
 > hardware that can't handle high lun scanning?
 
 I'm not sure whether this exists. Possibly. My own SCSI card BIOS
 (LSILogic 1030 Ultra4 Adapter) only scans LUNs 0-7 when the system
 boots, *but* that doesn't prevent FreeBSD to use much higher LUN numbers
 when dev/mpt/mpt_cam.c is patched and recompiled for allowing so.
 
 > The correct action requires a significant amount of code to be written
 > and tested; if it were trivial it would have been done already.
 
 Maybe guessing the highest LUN number to scan according to HW type would
 be difficult, but would it be also very difficult to make this a
 parameter that could default to 8 and be set to higher values with an
 entry i.e. in /boot/loader.conf ?
 
 Would be easier than having to recompile the kernel...
 
From bugmaster at FreeBSD.org  Mon May 18 11:07:01 2009
From: bugmaster at FreeBSD.org (FreeBSD bugmaster)
Date: Mon May 18 11:09:23 2009
Subject: Current problem reports assigned to freebsd-scsi@FreeBSD.org
Message-ID: <200905181106.n4IB6xj4075791@freefall.freebsd.org>

Note: to view an individual PR, use:
  http://www.freebsd.org/cgi/query-pr.cgi?pr=(number).

The following is a listing of current problems submitted by FreeBSD users.
These represent problem reports covering all versions including
experimental development code and obsolete releases.


S Tracker      Resp.      Description
--------------------------------------------------------------------------------
o kern/134488  scsi       [mpt] MPT SCSI driver probes max. 8 LUNs per device
o amd64/132394 scsi       [isp] - bad underruns with QLogic qla2300 and amd64
o kern/132250  scsi       [ciss] ciss driver does not support more then 15 drive
o kern/132206  scsi       [mpt] system panics on boot when mirroring and 2nd dri
o kern/131032  scsi       [panic] hald causing panic in scsi_sg
o kern/130735  scsi       [cam] [patch] pass M_NOWAIT to the malloc() call insid
o kern/130621  scsi       [mpt] tranfer rate is inscrutable slow when use lsi213
o kern/129602  scsi       [ahd] ahd(4) gets confused and wedges SCSI bus
o kern/128452  scsi       [sa] [panic] Accessing SCSI tape drive randomly crashe
o kern/128245  scsi       [scsi] "inquiry data fails comparison at DV1 step" [re
o kern/127927  scsi       [isp] isp(4) target driver crashes kernel when set up 
o kern/126866  scsi       [isp] [panic] kernel panic on card initialization
o kern/124667  scsi       [amd] [panic] FreeBSD-7 kernel page faults at amd-scsi
o kern/123674  scsi       [ahc] ahc driver dumping
o kern/123666  scsi       [aac] attach fails with Adaptec SAS RAID 3805 controll
o sparc/121676 scsi       [iscsi] iscontrol do not connect iscsi-target on sparc
o kern/120487  scsi       [sg] scsi_sg incompatible with scanners
o kern/120247  scsi       [mpt] FreeBSD 6.3 and LSI Logic 1030 = only 3.300MB/s 
o kern/119668  scsi       [cam] [patch] certain errors are too verbose comparing
o kern/114597  scsi       [sym] System hangs at SCSI bus reset with dual HBAs
o kern/110847  scsi       [ahd] Tyan U320 onboard problem with more than 3 disks
o kern/99954   scsi       [ahc] reading from DVD failes on 6.x [regression]
o kern/94838   scsi       Kernel panic while mounting SD card with lock switch o
o kern/92798   scsi       [ahc] SCSI problem with timeouts
o kern/90282   scsi       [sym] SCSI bus resets cause loss of ch device
o kern/76178   scsi       [ahd] Problem with ahd and large SCSI Raid system
o kern/74627   scsi       [ahc] [hang] Adaptec 2940U2W Can't boot 5.3
s kern/61165   scsi       [panic] kernel page fault after calling cam_send_ccb
o kern/60641   scsi       [sym] Sporadic SCSI bus resets with 53C810 under load
o kern/60598   scsi       wire down of scsi devices conflicts with config
s kern/57398   scsi       [mly] Current fails to install on mly(4) based RAID di
o kern/52638   scsi       [panic] SCSI U320 on SMP server won't run faster than 
o kern/44587   scsi       dev/dpt/dpt.h is missing defines required for DPT_HAND
o kern/40895   scsi       wierd kernel / device driver bug
o kern/39388   scsi       ncr/sym drivers fail with 53c810 and more than 256MB m
o kern/38828   scsi       [dpt] [request] DPT PM2012B/90 doesn't work
o kern/35234   scsi       World access to /dev/pass? (for scanner) requires acce

37 problems total.

From bugmaster at FreeBSD.org  Mon May 25 11:07:00 2009
From: bugmaster at FreeBSD.org (FreeBSD bugmaster)
Date: Mon May 25 11:09:23 2009
Subject: Current problem reports assigned to freebsd-scsi@FreeBSD.org
Message-ID: <200905251106.n4PB6xBj092948@freefall.freebsd.org>

Note: to view an individual PR, use:
  http://www.freebsd.org/cgi/query-pr.cgi?pr=(number).

The following is a listing of current problems submitted by FreeBSD users.
These represent problem reports covering all versions including
experimental development code and obsolete releases.


S Tracker      Resp.      Description
--------------------------------------------------------------------------------
o kern/134488  scsi       [mpt] MPT SCSI driver probes max. 8 LUNs per device
o amd64/132394 scsi       [isp] - bad underruns with QLogic qla2300 and amd64
o kern/132250  scsi       [ciss] ciss driver does not support more then 15 drive
o kern/132206  scsi       [mpt] system panics on boot when mirroring and 2nd dri
o kern/131032  scsi       [panic] hald causing panic in scsi_sg
o kern/130735  scsi       [cam] [patch] pass M_NOWAIT to the malloc() call insid
o kern/130621  scsi       [mpt] tranfer rate is inscrutable slow when use lsi213
o kern/129602  scsi       [ahd] ahd(4) gets confused and wedges SCSI bus
o kern/128452  scsi       [sa] [panic] Accessing SCSI tape drive randomly crashe
o kern/128245  scsi       [scsi] "inquiry data fails comparison at DV1 step" [re
o kern/127927  scsi       [isp] isp(4) target driver crashes kernel when set up 
o kern/126866  scsi       [isp] [panic] kernel panic on card initialization
o kern/124667  scsi       [amd] [panic] FreeBSD-7 kernel page faults at amd-scsi
o kern/123674  scsi       [ahc] ahc driver dumping
o kern/123666  scsi       [aac] attach fails with Adaptec SAS RAID 3805 controll
o sparc/121676 scsi       [iscsi] iscontrol do not connect iscsi-target on sparc
o kern/120487  scsi       [sg] scsi_sg incompatible with scanners
o kern/120247  scsi       [mpt] FreeBSD 6.3 and LSI Logic 1030 = only 3.300MB/s 
o kern/119668  scsi       [cam] [patch] certain errors are too verbose comparing
o kern/114597  scsi       [sym] System hangs at SCSI bus reset with dual HBAs
o kern/110847  scsi       [ahd] Tyan U320 onboard problem with more than 3 disks
o kern/99954   scsi       [ahc] reading from DVD failes on 6.x [regression]
o kern/94838   scsi       Kernel panic while mounting SD card with lock switch o
o kern/92798   scsi       [ahc] SCSI problem with timeouts
o kern/90282   scsi       [sym] SCSI bus resets cause loss of ch device
o kern/76178   scsi       [ahd] Problem with ahd and large SCSI Raid system
o kern/74627   scsi       [ahc] [hang] Adaptec 2940U2W Can't boot 5.3
s kern/61165   scsi       [panic] kernel page fault after calling cam_send_ccb
o kern/60641   scsi       [sym] Sporadic SCSI bus resets with 53C810 under load
o kern/60598   scsi       wire down of scsi devices conflicts with config
s kern/57398   scsi       [mly] Current fails to install on mly(4) based RAID di
o kern/52638   scsi       [panic] SCSI U320 on SMP server won't run faster than 
o kern/44587   scsi       dev/dpt/dpt.h is missing defines required for DPT_HAND
o kern/40895   scsi       wierd kernel / device driver bug
o kern/39388   scsi       ncr/sym drivers fail with 53c810 and more than 256MB m
o kern/38828   scsi       [dpt] [request] DPT PM2012B/90 doesn't work
o kern/35234   scsi       World access to /dev/pass? (for scanner) requires acce

37 problems total.

From francisco.cabrita at gmail.com  Mon May 25 14:00:53 2009
From: francisco.cabrita at gmail.com (Francisco Cabrita)
Date: Mon May 25 14:01:00 2009
Subject: Question about iSCSI
Message-ID: <ba4aa9cb0905250630l7f06c319vf144fd5609e025f0@mail.gmail.com>

Hi,

I don't know if this ML is the right place to post a question about iSCSI. I
will write it anyway.

info:
I have built a NAS server under FreeBSD. Geom RAID5 over 3 hard disks and
iSCSI target0 created.
It is up and running without problems "exporting" a SCSI driver to a Ms
Windows 2000 Server with Microsoft iSCSI Inititator driver.
The volume is NTFS.

doubt:
I have read multiple "old" posts around the web that I can't connect
multiple initiators (w2k clients) to the same target. Is this true nowadays?

Facts:
I really need at least two w2k clients to the same "storage NAS". Any tip
about how to solve this?
Maybe some kind of failover technique between both w2k servers?

I really appreciate your help. Thanks in advance

Best Regards
Francisco

PS: I am thinking about sending this email to FreeBSD Cluster ML too.

-- 
blog: http://sufixo.com/raw
http://www.linkedin.com/in/franciscocabrita
From lists at jnielsen.net  Mon May 25 15:17:43 2009
From: lists at jnielsen.net (John Nielsen)
Date: Mon May 25 15:17:49 2009
Subject: Question about iSCSI
In-Reply-To: <ba4aa9cb0905250630l7f06c319vf144fd5609e025f0@mail.gmail.com>
References: <ba4aa9cb0905250630l7f06c319vf144fd5609e025f0@mail.gmail.com>
Message-ID: <200905251056.09987.lists@jnielsen.net>

On Monday 25 May 2009 09:30:40 am Francisco Cabrita wrote:
> info:
> I have built a NAS server under FreeBSD. Geom RAID5 over 3 hard disks
> and iSCSI target0 created.
> It is up and running without problems "exporting" a SCSI driver to a Ms
> Windows 2000 Server with Microsoft iSCSI Inititator driver.
> The volume is NTFS.
>
> doubt:
> I have read multiple "old" posts around the web that I can't connect
> multiple initiators (w2k clients) to the same target. Is this true
> nowadays?

You do not want two machines to have write access to the same SCSI device 
at the same time unless you use a filesystem designed for such access. 
NTFS is not such a filesystem. Just hooking two win2k boxes to the same 
iSCSI target to do NTFS will cause problems.

Alternatives:
Microsoft clustering (two or more nodes coordinate to provide certain 
services, the disk volume is only active on one of them at any given 
time)
Some real clustered filesystem designed for shared access. I don't know of 
any for Windows off the top of my head but I haven't ever looked in to 
it.
Use the setup you have already with one w2k client, then use Windows 
filesharing to export the volume to other clients.
Avoid the middleman, drop iSCSI and just use Samba on the NAS box. (Or NFS 
if you want to dabble in Microsoft's Services for Unix... (cue scary 
music))

> Facts:
> I really need at least two w2k clients to the same "storage NAS". Any
> tip about how to solve this?
> Maybe some kind of failover technique between both w2k servers?

This is similar to the MS clustering option, there may be more manual ways 
to achieve the same effect.

> I really appreciate your help. Thanks in advance
> PS: I am thinking about sending this email to FreeBSD Cluster ML too.

Note that if you want to stick with iSCSI on the FreeBSD side then your 
questions are really Microsoft-centered, so non-FreeBSD resources may be 
more appropriate. Questions about configuring your FreeBSD storage box to 
allow concurrent access by multiple clients that happen to be running 
Windows would be appropriate on the FreeBSD-questions mailing list.

JN
From francisco.cabrita at gmail.com  Mon May 25 15:33:36 2009
From: francisco.cabrita at gmail.com (Francisco Cabrita)
Date: Mon May 25 15:33:42 2009
Subject: Question about iSCSI
In-Reply-To: <200905251056.09987.lists@jnielsen.net>
References: <ba4aa9cb0905250630l7f06c319vf144fd5609e025f0@mail.gmail.com>
	<200905251056.09987.lists@jnielsen.net>
Message-ID: <ba4aa9cb0905250833m45d609ddk4b5e40c097cba94c@mail.gmail.com>

Hi John,

I first want to say many thanks for your reply.

On Mon, May 25, 2009 at 3:56 PM, John Nielsen <lists@jnielsen.net> wrote:

> On Monday 25 May 2009 09:30:40 am Francisco Cabrita wrote:
> > info:
> > I have built a NAS server under FreeBSD. Geom RAID5 over 3 hard disks
> > and iSCSI target0 created.
> > It is up and running without problems "exporting" a SCSI driver to a Ms
> > Windows 2000 Server with Microsoft iSCSI Inititator driver.
> > The volume is NTFS.
> >
> > doubt:
> > I have read multiple "old" posts around the web that I can't connect
> > multiple initiators (w2k clients) to the same target. Is this true
> > nowadays?
>
> You do not want two machines to have write access to the same SCSI device
> at the same time unless you use a filesystem designed for such access.
> NTFS is not such a filesystem. Just hooking two win2k boxes to the same
> iSCSI target to do NTFS will cause problems.


yep I had such problems.


>
>
> Alternatives:
> Microsoft clustering (two or more nodes coordinate to provide certain
> services, the disk volume is only active on one of them at any given
> time)


I need to seek a Windows expert down here :)


>
> Some real clustered filesystem designed for shared access. I don't know of
> any for Windows off the top of my head but I haven't ever looked in to
> it.
> Use the setup you have already with one w2k client, then use Windows
> filesharing to export the volume to other clients.
> Avoid the middleman, drop iSCSI and just use Samba on the NAS box. (Or NFS
> if you want to dabble in Microsoft's Services for Unix... (cue scary
> music))


In another company I have another FreeBSD NAS exporting a NFS volume to
another FreeBSD Samba server, on wich I share some directories to Ms XP
clients. I have no iSCSI on it and it's just fine. Almost 3 years up and
running.

Avoiding iSCSI it's a nice possibility but, on this new scenario the volumes
are exported to both w2k PDC and w2k BDC. My client relies upon a very
granular permission scheme. I don't know if I can handle this without a NTFS
volume. (If I'm not wrong, we can't format a NTFS partition under FreeBSD)


>
>
> > Facts:
> > I really need at least two w2k clients to the same "storage NAS". Any
> > tip about how to solve this?
> > Maybe some kind of failover technique between both w2k servers?
>
> This is similar to the MS clustering option, there may be more manual ways
> to achieve the same effect.


I prefer not to use manual tasks.


>
> > I really appreciate your help. Thanks in advance
> > PS: I am thinking about sending this email to FreeBSD Cluster ML too.
>
> Note that if you want to stick with iSCSI on the FreeBSD side then your
> questions are really Microsoft-centered, so non-FreeBSD resources may be
> more appropriate. Questions about configuring your FreeBSD storage box to
> allow concurrent access by multiple clients that happen to be running
> Windows would be appropriate on the FreeBSD-questions mailing list.


Yes you are totally right. I just want to say I am truly grateful about your
reply because my primary doubt was about the possibility or not to "map"
multiple initiators to one target. And, where is the best place to ask a
thing and get a really valid answer? yep FreeBSD ML :)

I will try to explore your tips about MS Clustering.

Once again Thanks
Francisco Cabrita


>
>
> JN
>



-- 
blog: http://sufixo.com/raw
http://www.linkedin.com/in/franciscocabrita
From ivoras at freebsd.org  Tue May 26 15:05:02 2009
From: ivoras at freebsd.org (Ivan Voras)
Date: Tue May 26 15:05:09 2009
Subject: Question about iSCSI
In-Reply-To: <ba4aa9cb0905250833m45d609ddk4b5e40c097cba94c@mail.gmail.com>
References: <ba4aa9cb0905250630l7f06c319vf144fd5609e025f0@mail.gmail.com>	<200905251056.09987.lists@jnielsen.net>
	<ba4aa9cb0905250833m45d609ddk4b5e40c097cba94c@mail.gmail.com>
Message-ID: <gvgv7v$vs4$1@ger.gmane.org>

Francisco Cabrita wrote:

> Avoiding iSCSI it's a nice possibility but, on this new scenario the volumes
> are exported to both w2k PDC and w2k BDC. My client relies upon a very
> granular permission scheme. I don't know if I can handle this without a NTFS
> volume. (If I'm not wrong, we can't format a NTFS partition under FreeBSD)

No, and it wouldn't be of any use to you since Samba would still see it
as a POSIX file system.

OTOH, Samba has some rudimentary support for ACLs (it's a built-time
option) and UFS2 has ACL support by default, though it needs to be
enabled in fstab (see mount(8)), so depending on how convoluted are your
requirements, it might or might not work.

See for example: http://aisalen.wordpress.com/2007/08/10/acls-on-samba/


-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 260 bytes
Desc: OpenPGP digital signature
Url : http://lists.freebsd.org/pipermail/freebsd-scsi/attachments/20090526/7ef0cb78/signature.pgp
From francisco.cabrita at gmail.com  Tue May 26 15:44:03 2009
From: francisco.cabrita at gmail.com (Francisco Cabrita)
Date: Tue May 26 15:44:09 2009
Subject: Question about iSCSI
In-Reply-To: <gvgv7v$vs4$1@ger.gmane.org>
References: <ba4aa9cb0905250630l7f06c319vf144fd5609e025f0@mail.gmail.com>
	<200905251056.09987.lists@jnielsen.net>
	<ba4aa9cb0905250833m45d609ddk4b5e40c097cba94c@mail.gmail.com>
	<gvgv7v$vs4$1@ger.gmane.org>
Message-ID: <ba4aa9cb0905260844p72a68735w9f3cbb4408fd64a9@mail.gmail.com>

Hi Ivan,

On Tue, May 26, 2009 at 3:44 PM, Ivan Voras <ivoras@freebsd.org> wrote:

> Francisco Cabrita wrote:
>
> > Avoiding iSCSI it's a nice possibility but, on this new scenario the
> volumes
> > are exported to both w2k PDC and w2k BDC. My client relies upon a very
> > granular permission scheme. I don't know if I can handle this without a
> NTFS
> > volume. (If I'm not wrong, we can't format a NTFS partition under
> FreeBSD)
>
> No, and it wouldn't be of any use to you since Samba would still see it
> as a POSIX file system.
>

>
> OTOH, Samba has some rudimentary support for ACLs (it's a built-time
> option) and UFS2 has ACL support by default, though it needs to be
> enabled in fstab (see mount(8)), so depending on how convoluted are your
> requirements, it might or might not work.
>
> See for example: http://aisalen.wordpress.com/2007/08/10/acls-on-samba/
>

Oh great! This sounds very very good and simple too!

Resume
1) we have "options UFS_ACL" in our generic; so I can use UFS2 to host user
data;
2) Build Samba 3 with "ACL_SUPPORT=yes";
3) Add acls flag to fstab.

Et voi l?. Tests, lots of tests.

You guys really opened my mind! I don't know yet if I'm gonna use this way
on this particular project, but is very nice to know this stuff.

Once again, Many thanks :)

Best Regards,
Francisco Cabrita



-- 
blog: http://sufixo.com/raw
http://www.linkedin.com/in/franciscocabrita