From owner-freebsd-scsi@FreeBSD.ORG Mon Nov 13 11:08:37 2006 Return-Path: X-Original-To: freebsd-scsi@FreeBSD.org Delivered-To: freebsd-scsi@FreeBSD.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 32A6516A66C for ; Mon, 13 Nov 2006 11:08:37 +0000 (UTC) (envelope-from owner-bugmaster@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id DB95443D49 for ; Mon, 13 Nov 2006 11:08:36 +0000 (GMT) (envelope-from owner-bugmaster@FreeBSD.org) Received: from freefall.freebsd.org (linimon@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.4/8.13.4) with ESMTP id kADB8a2g091578 for ; Mon, 13 Nov 2006 11:08:36 GMT (envelope-from owner-bugmaster@FreeBSD.org) Received: (from linimon@localhost) by freefall.freebsd.org (8.13.4/8.13.4/Submit) id kADB8ZuK091574 for freebsd-scsi@FreeBSD.org; Mon, 13 Nov 2006 11:08:35 GMT (envelope-from owner-bugmaster@FreeBSD.org) Date: Mon, 13 Nov 2006 11:08:35 GMT Message-Id: <200611131108.kADB8ZuK091574@freefall.freebsd.org> X-Authentication-Warning: freefall.freebsd.org: linimon set sender to owner-bugmaster@FreeBSD.org using -f From: FreeBSD bugmaster To: freebsd-scsi@FreeBSD.org Cc: Subject: Current problem reports assigned to you X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 13 Nov 2006 11:08:37 -0000 Current FreeBSD problem reports Critical problems Serious problems S Tracker Resp. Description -------------------------------------------------------------------------------- o kern/27059 scsi [sym] SCSI subsystem hangs under heavy load on (Server o kern/28508 scsi problems with backup to Tandberg SLR40 strimmer o kern/39388 scsi ncr/sym drivers fail with 53c810 and more than 256MB m o kern/40895 scsi wierd kernel / device driver bug o kern/52638 scsi [panic] SCSI U320 on SMP server won't run faster than s kern/57398 scsi [mly] Current fails to install on mly(4) based RAID di o kern/60598 scsi wire down of scsi devices conflicts with config o kern/60641 scsi [sym] Sporadic SCSI bus resets with 53C810 under load s kern/61165 scsi [panic] kernel page fault after calling cam_send_ccb o kern/74627 scsi [ahc] [hang] Adaptec 2940U2W Can't boot 5.3 o kern/81887 scsi [aac] Adaptec SCSI 2130S aac0: GetDeviceProbeInfo comm o kern/90282 scsi [sym] SCSI bus resets cause loss of ch device o kern/92798 scsi [ahc] SCSI problem with timeouts o kern/93128 scsi [sym] FreeBSD 6.1 BETA 1 has problems with Symbios/LSI o kern/94838 scsi Kernel panic while mounting SD card with lock switch o o kern/99954 scsi [ahc] reading from DVD failes on 6.x (regression) 16 problems total. Non-critical problems S Tracker Resp. Description -------------------------------------------------------------------------------- o kern/23314 scsi aic driver fails to detect Adaptec 1520B unless PnP is o kern/35234 scsi World access to /dev/pass? (for scanner) requires acce o kern/38828 scsi [feature request] DPT PM2012B/90 doesn't work o kern/44587 scsi dev/dpt/dpt.h is missing defines required for DPT_HAND o kern/76178 scsi [ahd] Problem with ahd and large SCSI Raid system o kern/96133 scsi [scsi] [patch] add scsi quirk for joyfly 128mb flash u o kern/103702 scsi [cam] [patch] ChipsBnk: Unsupported USB memory stick 7 problems total. From owner-freebsd-scsi@FreeBSD.ORG Mon Nov 13 18:42:31 2006 Return-Path: X-Original-To: freebsd-scsi@freebsd.org Delivered-To: freebsd-scsi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2436716A500 for ; Mon, 13 Nov 2006 18:42:31 +0000 (UTC) (envelope-from ml@t-b-o-h.net) Received: from vjofn.tucs-beachin-obx-house.com (vjofn.tucs-beachin-obx-house.com [204.107.90.128]) by mx1.FreeBSD.org (Postfix) with ESMTP id C953643D5D for ; Mon, 13 Nov 2006 18:36:40 +0000 (GMT) (envelope-from ml@t-b-o-h.net) Received: from himinbjorg.tucs-beachin-obx-house.com (c-69-249-95-230.hsd1.nj.comcast.net [69.249.95.230]) (authenticated bits=0) by vjofn.tucs-beachin-obx-house.com (8.12.9/8.12.9) with ESMTP id kADIadrI089680 for ; Mon, 13 Nov 2006 13:36:40 -0500 (EST) Received: from himinbjorg.tucs-beachin-obx-house.com (localhost.tucs-beachin-obx-house.com [127.0.0.1]) by himinbjorg.tucs-beachin-obx-house.com (8.13.6/8.13.6) with ESMTP id kADIaYnw077143 for ; Mon, 13 Nov 2006 13:36:34 -0500 (EST) (envelope-from ml@t-b-o-h.net) Received: (from tbohml@localhost) by himinbjorg.tucs-beachin-obx-house.com (8.13.6/8.13.6/Submit) id kADIaYdh077142 for freebsd-scsi@freebsd.org; Mon, 13 Nov 2006 13:36:34 -0500 (EST) (envelope-from tbohml) From: "Tuc at T-B-O-H.NET" Message-Id: <200611131836.kADIaYdh077142@himinbjorg.tucs-beachin-obx-house.com> To: freebsd-scsi@freebsd.org Date: Mon, 13 Nov 2006 13:36:34 -0500 (EST) X-Mailer: ELM [version 2.5 PL8] MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Subject: Camcontrol not changing modepage X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 13 Nov 2006 18:42:31 -0000 Hi, I have a disk thats doing : THE FOLLOWING DISK SECTORS COULD NOT BE READ: 1131461, So I himinbjorg# camcontrol modepage da0 -m 1 AWRE (Auto Write Reallocation Enbld): 1 ARRE (Auto Read Reallocation Enbld): 0 TB (Transfer Block): 1 RC (Read Continuous): 1 EER (Enable Early Recovery): 1 PER (Post Error): 1 DTE (Disable Transfer on Error): 1 DCR (Disable Correction): 1 Read Retry Count: 191 Correction Span: 250 Head Offset Count: 204 Data Strobe Offset Count: 5 Write Retry Count: 70 Recovery Time Limit: 3880 I want to turn ARRE on, which is supposedly able to be re-written : himinbjorg# camcontrol modepage da0 -m 1 -P 1 AWRE (Auto Write Reallocation Enbld): 1 ARRE (Auto Read Reallocation Enbld): 0 TB (Transfer Block): 1 RC (Read Continuous): 1 EER (Enable Early Recovery): 1 PER (Post Error): 1 DTE (Disable Transfer on Error): 1 DCR (Disable Correction): 1 Read Retry Count: 191 Correction Span: 250 Head Offset Count: 204 Data Strobe Offset Count: 5 Write Retry Count: 70 Recovery Time Limit: 3880 I do the "-e" and insert in my editor : ARRE (Auto Read Reallocation Enbld): 1 And I get back : camcontrol: modepage entry "ARRE (Auto Read Reallocation Enbld)" is read-only; skipping. Am I doing something wrong? Thanks, Tuc From owner-freebsd-scsi@FreeBSD.ORG Mon Nov 13 19:56:59 2006 Return-Path: X-Original-To: freebsd-scsi@freebsd.org Delivered-To: freebsd-scsi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5AE9B16A417 for ; Mon, 13 Nov 2006 19:56:59 +0000 (UTC) (envelope-from ken@nargothrond.kdm.org) Received: from nargothrond.kdm.org (nargothrond.kdm.org [70.56.43.81]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7370843EA9 for ; Mon, 13 Nov 2006 19:53:12 +0000 (GMT) (envelope-from ken@nargothrond.kdm.org) Received: from nargothrond.kdm.org (localhost [127.0.0.1]) by nargothrond.kdm.org (8.13.6/8.13.6) with ESMTP id kADJrBMZ086803; Mon, 13 Nov 2006 12:53:11 -0700 (MST) (envelope-from ken@nargothrond.kdm.org) Received: (from ken@localhost) by nargothrond.kdm.org (8.13.6/8.13.6/Submit) id kADJrBhS086802; Mon, 13 Nov 2006 12:53:11 -0700 (MST) (envelope-from ken) Date: Mon, 13 Nov 2006 12:53:11 -0700 From: "Kenneth D. Merry" To: "Tuc at T-B-O-H.NET" Message-ID: <20061113195311.GA85979@nargothrond.kdm.org> References: <200611131836.kADIaYdh077142@himinbjorg.tucs-beachin-obx-house.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200611131836.kADIaYdh077142@himinbjorg.tucs-beachin-obx-house.com> User-Agent: Mutt/1.4.2i X-Virus-Scanned: ClamAV 0.88.1/2190/Mon Nov 13 02:31:57 2006 on nargothrond.kdm.org X-Virus-Status: Clean Cc: freebsd-scsi@freebsd.org Subject: Re: Camcontrol not changing modepage X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 13 Nov 2006 19:56:59 -0000 On Mon, Nov 13, 2006 at 13:36:34 -0500, Tuc at T-B-O-H.NET wrote: > Hi, > > I have a disk thats doing : > > THE FOLLOWING DISK SECTORS COULD NOT BE READ: 1131461, > > So I > > himinbjorg# camcontrol modepage da0 -m 1 > AWRE (Auto Write Reallocation Enbld): 1 > ARRE (Auto Read Reallocation Enbld): 0 > TB (Transfer Block): 1 > RC (Read Continuous): 1 > EER (Enable Early Recovery): 1 > PER (Post Error): 1 > DTE (Disable Transfer on Error): 1 > DCR (Disable Correction): 1 > Read Retry Count: 191 > Correction Span: 250 > Head Offset Count: 204 > Data Strobe Offset Count: 5 > Write Retry Count: 70 > Recovery Time Limit: 3880 > > I want to turn ARRE on, which is supposedly > able to be re-written : > > himinbjorg# camcontrol modepage da0 -m 1 -P 1 > AWRE (Auto Write Reallocation Enbld): 1 > ARRE (Auto Read Reallocation Enbld): 0 The page control value of 1 that you specified tells camcontrol to ask for the bitmask of changeable bits in the page. The 0, above, tells us that we cannot change the ARRE value. > TB (Transfer Block): 1 > RC (Read Continuous): 1 > EER (Enable Early Recovery): 1 > PER (Post Error): 1 > DTE (Disable Transfer on Error): 1 > DCR (Disable Correction): 1 > Read Retry Count: 191 > Correction Span: 250 > Head Offset Count: 204 > Data Strobe Offset Count: 5 > Write Retry Count: 70 > Recovery Time Limit: 3880 > > I do the "-e" and insert in my editor : > > ARRE (Auto Read Reallocation Enbld): 1 > > And I get back : > > camcontrol: modepage entry "ARRE (Auto Read Reallocation Enbld)" is read-only; skipping. > > > Am I doing something wrong? That's the expected response for a bit marked read-only. It looks like your drive is probably broken, though. It's returning the same values when you set the page control field to 1 as the current values. It should return a bitmask instead. What drive vendor/model is this? In any case, it probably doesn't matter that much. If the drive can't read the block you're trying to read, there is a 99% likelihood that it won't be able to do ARRE on that particular block, either. ARRE is only useful for blocks that can still be reconstructed with ECC information, not for blocks that are beyond repair. Although it would be good to turn on ARRE for any future bad blocks that can be recovered on read. I think the only way to do that with camcontrol for this particular drive would probably be with 'camcontrol cmd'. You'd have to format the CDB and mode page by hand. 'camcontrol modepage' won't let you edit fields that the drive says can't be edited. Ken -- Kenneth Merry ken@kdm.org From owner-freebsd-scsi@FreeBSD.ORG Mon Nov 13 22:24:03 2006 Return-Path: X-Original-To: freebsd-scsi@freebsd.org Delivered-To: freebsd-scsi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 46E2016A51A for ; Mon, 13 Nov 2006 22:24:03 +0000 (UTC) (envelope-from ml@t-b-o-h.net) Received: from vjofn.tucs-beachin-obx-house.com (vjofn.tucs-beachin-obx-house.com [204.107.90.128]) by mx1.FreeBSD.org (Postfix) with ESMTP id B4B7D43D4C for ; Mon, 13 Nov 2006 22:22:51 +0000 (GMT) (envelope-from ml@t-b-o-h.net) Received: from himinbjorg.tucs-beachin-obx-house.com (c-69-249-95-230.hsd1.nj.comcast.net [69.249.95.230]) (authenticated bits=0) by vjofn.tucs-beachin-obx-house.com (8.12.9/8.12.9) with ESMTP id kADMMorI096189; Mon, 13 Nov 2006 17:22:50 -0500 (EST) Received: from himinbjorg.tucs-beachin-obx-house.com (localhost.tucs-beachin-obx-house.com [127.0.0.1]) by himinbjorg.tucs-beachin-obx-house.com (8.13.6/8.13.6) with ESMTP id kADMMjqV081206; Mon, 13 Nov 2006 17:22:45 -0500 (EST) (envelope-from ml@t-b-o-h.net) Received: (from tbohml@localhost) by himinbjorg.tucs-beachin-obx-house.com (8.13.6/8.13.6/Submit) id kADMMiAG081205; Mon, 13 Nov 2006 17:22:44 -0500 (EST) (envelope-from tbohml) From: "Tuc at T-B-O-H.NET" Message-Id: <200611132222.kADMMiAG081205@himinbjorg.tucs-beachin-obx-house.com> To: ken@kdm.org (Kenneth D. Merry) Date: Mon, 13 Nov 2006 17:22:44 -0500 (EST) In-Reply-To: <20061113195311.GA85979@nargothrond.kdm.org> X-Mailer: ELM [version 2.5 PL8] MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Cc: freebsd-scsi@freebsd.org Subject: Re: Camcontrol not changing modepage X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 13 Nov 2006 22:24:03 -0000 > > I want to turn ARRE on, which is supposedly > > able to be re-written : > > > > himinbjorg# camcontrol modepage da0 -m 1 -P 1 > > AWRE (Auto Write Reallocation Enbld): 1 > > ARRE (Auto Read Reallocation Enbld): 0 > > The page control value of 1 that you specified tells camcontrol to ask for > the bitmask of changeable bits in the page. > > The 0, above, tells us that we cannot change the ARRE value. > OOOOOOOOHHHHHHH! I thought it was telling me that it was available for R/W, AND that it was currently set to zero..... > > > TB (Transfer Block): 1 > > RC (Read Continuous): 1 > > EER (Enable Early Recovery): 1 > > PER (Post Error): 1 > > DTE (Disable Transfer on Error): 1 > > DCR (Disable Correction): 1 > > Read Retry Count: 191 > > Correction Span: 250 > > Head Offset Count: 204 > > Data Strobe Offset Count: 5 > > Write Retry Count: 70 > > Recovery Time Limit: 3880 > And I thought that because the above ones were not 0 or 1... > > > > > I do the "-e" and insert in my editor : > > > > ARRE (Auto Read Reallocation Enbld): 1 > > > > And I get back : > > > > camcontrol: modepage entry "ARRE (Auto Read Reallocation Enbld)" is read-only; skipping. > > > > > > Am I doing something wrong? > > That's the expected response for a bit marked read-only. It looks like > your drive is probably broken, though. It's returning the same values when > you set the page control field to 1 as the current values. It should > return a bitmask instead. > > What drive vendor/model is this? > umass0: Generic Mass Storage Device, rev 2.00/1.41, addr 2 da0 at umass-sim0 bus 0 target 0 lun 0 da0: Removable Direct Access SCSI-2 device da0: 1.000MB/s transfers da0: 3999MB (8191998 512 byte sectors: 255H 63S/T 509C) USB pendrive...... > > In any case, it probably doesn't matter that much. If the drive can't read > the block you're trying to read, there is a 99% likelihood that it won't be > able to do ARRE on that particular block, either. ARRE is only useful for > blocks that can still be reconstructed with ECC information, not for blocks > that are beyond repair. > I was hoping it would "try" to move it, and mark it bad so I can atleast continue to use it as is. If something was destroyed, atleast I can get the rest of the information. > > Although it would be good to turn on ARRE for any future bad blocks that > can be recovered on read. > > I think the only way to do that with camcontrol for this particular drive > would probably be with 'camcontrol cmd'. You'd have to format the CDB and > mode page by hand. 'camcontrol modepage' won't let you edit fields that > the drive says can't be edited. > This is *W-A-Y* out of my league...... :-/ Thanks, Tuc From owner-freebsd-scsi@FreeBSD.ORG Mon Nov 13 22:38:24 2006 Return-Path: X-Original-To: freebsd-scsi@freebsd.org Delivered-To: freebsd-scsi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3836B16A4AB for ; Mon, 13 Nov 2006 22:38:24 +0000 (UTC) (envelope-from jfruge4@lsu.edu) Received: from gate012.lsu.edu (gate012.ocs.lsu.edu [130.39.184.214]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4CC1443E80 for ; Mon, 13 Nov 2006 22:34:49 +0000 (GMT) (envelope-from jfruge4@lsu.edu) Received: from [130.39.198.198] ([130.39.198.198]) by gate012.lsu.edu (Lotus Domino Release 6.0.3) with ESMTP id 2006111316342835-5259 ; Mon, 13 Nov 2006 16:34:28 -0600 From: Joshua =?ISO-8859-1?Q?Frug=E9?= To: freebsd-scsi@freebsd.org Date: Mon, 13 Nov 2006 16:34:28 -0600 Message-Id: <1163457268.15851.17.camel@localhost> Mime-Version: 1.0 X-Mailer: Evolution 2.8.1 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=UTF-8 Subject: problems with serverraid 8i on an ibm x260 X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 13 Nov 2006 22:38:24 -0000 Hello, I am running freebsd 6.1 (amd64) on an ibm x260 and getting these errors: dmesg: g_vfs_done():aacd0s1a[WRITE(offset=3D16567468032, length=3D16384)]error =3D= 5 aacd0: hard error cmd=3Dwrite 1673028351-1673028382 and in messages : Nov 12 23:59:14 nms kernel: aac0: COMMAND 0xffffffff8bd3b2c0 TIMEOUT AFTER 50189 SECONDS Nov 12 23:59:34 nms kernel: aac0: COMMAND 0xffffffff8bd3b2c0 TIMEOUT AFTER 50209 SECONDS Nov 12 23:59:54 nms kernel: aac0: COMMAND 0xffffffff8bd3b2c0 TIMEOUT AFTER 50229 SECONDS The system will lock, and require a manual reboot. =20 Has anyone run into this before, or can point me in the right direction to look for answers? Thanks, --=20 Joshua Frug=C3=A9 jfruge4@lsu.edu Louisiana State University Information Technology Services=20 From owner-freebsd-scsi@FreeBSD.ORG Mon Nov 13 22:43:28 2006 Return-Path: X-Original-To: freebsd-scsi@freebsd.org Delivered-To: freebsd-scsi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8593616A52E for ; Mon, 13 Nov 2006 22:43:28 +0000 (UTC) (envelope-from ken@nargothrond.kdm.org) Received: from nargothrond.kdm.org (nargothrond.kdm.org [70.56.43.81]) by mx1.FreeBSD.org (Postfix) with ESMTP id ACC9443DD3 for ; Mon, 13 Nov 2006 22:42:29 +0000 (GMT) (envelope-from ken@nargothrond.kdm.org) Received: from nargothrond.kdm.org (localhost [127.0.0.1]) by nargothrond.kdm.org (8.13.6/8.13.6) with ESMTP id kADMgHxK095131; Mon, 13 Nov 2006 15:42:17 -0700 (MST) (envelope-from ken@nargothrond.kdm.org) Received: (from ken@localhost) by nargothrond.kdm.org (8.13.6/8.13.6/Submit) id kADMgHHO095130; Mon, 13 Nov 2006 15:42:17 -0700 (MST) (envelope-from ken) Date: Mon, 13 Nov 2006 15:42:17 -0700 From: "Kenneth D. Merry" To: "Tuc at T-B-O-H.NET" Message-ID: <20061113224217.GA94669@nargothrond.kdm.org> References: <20061113195311.GA85979@nargothrond.kdm.org> <200611132222.kADMMiAG081205@himinbjorg.tucs-beachin-obx-house.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200611132222.kADMMiAG081205@himinbjorg.tucs-beachin-obx-house.com> User-Agent: Mutt/1.4.2i X-Virus-Scanned: ClamAV 0.88.1/2191/Mon Nov 13 11:37:53 2006 on nargothrond.kdm.org X-Virus-Status: Clean Cc: freebsd-scsi@freebsd.org Subject: Re: Camcontrol not changing modepage X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 13 Nov 2006 22:43:28 -0000 On Mon, Nov 13, 2006 at 17:22:44 -0500, Tuc at T-B-O-H.NET wrote: > > > I want to turn ARRE on, which is supposedly > > > able to be re-written : > > > > > > himinbjorg# camcontrol modepage da0 -m 1 -P 1 > > > AWRE (Auto Write Reallocation Enbld): 1 > > > ARRE (Auto Read Reallocation Enbld): 0 > > > > The page control value of 1 that you specified tells camcontrol to ask for > > the bitmask of changeable bits in the page. > > > > The 0, above, tells us that we cannot change the ARRE value. > > > OOOOOOOOHHHHHHH! I thought it was telling me that it was > available for R/W, AND that it was currently set to zero..... > > > > > TB (Transfer Block): 1 > > > RC (Read Continuous): 1 > > > EER (Enable Early Recovery): 1 > > > PER (Post Error): 1 > > > DTE (Disable Transfer on Error): 1 > > > DCR (Disable Correction): 1 > > > Read Retry Count: 191 > > > Correction Span: 250 > > > Head Offset Count: 204 > > > Data Strobe Offset Count: 5 > > > Write Retry Count: 70 > > > Recovery Time Limit: 3880 > > > And I thought that because the above ones were not 0 or 1... > > > > > > > > I do the "-e" and insert in my editor : > > > > > > ARRE (Auto Read Reallocation Enbld): 1 > > > > > > And I get back : > > > > > > camcontrol: modepage entry "ARRE (Auto Read Reallocation Enbld)" is read-only; skipping. > > > > > > > > > Am I doing something wrong? > > > > That's the expected response for a bit marked read-only. It looks like > > your drive is probably broken, though. It's returning the same values when > > you set the page control field to 1 as the current values. It should > > return a bitmask instead. > > > > What drive vendor/model is this? > > > umass0: Generic Mass Storage Device, rev 2.00/1.41, addr 2 > da0 at umass-sim0 bus 0 target 0 lun 0 > da0: Removable Direct Access SCSI-2 device > da0: 1.000MB/s transfers > da0: 3999MB (8191998 512 byte sectors: 255H 63S/T 509C) > > USB pendrive...... That explains things... > > > > In any case, it probably doesn't matter that much. If the drive can't read > > the block you're trying to read, there is a 99% likelihood that it won't be > > able to do ARRE on that particular block, either. ARRE is only useful for > > blocks that can still be reconstructed with ECC information, not for blocks > > that are beyond repair. > > > I was hoping it would "try" to move it, and mark it bad so I can > atleast continue to use it as is. If something was destroyed, atleast I > can get the rest of the information. Your best bet is to write to that individual sector. Since the drive seems to support write reallocation, that should allow it to remap that sector, and the rest of the drive should be useable. One way to try to pull all of the accessible data off the drive is phk's 'recoverdisk' program, located in /usr/src/tools/tools/recoverdisk. It will pull as many blocks as it can off the drive. You could pull off as many blocks as you can into a file that is an image of the drive, and then dd that image back over the drive itself. > > Although it would be good to turn on ARRE for any future bad blocks that > > can be recovered on read. > > > > I think the only way to do that with camcontrol for this particular drive > > would probably be with 'camcontrol cmd'. You'd have to format the CDB and > > mode page by hand. 'camcontrol modepage' won't let you edit fields that > > the drive says can't be edited. > > > This is *W-A-Y* out of my league...... :-/ recoverdisk may be a little easier to deal with. Ken -- Kenneth Merry ken@kdm.org From owner-freebsd-scsi@FreeBSD.ORG Tue Nov 14 01:35:53 2006 Return-Path: X-Original-To: freebsd-scsi@freebsd.org Delivered-To: freebsd-scsi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C502716A412 for ; Tue, 14 Nov 2006 01:35:53 +0000 (UTC) (envelope-from ml@t-b-o-h.net) Received: from vjofn.tucs-beachin-obx-house.com (vjofn.tucs-beachin-obx-house.com [204.107.90.128]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7E08F43D79 for ; Tue, 14 Nov 2006 01:35:49 +0000 (GMT) (envelope-from ml@t-b-o-h.net) Received: from himinbjorg.tucs-beachin-obx-house.com (c-69-249-95-230.hsd1.nj.comcast.net [69.249.95.230]) (authenticated bits=0) by vjofn.tucs-beachin-obx-house.com (8.12.9/8.12.9) with ESMTP id kAE1ZmrI001159; Mon, 13 Nov 2006 20:35:48 -0500 (EST) Received: from himinbjorg.tucs-beachin-obx-house.com (localhost.tucs-beachin-obx-house.com [127.0.0.1]) by himinbjorg.tucs-beachin-obx-house.com (8.13.6/8.13.6) with ESMTP id kAE1ZgF2084857; Mon, 13 Nov 2006 20:35:42 -0500 (EST) (envelope-from ml@t-b-o-h.net) Received: (from tbohml@localhost) by himinbjorg.tucs-beachin-obx-house.com (8.13.6/8.13.6/Submit) id kAE1ZgMs084856; Mon, 13 Nov 2006 20:35:42 -0500 (EST) (envelope-from tbohml) From: "Tuc at T-B-O-H.NET" Message-Id: <200611140135.kAE1ZgMs084856@himinbjorg.tucs-beachin-obx-house.com> To: ken@kdm.org (Kenneth D. Merry) Date: Mon, 13 Nov 2006 20:35:42 -0500 (EST) In-Reply-To: <20061113224217.GA94669@nargothrond.kdm.org> X-Mailer: ELM [version 2.5 PL8] MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Cc: freebsd-scsi@freebsd.org Subject: Re: Camcontrol not changing modepage X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 14 Nov 2006 01:35:53 -0000 > > Your best bet is to write to that individual sector. Since the drive seems > to support write reallocation, that should allow it to remap that sector, > and the rest of the drive should be useable. > > One way to try to pull all of the accessible data off the drive is phk's > 'recoverdisk' program, located in /usr/src/tools/tools/recoverdisk. > > It will pull as many blocks as it can off the drive. > > You could pull off as many blocks as you can into a file that is an image > of the drive, and then dd that image back over the drive itself. > > recoverdisk may be a little easier to deal with. > I appreciate the help, but it didn't seem to help/work/etc. I just newfs'd it, but thanks again. Tuc (Personal question, are you related to a Karen Merry from MI and FL?) From owner-freebsd-scsi@FreeBSD.ORG Tue Nov 14 02:18:44 2006 Return-Path: X-Original-To: freebsd-scsi@freebsd.org Delivered-To: freebsd-scsi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 89B9C16A4EE for ; Tue, 14 Nov 2006 02:18:44 +0000 (UTC) (envelope-from ken@nargothrond.kdm.org) Received: from nargothrond.kdm.org (nargothrond.kdm.org [70.56.43.81]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1462D43F62 for ; Tue, 14 Nov 2006 02:15:29 +0000 (GMT) (envelope-from ken@nargothrond.kdm.org) Received: from nargothrond.kdm.org (localhost [127.0.0.1]) by nargothrond.kdm.org (8.13.6/8.13.6) with ESMTP id kAE2FK5a005027; Mon, 13 Nov 2006 19:15:20 -0700 (MST) (envelope-from ken@nargothrond.kdm.org) Received: (from ken@localhost) by nargothrond.kdm.org (8.13.6/8.13.6/Submit) id kAE2FKkR005026; Mon, 13 Nov 2006 19:15:20 -0700 (MST) (envelope-from ken) Date: Mon, 13 Nov 2006 19:15:20 -0700 From: "Kenneth D. Merry" To: "Tuc at T-B-O-H.NET" Message-ID: <20061114021520.GA4995@nargothrond.kdm.org> References: <20061113224217.GA94669@nargothrond.kdm.org> <200611140135.kAE1ZgMs084856@himinbjorg.tucs-beachin-obx-house.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200611140135.kAE1ZgMs084856@himinbjorg.tucs-beachin-obx-house.com> User-Agent: Mutt/1.4.2i X-Virus-Scanned: ClamAV 0.88.1/2191/Mon Nov 13 11:37:53 2006 on nargothrond.kdm.org X-Virus-Status: Clean Cc: freebsd-scsi@freebsd.org Subject: Re: Camcontrol not changing modepage X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 14 Nov 2006 02:18:44 -0000 On Mon, Nov 13, 2006 at 20:35:42 -0500, Tuc at T-B-O-H.NET wrote: > > > > Your best bet is to write to that individual sector. Since the drive seems > > to support write reallocation, that should allow it to remap that sector, > > and the rest of the drive should be useable. > > > > One way to try to pull all of the accessible data off the drive is phk's > > 'recoverdisk' program, located in /usr/src/tools/tools/recoverdisk. > > > > It will pull as many blocks as it can off the drive. > > > > You could pull off as many blocks as you can into a file that is an image > > of the drive, and then dd that image back over the drive itself. > > > > recoverdisk may be a little easier to deal with. > > > I appreciate the help, but it didn't seem to help/work/etc. I > just newfs'd it, but thanks again. Glad you got it working, sorry you lost your data. Keep in mind that newfs doesn't overwrite every sector on the disk, but as you write files and fill up the disk, you should end up writing every sector. > (Personal question, are you related to a Karen Merry from MI and > FL?) Nope. Ken -- Kenneth Merry ken@kdm.org From owner-freebsd-scsi@FreeBSD.ORG Wed Nov 15 04:24:04 2006 Return-Path: X-Original-To: freebsd-scsi@freebsd.org Delivered-To: freebsd-scsi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 38BEF16A40F for ; Wed, 15 Nov 2006 04:24:04 +0000 (UTC) (envelope-from lydianconcepts@gmail.com) Received: from nf-out-0910.google.com (nf-out-0910.google.com [64.233.182.191]) by mx1.FreeBSD.org (Postfix) with ESMTP id C2DAD43D58 for ; Wed, 15 Nov 2006 04:24:02 +0000 (GMT) (envelope-from lydianconcepts@gmail.com) Received: by nf-out-0910.google.com with SMTP id x37so145669nfc for ; Tue, 14 Nov 2006 20:24:01 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:mime-version:content-type:content-transfer-encoding:content-disposition; b=DpnZl1BXM3lmvnoXzme5VMydtr/OVzACRATqjjYJB4veOFHvx2ru5BM7tUrVZlAT8AhBf4mLayashwHQUIcWPDoPxFNw55ySOnwqjNEz554iZW3PViEJHYfy8MbAl57jmRnHtJzj8myL8Fl5Cqu+sn4gj7sJt3acubB8hviPY/c= Received: by 10.78.26.9 with SMTP id 9mr1820840huz.1163564641034; Tue, 14 Nov 2006 20:24:01 -0800 (PST) Received: by 10.78.199.15 with HTTP; Tue, 14 Nov 2006 20:23:55 -0800 (PST) Message-ID: <7579f7fb0611142023l614c0d3bj4559c0b26b5817b8@mail.gmail.com> Date: Tue, 14 Nov 2006 20:23:55 -0800 From: "Matthew Jacob" To: freebsd-scsi@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline Subject: basic domain validation patches- 3rd and final call X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 15 Nov 2006 04:24:04 -0000 Please review, or these will be going in as the basis for ongoing work. They aren't perfect, but I believe that they are a sorely needed start. Speak now or forever hold your piece. On 11/2/06, mjacob@freebsd.org wrote: > > See http://people.freebsd.org/~mjacob/DV_PATCHES > > The ANSI document on Domain Validation gives an algorithm for doing > Basic Domain Validation as, in part: > > Send an INQUIRY command to a SCSI device 3 times- twice with the > default transfer agreement and once with the transfer agreement set > to the fastest supported values. The Basic test fails when the first > 36 bytes of data returned at the negotiated synchronous speed does not > match the data received at the asynchronous transfer speed. In > addition, the Basic test fails if a CRC error (or parity error for > non-DT clocking) or a timeout occurs. If data miscompare occurs, the > test should be repeated (e.g., this could be due to the target changing > INQUIRY data during SCSI device initialization). After a finite number > of retries, if data miscompare recurs then fall-back should be > attempted (see 5.5.2). > > and 5.5.2 has: > > If Basic or Enhanced tests fail, a fall-back setting is set and the > tests are performed again. The recommended fall-back order is: > > 1. fast-160 > 2. fast-80 > 3. fast-40 (with DT clocking enabled) > 4. fast-40 (with ST clocking enabled) > 5. fast-20 > 6. fast-10; and > 7. asynchrnous transfer. > > I've done an implementation interwoven into the probe code in cam_xpt > such that the following occurs.. > > The normal sequence is: > > ... > INQUIRY (short) > INQUIRY (long) > ... > ('default' sync settings are enabled) > ... > PROBE_TUR_FOR_NEGOTIATION > > > I've changed to be: > > PROBE_TUR_FOR_NEGOTIATION > PROBE_INQUIRY_BASIC_DV1 > ... > PROBE_INQUIRY_BASIC_DV2 > ... > > The idea here is to leverage the two initial INQUIRY commands done at > async mode and compare with the last known one and to do *two* > additional INQUIRY commands (at speed) to see if they compare with the > last ASYNC long INQUIRY command. If they don't, we can do backoff and > just re-enter the state machine at PROBE_TUR_FOR_NEGOTIATION. > > The backoff doesn't do DT/ST settings, but just simply increments the > sync_period factor until we hit 0xf (5 MHz) and then drops to async. > > I don't mess with PPR settings on the theory that the SIM will do the > right thing with PPR settings depending on the values of sync period and > offset. > > By doing fault injection (e..g, failed compares) I've done some testing > and this *appears* to do what one would want. > > Any comments? I *know* there are people out there on this list who have > more experience with DV than I do so I'd appreciate some comments. > > -matt > > > > > _______________________________________________ > freebsd-scsi@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-scsi > To unsubscribe, send any mail to "freebsd-scsi-unsubscribe@freebsd.org" > From owner-freebsd-scsi@FreeBSD.ORG Wed Nov 15 04:45:46 2006 Return-Path: X-Original-To: freebsd-scsi@freebsd.org Delivered-To: freebsd-scsi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2753616A403 for ; Wed, 15 Nov 2006 04:45:46 +0000 (UTC) (envelope-from scottl@samsco.org) Received: from pooker.samsco.org (pooker.samsco.org [168.103.85.57]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7B57743D66 for ; Wed, 15 Nov 2006 04:45:45 +0000 (GMT) (envelope-from scottl@samsco.org) Received: from [192.168.254.11] (phobos.samsco.home [192.168.254.11]) (authenticated bits=0) by pooker.samsco.org (8.13.4/8.13.4) with ESMTP id kAF4jcrS098364; Tue, 14 Nov 2006 21:45:43 -0700 (MST) (envelope-from scottl@samsco.org) Message-ID: <455A9B72.4000605@samsco.org> Date: Tue, 14 Nov 2006 21:45:38 -0700 From: Scott Long User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X; en-US; rv:1.8.0.7) Gecko/20060910 SeaMonkey/1.0.5 MIME-Version: 1.0 To: Matthew Jacob References: <7579f7fb0611142023l614c0d3bj4559c0b26b5817b8@mail.gmail.com> In-Reply-To: <7579f7fb0611142023l614c0d3bj4559c0b26b5817b8@mail.gmail.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=-1.4 required=3.8 tests=ALL_TRUSTED autolearn=failed version=3.1.1 X-Spam-Checker-Version: SpamAssassin 3.1.1 (2006-03-10) on pooker.samsco.org Cc: freebsd-scsi@freebsd.org Subject: Re: basic domain validation patches- 3rd and final call X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 15 Nov 2006 04:45:46 -0000 Go for it! Matthew Jacob wrote: > Please review, or these will be going in as the basis for ongoing > work. They aren't perfect, but I believe that they are a sorely needed > start. Speak now or forever hold your piece. > > On 11/2/06, mjacob@freebsd.org wrote: >> >> See http://people.freebsd.org/~mjacob/DV_PATCHES >> >> The ANSI document on Domain Validation gives an algorithm for doing >> Basic Domain Validation as, in part: >> >> Send an INQUIRY command to a SCSI device 3 times- twice with the >> default transfer agreement and once with the transfer agreement set >> to the fastest supported values. The Basic test fails when the first >> 36 bytes of data returned at the negotiated synchronous speed does not >> match the data received at the asynchronous transfer speed. In >> addition, the Basic test fails if a CRC error (or parity error for >> non-DT clocking) or a timeout occurs. If data miscompare occurs, the >> test should be repeated (e.g., this could be due to the target changing >> INQUIRY data during SCSI device initialization). After a finite number >> of retries, if data miscompare recurs then fall-back should be >> attempted (see 5.5.2). >> >> and 5.5.2 has: >> >> If Basic or Enhanced tests fail, a fall-back setting is set and the >> tests are performed again. The recommended fall-back order is: >> >> 1. fast-160 >> 2. fast-80 >> 3. fast-40 (with DT clocking enabled) >> 4. fast-40 (with ST clocking enabled) >> 5. fast-20 >> 6. fast-10; and >> 7. asynchrnous transfer. >> >> I've done an implementation interwoven into the probe code in cam_xpt >> such that the following occurs.. >> >> The normal sequence is: >> >> ... >> INQUIRY (short) >> INQUIRY (long) >> ... >> ('default' sync settings are enabled) >> ... >> PROBE_TUR_FOR_NEGOTIATION >> >> >> I've changed to be: >> >> PROBE_TUR_FOR_NEGOTIATION >> PROBE_INQUIRY_BASIC_DV1 >> ... >> PROBE_INQUIRY_BASIC_DV2 >> ... >> >> The idea here is to leverage the two initial INQUIRY commands done at >> async mode and compare with the last known one and to do *two* >> additional INQUIRY commands (at speed) to see if they compare with the >> last ASYNC long INQUIRY command. If they don't, we can do backoff and >> just re-enter the state machine at PROBE_TUR_FOR_NEGOTIATION. >> >> The backoff doesn't do DT/ST settings, but just simply increments the >> sync_period factor until we hit 0xf (5 MHz) and then drops to async. >> >> I don't mess with PPR settings on the theory that the SIM will do the >> right thing with PPR settings depending on the values of sync period and >> offset. >> >> By doing fault injection (e..g, failed compares) I've done some testing >> and this *appears* to do what one would want. >> >> Any comments? I *know* there are people out there on this list who have >> more experience with DV than I do so I'd appreciate some comments. >> >> -matt >> >> >> >> >> _______________________________________________ >> freebsd-scsi@freebsd.org mailing list >> http://lists.freebsd.org/mailman/listinfo/freebsd-scsi >> To unsubscribe, send any mail to "freebsd-scsi-unsubscribe@freebsd.org" >> > _______________________________________________ > freebsd-scsi@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-scsi > To unsubscribe, send any mail to "freebsd-scsi-unsubscribe@freebsd.org" From owner-freebsd-scsi@FreeBSD.ORG Thu Nov 16 05:15:12 2006 Return-Path: X-Original-To: freebsd-scsi@freebsd.org Delivered-To: freebsd-scsi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7D87716A403 for ; Thu, 16 Nov 2006 05:15:12 +0000 (UTC) (envelope-from mjacob@freebsd.org) Received: from ns1.feral.com (ns1.feral.com [192.67.166.1]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3784343D53 for ; Thu, 16 Nov 2006 05:15:12 +0000 (GMT) (envelope-from mjacob@freebsd.org) Received: from ns1.feral.com (localhost [127.0.0.1]) by ns1.feral.com (8.13.8/8.13.8) with ESMTP id kAG5F1sP008060 for ; Wed, 15 Nov 2006 21:15:11 -0800 (PST) (envelope-from mjacob@freebsd.org) Received: from localhost (mjacob@localhost) by ns1.feral.com (8.13.8/8.13.8/Submit) with ESMTP id kAG5F1pL008057 for ; Wed, 15 Nov 2006 21:15:01 -0800 (PST) (envelope-from mjacob@freebsd.org) X-Authentication-Warning: ns1.feral.com: mjacob owned process doing -bs Date: Wed, 15 Nov 2006 21:15:01 -0800 (PST) From: mjacob@freebsd.org X-X-Sender: mjacob@ns1.feral.com To: freebsd-scsi@freebsd.org Message-ID: <20061115211433.R8053@ns1.feral.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Subject: amusing stumble for the 6 to 10 byte checking code X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: mjacob@freebsd.org List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 16 Nov 2006 05:15:12 -0000 This caught my eye this morning: (da0:isp1:0:0:0): WRITE(06). CDB: a 8 68 90 80 0 (da0:isp1:0:0:0): CAM Status: SCSI Status Error (da0:isp1:0:0:0): SCSI Status: Check Condition (da0:isp1:0:0:0): UNIT ATTENTION asc:29,1 (da0:isp1:0:0:0): Power on occurred (da0:isp1:0:0:0): Retrying Command (per Sense Data) (da0:isp1:0:0:0): READ(6)/WRITE(6) not supported, increasing minimum_cmd_size to 10. (da0:isp1:0:0:0): WRITE(10). CDB: 2a 0 0 8 68 90 0 0 80 0 (da0:isp1:0:0:0): CAM Status: SCSI Status Error (da0:isp1:0:0:0): SCSI Status: Check Condition (da0:isp1:0:0:0): ILLEGAL REQUEST asc:24,0 (da0:isp1:0:0:0): Invalid field in CDB (da0:isp1:0:0:0): Unretryable error I'm still trying to figure out what happened here. Anyone else seen this? From owner-freebsd-scsi@FreeBSD.ORG Thu Nov 16 06:11:59 2006 Return-Path: X-Original-To: freebsd-scsi@freebsd.org Delivered-To: freebsd-scsi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D9F3516A407; Thu, 16 Nov 2006 06:11:59 +0000 (UTC) (envelope-from ken@nargothrond.kdm.org) Received: from nargothrond.kdm.org (nargothrond.kdm.org [70.56.43.81]) by mx1.FreeBSD.org (Postfix) with ESMTP id 689A943D5C; Thu, 16 Nov 2006 06:11:59 +0000 (GMT) (envelope-from ken@nargothrond.kdm.org) Received: from nargothrond.kdm.org (localhost [127.0.0.1]) by nargothrond.kdm.org (8.13.6/8.13.6) with ESMTP id kAG6BwXU037469; Wed, 15 Nov 2006 23:11:58 -0700 (MST) (envelope-from ken@nargothrond.kdm.org) Received: (from ken@localhost) by nargothrond.kdm.org (8.13.6/8.13.6/Submit) id kAG6Bw1c037468; Wed, 15 Nov 2006 23:11:58 -0700 (MST) (envelope-from ken) Date: Wed, 15 Nov 2006 23:11:58 -0700 From: "Kenneth D. Merry" To: mjacob@freebsd.org Message-ID: <20061116061158.GA37070@nargothrond.kdm.org> References: <20061115211433.R8053@ns1.feral.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20061115211433.R8053@ns1.feral.com> User-Agent: Mutt/1.4.2i X-Virus-Scanned: ClamAV 0.88.1/2199/Wed Nov 15 20:54:28 2006 on nargothrond.kdm.org X-Virus-Status: Clean Cc: freebsd-scsi@freebsd.org Subject: Re: amusing stumble for the 6 to 10 byte checking code X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 16 Nov 2006 06:11:59 -0000 On Wed, Nov 15, 2006 at 21:15:01 -0800, mjacob@freebsd.org wrote: > > This caught my eye this morning: > > > (da0:isp1:0:0:0): WRITE(06). CDB: a 8 68 90 80 0 > (da0:isp1:0:0:0): CAM Status: SCSI Status Error > (da0:isp1:0:0:0): SCSI Status: Check Condition > (da0:isp1:0:0:0): UNIT ATTENTION asc:29,1 > (da0:isp1:0:0:0): Power on occurred > (da0:isp1:0:0:0): Retrying Command (per Sense Data) > (da0:isp1:0:0:0): READ(6)/WRITE(6) not supported, increasing > minimum_cmd_size to > 10. That shouldn't have happened in response to a unit attention. It should only happen if the SIM comes back with CAM_REQ_INVALID, or if the target comes back with an illegal request sense code. So there may have been another intervening error that caused the switchover. > (da0:isp1:0:0:0): WRITE(10). CDB: 2a 0 0 8 68 90 0 0 80 0 > (da0:isp1:0:0:0): CAM Status: SCSI Status Error > (da0:isp1:0:0:0): SCSI Status: Check Condition > (da0:isp1:0:0:0): ILLEGAL REQUEST asc:24,0 > (da0:isp1:0:0:0): Invalid field in CDB > (da0:isp1:0:0:0): Unretryable error Hmm. Illegal field, and not invalid command operation code? That's odd. What kind of drive is this? The CDB looks valid at first glance... > I'm still trying to figure out what happened here. Anyone else seen > this? Never seen it. Ken -- Kenneth Merry ken@kdm.org From owner-freebsd-scsi@FreeBSD.ORG Thu Nov 16 09:45:16 2006 Return-Path: X-Original-To: freebsd-scsi@freebsd.org Delivered-To: freebsd-scsi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 04BAE16A40F for ; Thu, 16 Nov 2006 09:45:16 +0000 (UTC) (envelope-from bounces@nabble.com) Received: from talk.nabble.com (www.nabble.com [72.21.53.35]) by mx1.FreeBSD.org (Postfix) with ESMTP id BC1B643D5E for ; Thu, 16 Nov 2006 09:45:15 +0000 (GMT) (envelope-from bounces@nabble.com) Received: from [72.21.53.38] (helo=jubjub.nabble.com) by talk.nabble.com with esmtp (Exim 4.50) id 1Gkdo0-0003yQ-IF for freebsd-scsi@freebsd.org; Thu, 16 Nov 2006 01:45:12 -0800 Message-ID: <7374466.post@talk.nabble.com> Date: Thu, 16 Nov 2006 01:45:12 -0800 (PST) From: djshetty To: freebsd-scsi@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Nabble-From: dhirajshetty.junk@mailnull.com Subject: Persistent Reservation X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 16 Nov 2006 09:45:16 -0000 Hi, I had a doubt. In order to persist the reservation we need to store some information like reservation keys, scope, type of reservation etc. Where exactly are such information stored and by whom ? Regards, Dhiraj -- View this message in context: http://www.nabble.com/Persistent-Reservation-tf2641860.html#a7374466 Sent from the freebsd-scsi mailing list archive at Nabble.com. From owner-freebsd-scsi@FreeBSD.ORG Thu Nov 16 16:36:18 2006 Return-Path: X-Original-To: freebsd-scsi@freebsd.org Delivered-To: freebsd-scsi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 29E1016A40F for ; Thu, 16 Nov 2006 16:36:18 +0000 (UTC) (envelope-from lydianconcepts@gmail.com) Received: from wr-out-0506.google.com (wr-out-0506.google.com [64.233.184.231]) by mx1.FreeBSD.org (Postfix) with ESMTP id DEDA243D4C for ; Thu, 16 Nov 2006 16:36:16 +0000 (GMT) (envelope-from lydianconcepts@gmail.com) Received: by wr-out-0506.google.com with SMTP id i20so177074wra for ; Thu, 16 Nov 2006 08:36:16 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=YSXYRz4V0ISXw3FILZGJQPnXCTzBKh5dlHB4mdnhvT2ijFIhkJZCA5n0DVtJM4FFeL2KlA9sg4ksnvdv0YcXZsiR1QlQW3X4RGIQfFVvXFpBuizKPeYbCDIfglF65Ee9dCXvYLbXM+4xkFTM41YZQwUlEnTrxRD8SfsadGy5HU8= Received: by 10.78.51.9 with SMTP id y9mr742323huy.1163694975938; Thu, 16 Nov 2006 08:36:15 -0800 (PST) Received: by 10.78.199.15 with HTTP; Thu, 16 Nov 2006 08:36:15 -0800 (PST) Message-ID: <7579f7fb0611160836t655c8100j31e300a37c0cc9dc@mail.gmail.com> Date: Thu, 16 Nov 2006 08:36:15 -0800 From: "Matthew Jacob" To: "Kenneth D. Merry" In-Reply-To: <20061116061158.GA37070@nargothrond.kdm.org> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <20061115211433.R8053@ns1.feral.com> <20061116061158.GA37070@nargothrond.kdm.org> Cc: freebsd-scsi@freebsd.org, mjacob@freebsd.org Subject: Re: amusing stumble for the 6 to 10 byte checking code X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 16 Nov 2006 16:36:18 -0000 > > That shouldn't have happened in response to a unit attention. It should > only happen if the SIM comes back with CAM_REQ_INVALID, or if the target > comes back with an illegal request sense code. So there may have been > another intervening error that caused the switchover. Yeah- but where? > > > (da0:isp1:0:0:0): WRITE(10). CDB: 2a 0 0 8 68 90 0 0 80 0 > > (da0:isp1:0:0:0): CAM Status: SCSI Status Error > > (da0:isp1:0:0:0): SCSI Status: Check Condition > > (da0:isp1:0:0:0): ILLEGAL REQUEST asc:24,0 > > (da0:isp1:0:0:0): Invalid field in CDB > > (da0:isp1:0:0:0): Unretryable error > > Hmm. Illegal field, and not invalid command operation code? That's odd. > What kind of drive is this? The CDB looks valid at first glance... > Yeah, this is what's puzzling me. This is a normal FC drive. Puzzled... From owner-freebsd-scsi@FreeBSD.ORG Thu Nov 16 17:38:44 2006 Return-Path: X-Original-To: freebsd-scsi@freebsd.org Delivered-To: freebsd-scsi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 74E8416A4A7; Thu, 16 Nov 2006 17:38:44 +0000 (UTC) (envelope-from ken@nargothrond.kdm.org) Received: from nargothrond.kdm.org (nargothrond.kdm.org [70.56.43.81]) by mx1.FreeBSD.org (Postfix) with ESMTP id E2B1743D5D; Thu, 16 Nov 2006 17:38:43 +0000 (GMT) (envelope-from ken@nargothrond.kdm.org) Received: from nargothrond.kdm.org (localhost [127.0.0.1]) by nargothrond.kdm.org (8.13.6/8.13.6) with ESMTP id kAGHcgde066352; Thu, 16 Nov 2006 10:38:42 -0700 (MST) (envelope-from ken@nargothrond.kdm.org) Received: (from ken@localhost) by nargothrond.kdm.org (8.13.6/8.13.6/Submit) id kAGHcgWQ066351; Thu, 16 Nov 2006 10:38:42 -0700 (MST) (envelope-from ken) Date: Thu, 16 Nov 2006 10:38:42 -0700 From: "Kenneth D. Merry" To: Matthew Jacob Message-ID: <20061116173842.GB64023@nargothrond.kdm.org> References: <20061115211433.R8053@ns1.feral.com> <20061116061158.GA37070@nargothrond.kdm.org> <7579f7fb0611160836t655c8100j31e300a37c0cc9dc@mail.gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <7579f7fb0611160836t655c8100j31e300a37c0cc9dc@mail.gmail.com> User-Agent: Mutt/1.4.2i X-Virus-Scanned: ClamAV 0.88.1/2200/Thu Nov 16 07:10:16 2006 on nargothrond.kdm.org X-Virus-Status: Clean Cc: freebsd-scsi@freebsd.org, mjacob@freebsd.org Subject: Re: amusing stumble for the 6 to 10 byte checking code X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 16 Nov 2006 17:38:44 -0000 On Thu, Nov 16, 2006 at 08:36:15 -0800, Matthew Jacob wrote: > >That shouldn't have happened in response to a unit attention. It should > >only happen if the SIM comes back with CAM_REQ_INVALID, or if the target > >comes back with an illegal request sense code. So there may have been > >another intervening error that caused the switchover. > > Yeah- but where? I dunno. I just took a quick look through CAM and the ISP driver for CAM_REQ_INVALID, and didn't see any obvious place that would return CAM_REQ_INVALID for a 6 byte write... Computers are causal, though, so I'm sure there's a reason in there *somewhere*... > >> (da0:isp1:0:0:0): WRITE(10). CDB: 2a 0 0 8 68 90 0 0 80 0 > >> (da0:isp1:0:0:0): CAM Status: SCSI Status Error > >> (da0:isp1:0:0:0): SCSI Status: Check Condition > >> (da0:isp1:0:0:0): ILLEGAL REQUEST asc:24,0 > >> (da0:isp1:0:0:0): Invalid field in CDB > >> (da0:isp1:0:0:0): Unretryable error > > > >Hmm. Illegal field, and not invalid command operation code? That's odd. > >What kind of drive is this? The CDB looks valid at first glance... > > > > Yeah, this is what's puzzling me. This is a normal FC drive. Puzzled... Yeah, definitely a weird error. I'd never expect a SCSI drive to reject a normal 10 byte write like that. There are no weird flags in the CDB, and the lba and length don't seem out of range at all... (Unless you've got a 200MB hard FC hard drive...) Ken -- Kenneth Merry ken@kdm.org From owner-freebsd-scsi@FreeBSD.ORG Thu Nov 16 18:09:12 2006 Return-Path: X-Original-To: freebsd-scsi@freebsd.org Delivered-To: freebsd-scsi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 524D816A417 for ; Thu, 16 Nov 2006 18:09:12 +0000 (UTC) (envelope-from mjacob@freebsd.org) Received: from ns1.feral.com (ns1.feral.com [192.67.166.1]) by mx1.FreeBSD.org (Postfix) with ESMTP id C5DF443D9D for ; Thu, 16 Nov 2006 18:08:52 +0000 (GMT) (envelope-from mjacob@freebsd.org) Received: from ns1.feral.com (localhost [127.0.0.1]) by ns1.feral.com (8.13.8/8.13.8) with ESMTP id kAGI8g2s010013; Thu, 16 Nov 2006 10:08:52 -0800 (PST) (envelope-from mjacob@freebsd.org) Received: from localhost (mjacob@localhost) by ns1.feral.com (8.13.8/8.13.8/Submit) with ESMTP id kAGI8gDw010010; Thu, 16 Nov 2006 10:08:42 -0800 (PST) (envelope-from mjacob@freebsd.org) X-Authentication-Warning: ns1.feral.com: mjacob owned process doing -bs Date: Thu, 16 Nov 2006 10:08:42 -0800 (PST) From: mjacob@freebsd.org X-X-Sender: mjacob@ns1.feral.com To: "Kenneth D. Merry" In-Reply-To: <20061116173842.GB64023@nargothrond.kdm.org> Message-ID: <20061116100713.D9739@ns1.feral.com> References: <20061115211433.R8053@ns1.feral.com> <20061116061158.GA37070@nargothrond.kdm.org> <7579f7fb0611160836t655c8100j31e300a37c0cc9dc@mail.gmail.com> <20061116173842.GB64023@nargothrond.kdm.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: freebsd-scsi@freebsd.org Subject: Re: amusing stumble for the 6 to 10 byte checking code X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: mjacob@freebsd.org List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 16 Nov 2006 18:09:12 -0000 On Thu, 16 Nov 2006, Kenneth D. Merry wrote: > On Thu, Nov 16, 2006 at 08:36:15 -0800, Matthew Jacob wrote: >>> That shouldn't have happened in response to a unit attention. It should >>> only happen if the SIM comes back with CAM_REQ_INVALID, or if the target >>> comes back with an illegal request sense code. So there may have been >>> another intervening error that caused the switchover. >> >> Yeah- but where? > > I dunno. I just took a quick look through CAM and the ISP driver for > CAM_REQ_INVALID, and didn't see any obvious place that would return > CAM_REQ_INVALID for a 6 byte write... > > Computers are causal, though, so I'm sure there's a reason in there > *somewhere*... > >>>> (da0:isp1:0:0:0): WRITE(10). CDB: 2a 0 0 8 68 90 0 0 80 0 >>>> (da0:isp1:0:0:0): CAM Status: SCSI Status Error >>>> (da0:isp1:0:0:0): SCSI Status: Check Condition >>>> (da0:isp1:0:0:0): ILLEGAL REQUEST asc:24,0 >>>> (da0:isp1:0:0:0): Invalid field in CDB >>>> (da0:isp1:0:0:0): Unretryable error >>> >>> Hmm. Illegal field, and not invalid command operation code? That's odd. >>> What kind of drive is this? The CDB looks valid at first glance... >>> >> >> Yeah, this is what's puzzling me. This is a normal FC drive. Puzzled... > > Yeah, definitely a weird error. I'd never expect a SCSI drive to reject a > normal 10 byte write like that. There are no weird flags in the CDB, and > the lba and length don't seem out of range at all... (Unless you've got a > 200MB hard FC hard drive...) Hmm- that might be lcue. It might have been one of my 50MB test virtual luns which *might* have had a bad label. That gives me a clue of where to go look for at least the second error- thanks! From owner-freebsd-scsi@FreeBSD.ORG Sat Nov 18 17:28:58 2006 Return-Path: X-Original-To: freebsd-scsi@freebsd.org Delivered-To: freebsd-scsi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 4F1DB16A514 for ; Sat, 18 Nov 2006 17:28:58 +0000 (UTC) (envelope-from driver@pasins.com) Received: from [195.210.225.166] (BSN-210-225-166.dial-up.dsl.siol.net [195.210.225.166]) by mx1.FreeBSD.org (Postfix) with ESMTP id A5C9443DC9 for ; Sat, 18 Nov 2006 17:28:12 +0000 (GMT) (envelope-from driver@pasins.com) Message-ID: <000c01c70b36$eb51e1e0$a6e1d2c3@xy40b87df0ffca> From: "Headlines" To: freebsd-scsi@freebsd.org Date: Sat, 18 Nov 2006 18:28:10 +0100 MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="----=_NextPart_000_0008_01C70B3F.4D1649E0" X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2900.2869 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2962 X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: IST X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 18 Nov 2006 17:28:58 -0000 ------=_NextPart_000_0008_01C70B3F.4D1649E0 Content-Type: text/plain; charset="windows-1250" Content-Transfer-Encoding: quoted-printable Stocks Quotes in attachement Kind blessing Heads amp. Corus and above Tatacorus of. Match Mittal Ratan inc in cites Tatas. Internet Limited rights. Muslims enraged Rashmee Lalltimes Networkthe Dutch ban? Letters to a Editor Sunday in Deep Focus. ------=_NextPart_000_0008_01C70B3F.4D1649E0--