Stefan Richter wrote:
DervishD wrote at lkml:
Hi all :)
I know, this has been treated on the list before (year 2005) but
without any real solution I'm aware of.
I'm running kernel 2.6.20.14, and I have an ATAPI DVD writer that I
use with an IDE-to-USB adapter, so it appears as
James Bottomley wrote:
On Thu, 2007-07-05 at 14:06 -0700, Kristen Carlson Accardi wrote:
Since gendisk will now become part of struct scsi_device, we don't need
to store this value in any private data structs where they already store
scsi_device. This series cleans up a few drivers which did
Kristen Carlson Accardi wrote:
Since gendisk will now become part of struct scsi_device, we don't need
to store this value in any private data structs where they already store
scsi_device. This series cleans up a few drivers which did this.
Since a scsi_device object is usually a SCSI logical
Matthias Urlichs wrote:
Hello,
Yesterday I managed to buy a couple of SCA disks with a sector size of ...
*drumroll* ... 524.
What's the easiest way to re-format these to use 512 bytes?
Preferably without screwing up anything else on these things?
Umm, I hope you don't consider losing
James Bottomley wrote:
On Fri, 2007-06-29 at 15:34 +, Matthias Urlichs wrote:
Yesterday I managed to buy a couple of SCA disks with a sector size of ...
*drumroll* ... 524.
What's the easiest way to re-format these to use 512 bytes?
Preferably without screwing up anything else on these
[EMAIL PROTECTED] wrote:
On Tue, 05 Jun 2007, [EMAIL PROTECTED] wrote:
Hello
I'm seeing very slow writes on a Dell Precision 690 with the Dell SAS5
adapter, serving a RAID1 array of SATA-II disks.
It's very similar to the problem in FreeBSD, described here:
Parav Pandit wrote:
Hi,
Few basic questions on sg driver:
1. Are there any hooks that low level HBA driver needs
to implement - for providing support for SG (SCSI
generic) driver?
Or SG always interacts with scsi_mod and it is
transparent to the HBA drivers?
From the tldp How-to and
Randy Dunlap wrote:
Hi Doug,
scsi_debug.c says:
MODULE_PARM_DESC(every_nth, timeout every nth command(def=100));
I don't see where the default of 100 is set.
#define DEF_EVERY_NTH 0
...
static int scsi_debug_every_nth = DEF_EVERY_NTH;
Can you clarify for me, please?
Randy,
Randy Dunlap wrote:
From: Randy Dunlap [EMAIL PROTECTED]
Correct the module info text for the default value of
every_nth to 0.
Signed-off-by: Randy Dunlap [EMAIL PROTECTED]
Signed-off-by: Douglas Gilbert [EMAIL PROTECTED]
Doug Gilbert
---
drivers/scsi/scsi_debug.c |2 +-
1 file
sandip shete wrote:
Hi,
I recieved the following ASC/ASCQ values as Additional Sense data :
31/00.
I looked it up and found that it stands for MEDIUM FORMAT CORRUPTED.
Does it mean that the target disk has bad sectors?
That error may be reported after a disk is reset during a
FORMAT
Matthew Jacob wrote:
The FreeBSD problem was fixed by Scott Long a couple of days ago by
doing some cut through SAS stuff that enabled Write Cache for SATA
drives. Why LSI-Logic couldn't just blitheringly synthesize mode page
8 is beyond me, but okay.
I dunno whether the issue here is the
Pim Zandbergen wrote:
Is SMART support available for SATA drives in SAS enclosures?
I'm testing this setup
LSI Logic SAS3800X PCI-X SAS controller (mptsas driver)
Promise V-Trak J300S SAS/SATA enclosure/expander
12x Seagate ST3500630NS
Linux kernel 2.6.21.1 x86_64
Haefliger, Juerg wrote:
Hi,
Not sure if this is the right list for my question but I couldn't find a
more suitable place to ask it.
I'm trying to set the locator light of a disk in a SAS enclosure using
sg_ses but I'm not getting anywhere. I'm dumping the enclosure status
diagnostic page
Mark Lord's hdparm version 7.3 supports the SCSI to ATA
Translation (SAT) pass-through. So if SAT is supported,
this allows hdparm to access ATA (e.g. SATA disks) and
ATAPI (e.g. cd/dvd drives) devices behind SCSI transports.
Note that the SAT layer may be in the kernel (e.g. libata),
in a HBA's
Jens Axboe wrote:
On Mon, Apr 30 2007, Benny Halevy wrote:
Jens Axboe wrote:
On Sun, Apr 29 2007, James Bottomley wrote:
On Sun, 2007-04-29 at 18:48 +0300, Boaz Harrosh wrote:
FUJITA Tomonori wrote:
From: Boaz Harrosh [EMAIL PROTECTED]
Subject: [PATCH 4/4] bidi support: bidirectional
Boaz Harrosh wrote:
Following are 4 (large) patches for support of bidirectional
block I/O in kernel. (not including SCSI-ml or iSCSI)
The submitted work is against linux-2.6-block tree as of
2007/04/15, and will only cleanly apply in succession.
The patches are based on the RFC I sent 3
sdparm is a command line utility designed to get and set
SCSI device parameters (cf hdparm for ATA disks). The
parameters are held in mode pages. Apart from SCSI devices
(e.g. disks, tapes and enclosures) sdparm can be used on
any device that uses a SCSI command set. Virtually all CD/DVD
drives
James Bottomley wrote:
On Fri, 2007-04-06 at 08:51 -0700, Andrew Burgess wrote:
James Bottomley wrote:
It's actually a long standing bug in the 3w- driver. Apparently it
assumes request sense is always the use_sg == 0 case. This is what it
does on a request sense:
static int
the actual max_sectors value for
any raw SCSI transport.
Signed-off-by: Alan Stern [EMAIL PROTECTED]
Alan,
I have voiced my concerns about this earlier but I will
now sign off to unblock the process (and deal with the
consequences to sg users, if any).
Signed-off-by: Douglas Gilbert [EMAIL
Kai Makisara wrote:
On Tue, 3 Apr 2007, Andrew Morton wrote:
(cc's added, with permission)
On Tue, 3 Apr 2007 15:08:37 +0200
Kern Sibbald [EMAIL PROTECTED] wrote:
Hello,
I am the project manager for Bacula, an Open Source network backup program
that runs on all popular OSes. After
Attached is the SCSI generic version 4 interface, release
1.3
ChangeLog for release 1.3 [20070404]
- increase tag size to 64 bits to comply with SAM-4 and SRP
- add request_extra and spare_out2 for alignment
Doug Gilbert
SCSI Generic version 4 interface structure
James Smart wrote:
James Bottomley wrote:
-- each SAS object (host, device, expander, etc) has the own bsg
device
I think so; probably attached via the transport class.
FYI - I understand the idea of a bsg device per object, but really, for
something that is used rarely, it's a bunch
James Bottomley wrote:
On Sun, 2007-04-01 at 16:29 -0400, Douglas Gilbert wrote:
...
sas: phy3 added to port0, phy_mask:0x8
sas: DOING DISCOVERY on port 0, pid:2110
aic94xx: scb:0x80 timed out
This might be the problem.
I see this periodically when a phy goes out to lunch on my system
James Bottomley wrote:
On Sat, 2007-03-31 at 15:05 -0400, Douglas Gilbert wrote:
James, note the SAS address of the first expander.
Thanks, just checking ... what happens when you directly attach a disk?
Then I get what I term as udev hell. That is when
FC6 gets to the point during boot-up
Darrick J. Wong wrote:
Douglas Gilbert wrote:
So that is almost 12 months that I have been reporting
this driver as broken. Is it just me or my hardware?
I seem to recall you saying that the LSI Fusion card was plugged into
the same expander as the 48300? If so, does unplugging
Brian King wrote:
Currently, the scsi error handler will issue a START_UNIT
command if the drive indicates it needs its motor started
and the allow_restart flag is set in the scsi_device. If,
after the scsi error handler invokes a host adapter reset
due to error recovery, a device is in a
Mark Lobo wrote:
Hello!
I had a question about disabling the block layer for SCSI devices. We
have an embedded device, and it runs 2.4.30. We need to be able to
support a lot of SCSI devices (in the thousands) for our device, and we
talk to the devices via SG. We are facing a memory
I mentioned this idea a few weeks ago on this list: namely
to allow a sg pass-through request to use the mmap-ed
reserve buffer associated with another sg file descriptor.
In my experience mmap-ed IO using sg's reserve buffer mapped
into the user space is faster than direct IO schemes. However
Tejun Heo wrote:
Implement SBC START/STOP management. sdev-mange_start_stop is added.
When it's set to one, sd STOPs the device on suspend and shutdown and
STARTs it on resume. sdev-manage_start_stop defaults is in sdev
instead of scsi_disk cdev to allow -slave_config() override the
default
FUJITA Tomonori wrote:
From: Pete Wyckoff [EMAIL PROTECTED]
Subject: [PATCH] bsg: iovec support
Date: Thu, 1 Mar 2007 17:29:08 -0500
Support vectored IO as in SGv3. The iovec structure uses explicit
sizes to avoid the need for compat conversion.
Signed-off-by: Pete Wyckoff [EMAIL
FUJITA Tomonori wrote:
From: Douglas Gilbert [EMAIL PROTECTED]
Subject: Re: [PATCH] bsg: iovec support
Date: Mon, 19 Mar 2007 08:56:39 -0400
FUJITA Tomonori wrote:
From: Pete Wyckoff [EMAIL PROTECTED]
Subject: [PATCH] bsg: iovec support
Date: Thu, 1 Mar 2007 17:29:08 -0500
Support
Randy Dunlap wrote:
On Fri, 16 Mar 2007 11:14:51 -0500 James Bottomley wrote:
On Fri, 2007-03-16 at 08:06 -0700, Randy Dunlap wrote:
On Fri, 16 Mar 2007 09:27:26 -0500 James Bottomley wrote:
On Fri, 2007-03-16 at 16:05 +0900, Horms wrote:
+ err = pci_enable_device(pdev);
+ if
After reviewing this post by Pete Wyckoff:
http://marc.theaimsgroup.com/?l=linux-scsim=117278879816029w=2
I decided to update my sg v4 interface document originally
posted 20061106 which I will now call release 1.1 :
http://lwn.net/Articles/208082/
Pete was proposing to put back din_iovec_count
MasthanUsha wrote:
Hi All,
Any one og you have any idea on scsi inquiry command ?
I want to send an Inquiry command to a scsi device through sd path (.i.e.
/dev/sda or /dev/sdb) by using SG_IO ioctl. Please explain me...
If you look at http://www.torque.net/sg/sg3_utils.html
and fetch
dudekula mastan wrote:
Hi Gilbert,
Thanks for quick reply.
The example program (sg_Simple --- not only this all examples) is taking
/dev/sg path as input but I want /dev/sd path as input.
In the lk 2.6 series, it will also work for sd devices
(and hd devices if they happen to
Bryan Henderson wrote:
DOS partitions start partitions on odd-numbered sectors
I don't get this. If you mean partitions defined by the classic DOS
partition table format, then AFAICS, such a partition can start in any
sector.
Bryan,
Typically the first partition on a DOS partitioned disk
renuka apte wrote:
The 'Specify Initiator Ports' support in persistent reservation allows
the application client to send a bunch of transport IDs which identify
initiator ports. I would like to know the suggested format for these
transport IDs.
Mark Harvey wrote:
Looking thru this driver, I saw what looks to be a bug/typo if an error
occurs when
calling driver_register() from scsi_debug_init()
Cheers
Mark
--- scsi_debug-orig.c 2007-03-03 19:38:23.0 +1100
+++ scsi_debug.c2007-03-03 19:39:51.0 +1100
@@
Olaf Hering wrote:
Upcoming IBM pSeries firmware can boot from iscsi. To configure the
openfirmware boot-device string, we need to construct a correct
devicepath. This path includes the lun. Its currently not 100% clear
how exactly this lun value has to look like.
sg_luns may be the tool to
FUJITA Tomonori wrote:
From: Douglas Gilbert [EMAIL PROTECTED]
Subject: Re: [PATCH 3/3] tgt: fix scsi command leak
Date: Sat, 03 Mar 2007 11:58:19 -0500
FUJITA Tomonori wrote:
The failure to map user-space pages leads to scsi command leak. It can
happens mostly because of user-space daemon
[EMAIL PROTECTED] wrote:
There is no big changes between v4 and v5. I was able to fix
things in scsi tgt, so I could remove the weird arguements
the block helpers were taking for it. I also tried to break
up the patchset for easier viewing. The final patch also
takes care of the access_ok
Mike Christie wrote:
Douglas Gilbert wrote:
Mike,
I see you are removing the scatter_elem_sz parameter.
What decides the scatter gather element size? Can it
be greater than PAGE_SIZE?
Oh yeah, sorry I should have documented that.
I just made the code try to allocate as large a element
Martin K. Petersen wrote:
This patch series is the first batch of cleanups in an attempt to make
the SCSI printing more consistent and suitable for human consumption.
Previously a typical error looked like this:
sd 0:0:0:0: SCSI error: return code = 0x0802
sda: Current: sense
H. Peter Anvin wrote:
Ric Wheeler wrote:
We still have the following challenges:
(1) read-ahead often means that we will retry every bad sector at
least twice from the file system level. The first time, the fs read
ahead request triggers a speculative read that includes the bad sector
Pete Wyckoff wrote:
Use the status codes from the standard, not the shifted-by-one codes
that are marked deprecated in scsi.h. This makes bsg v4 status
report the same value as sg v3 status too.
Pete,
Good pick up. We certainly don't want to re-introduce
the SCSI status byte shift from the
James Bottomley wrote:
On Thu, 2007-02-22 at 11:59 +0530, MASTHAN DUDEKULA wrote:
Hi JAMES,
The following code is SG_IO equivalent of scsi ioctls
SCSI_TEST_UNIT_READY
unsigned char sense_b[32];
unsigned char turCmbBlk[] = {0x00, 0, 0, 0, 0, 0};
struct sg_io_hdr io_hdr;
Andrew Morton wrote:
On Fri, 16 Feb 2007 22:59:31 -0500 Douglas Gilbert [EMAIL PROTECTED] wrote:
The patch that I sent, shown at the end of this post,
is incomplete as it doesn't check the return value
from kzalloc(..., GFP_ATOMIC).
The diff which is in mainline now looks to be OK?
Yes
Elias,
If you want to define a SCSI operation code for
internal use within the kernel, please make sure
that the byte isn't in the range 0 to 255 (inclusive).
Those ones are either t10 defined, reserved or vendor
specific for logical_unit or target use.
IOW don't do it!
Better would be to flag
6 weeks ago:
http://marc.theaimsgroup.com/?l=linux-scsim=116797354920256w=2
I'm not sure if this patch is in the works or
not.
Doug Gilbert
Douglas Gilbert wrote:
James Bottomley wrote:
On Mon, 2007-02-12 at 20:06 -0800, Andrew Morton wrote:
This is fixed in mainline and I expect
FUJITA Tomonori wrote:
I created a git tree for makeshift sg version 4 tools:
http://www.kernel.org/git/?p=linux/kernel/git/tomo/sgv4-tools.git;a=summary
# not synchronized yet.
The interface has changed continuously (and will do). After mainline
inclusion, Doug's sg tools support sg
Jeff Garzik wrote:
On Wed, Feb 14, 2007 at 02:53:31AM +0900, FUJITA Tomonori wrote:
It seems that it would be better to bind bsg devices to request_queue
instead of gendisk. This enables any objects to define own
request_handler and create own bsg device (under sysfs).
Possible enhancements:
James,
I thought this had been addressed but I can't find a
trail on my laptop. A minimal patch is attached.
ChangeLog:
- Use GFP_ATOMIC for allocations that can be called
from the queuecommand() entry point
Signed-off-by: Douglas Gilbert [EMAIL PROTECTED]
Doug Gilbert
--- linux
Randy Dunlap wrote:
[lkml dropped] [old thread]
On Fri, 18 Aug 2006 11:11:39 +0200 Andreas Herrmann wrote:
On 18.08.2006 00:33 Stefan Richter [EMAIL PROTECTED] wrote:
Andreas Herrmann wrote:
Anyone interested in a script to conveniently interpret or change the
SCSI logging level? Such a
Bernardo Innocenti wrote:
Hello,
I've stumbled onto a strange performance problem on a new server:
reading from disks is fast (70-80MB/s), but writing is extremely
slow (13-15MB/s). I've measured it like this:
dd if=/dev/zero of=/dev/sdd bs=4096 count=65536 conv=fdatasync
65536+0
Cameron, Steve wrote:
I noticed that when I do two SG_IO ioctls to a target
device (say, tape drive, disk drive, whatever) in which
the first request is well formed (e.g. an inquiry) and the
second one has a malformed CDB, such that it gets check condition
with sense key == 5 (ILLEGAL
Cameron, Steve wrote:
Steve,
Even though the SCSI status is CHECK CONDITION, the data-in
buffer may still be transferred. One obvious example
is a READ command when the sense key is RECOVERED ERROR.
Yep, of course.
The sg driver and I suspect the block layer SG_IO do
not check the SCSI
Alan wrote:
The interesting point of this question is about the typically pattern of
IO errors. On a read, it is safe to assume that you will have issues
with some bounded numbers of adjacent sectors.
Which in theory you can get by asking the drive for the real sector size
from the ATA7
sg3_utils is a package of command line utilities for sending
SCSI (and some ATA) commands to devices. This package targets
the linux kernel (lk) 2.6 and lk 2.4 series. In the lk 2.6
series these utilities (except sgp_dd) can be used with any
devices that support the SG_IO ioctl. Ported to FreeBSD,
James Bottomley wrote:
On Thu, 2007-02-01 at 04:54 -0500, Jeff Garzik wrote:
Agreed... but that doesn't make it the /right/ thing to do ;-)
The logic behind the current code, which limits to the maximum size
allowed by an attached device on the port, is mainly to leverage the
SCSI layer as
Ric Wheeler wrote:
Jeff Garzik wrote:
Mark Lord wrote:
Eric D. Mudama wrote:
Actually, it's possibly worse, since each failure in libata will
generate 3-4 retries. With existing ATA error recovery in the
drives, that's about 3 seconds per retry on average, or 12 seconds
per failure.
Darrick J. Wong wrote:
libsas: Don't BUG when connecting two expanders via wide port
When a device is connected to an expander, the discovery process goes through
sas_ex_discover_dev to figure out what's attached to the phy. If it is the
case that the phy being discovered happens to be the
Ric Wheeler wrote:
Mark Lord wrote:
Eric D. Mudama wrote:
Actually, it's possibly worse, since each failure in libata will
generate 3-4 retries. With existing ATA error recovery in the
drives, that's about 3 seconds per retry on average, or 12 seconds
per failure. Multiply that by
Darrick J. Wong wrote:
Hi all,
This is a roll-up of all of my uncommitted patches against libsas
and aic94xx to date. The first patch features an important fix for an
incorrect port deformation after a phy reset event. The next two
patches in this set complete the reorganization of the
lsscsi is a utility that uses sysfs in linux 2.6 series kernels
to list information about SCSI devices and SCSI hosts. Both a
compact format (default) which is one line per device and a
classic format (like the output of 'cat /proc/scsi/scsi') are
supported.
Version 0.19 is available at
Aboo Valappil wrote:
Hi Stefan Richter,
Thanks everyone for their advice on this. As per your advice, I did the
following when the last user space target serving the scsi_host quits,
the queue command will do the following on the new commands coming through.
sc-result =
Benny Halevy wrote:
Douglas Gilbert wrote:
Boaz Harrosh wrote:
- Introduce a new enum dma_data_direction data_dir member in struct request.
and remove the RW bit from request-cmd_flag
- Add new API to query request direction.
- Adjust existing API and implementation.
- Cleanup wrong use
Boaz Harrosh wrote:
- Introduce a new enum dma_data_direction data_dir member in struct request.
and remove the RW bit from request-cmd_flag
- Add new API to query request direction.
- Adjust existing API and implementation.
- Cleanup wrong use of DMA_BIDIRECTIONAL
- Introduce new
Thayne Harmon wrote:
On Thu, Jan 11, 2007 at 1:15 PM, in message [EMAIL PROTECTED],
Douglas Gilbert [EMAIL PROTECTED] wrote:
Thayne Harmon wrote:
Gentlemen,
hwinfo, lshal, sysfs do not show the relationship for non- sg BLOCK devices
with there
associated Host Bus Adapter.
All devices
Aboo Valappil wrote:
Hi All,
Thanks everyone to have a look at this.
I think i modified to have the latest kernel support. Unfortunately I
could not test it with 2.6.20 kernel due to some issues in my laptop and
2.6.20 kernel. But it should work with 2.6.20 with this modification.
The
Aboo Valappil wrote:
Hi All,
I have tried this before but I guess I was unsuccessful in presenting it
properly in the mailing list. I think it is really useful especially for
prototyping and also for people who wants to develop their own scsi
targets and transports.
There are few people
Kristian Høgsberg wrote:
On 1/14/07, Stefan Richter [EMAIL PROTECTED] wrote:
There is no emulation going on here.
...
- .emulated= 1,
Not sure what this flag does, but I copied it over to fw-sbp2.c. If
it's bogus, I guess we should drop it from fw-sbp2.c too.
Tarjei Huse wrote:
Hi, I'm working on getting Linux to use my SATA drives on an IBM x306
running a HostRaid controller that uses the adaptech 9405w chipset.
I found this thread on the list:
http://thread.gmane.org/gmane.linux.scsi/29040/focus=29040
Basically Luben Tuikov developed the
Thayne Harmon wrote:
Gentlemen,
hwinfo, lshal, sysfs do not show the relationship for non-sg BLOCK devices
with there
associated Host Bus Adapter.
All devices (i.e. logical units) have a 4 element tuple
associated with them and the first element is the host
number. A HBA contains one or
Stefan Richter wrote:
Douglas Gilbert wrote:
john clyne wrote:
What do the different hostX in /sys/class/scsi_host corespond to? There are
seven hostX directories, 5 with sg_tablesize set to 128 and two set to 255.
A Linux host is a SCSI initiator port (e.g. FC) or a
SCSI initiator device
john clyne wrote:
Can anyone give me some guidance on where in the IO stack I might be running
into a 512KB limit on IO transfer sizes to an external FC device? I've
checked IO scheduler parameter
(/sys/block/dev/queue/{max_sectors_kb,max_hw_sectors_kb}. Both are set to
32767. I'm using
john clyne wrote:
What do the different hostX in /sys/class/scsi_host corespond to? There are
seven hostX directories, 5 with sg_tablesize set to 128 and two set to 255.
A Linux host is a SCSI initiator port (e.g. FC) or a
SCSI initiator device (e.g. SAS). Another way of looking
at a host is as
) but deselecting SYSFS_DEPRECATED
removes various symlinks which breaks earlier lsscsi
betas.
Thanks to the maintainers of various SCSI transports
for helping me find what information is available in
sysfs and testing code for me. They are named in the
CREDITS file.
Doug Gilbert
Douglas Gilbert wrote [2006/12
Alan Stern wrote:
Both scsi_device and scsi_target include a scsi_level field, and the
SCSI core makes a half-hearted effort to keep the values equal.
Ultimately this effort may be doomed, since as far as I know there is
no reason why all LUNs in a target must report the same ANSI-approved
** post from Eric Moore
which you and I also received:
On Thursday, January 04, 2007 9:39 PM, Douglas Gilbert wrote:
This patch makes the mptctl pass through available if
the mptsas driver is selected. Without this patch
if mptsas is the only fusion driver chosen, then
the mptctl
error injection support
(opts mask 0x10), similar mechanism to
recovered_error injection.
Signed-off-by: Douglas Gilbert [EMAIL PROTECTED]
Doug Gilbert
--- linux/drivers/scsi/scsi_debug.c 2006-11-30 10:00:01.0 -0500
+++ linux/drivers/scsi/scsi_debug.c2620rc3abo1 2007-01-04 21
Jens Axboe wrote:
On Thu, Jan 04 2007, James Bottomley wrote:
On Thu, 2007-01-04 at 12:21 +0100, Jens Axboe wrote:
I guess it's fully up to you how you want to solve it. The scheme seems
a little elaborate, but these error conditions are unlikely to ever been
seen in the wild, so no
Jens Axboe wrote:
Hi Doug,
resp_inquiry() does a GFP_KERNEL memory allocation, but it's not allowed
to from the queuecommand context. There's no good way to return this
error, so I used DID_ERROR which is used from similar paths. That
doesn't seem quite right though, it would be better to
Randy Dunlap wrote:
On Fri, 29 Dec 2006 08:02:17 -0800 Sumant Patro wrote:
See Documentation/SubmittingPatches:
Please include output of diffstat -p1 -w70 so that we can easily see
the scope of the changes.
and see Documentation/CodingStyle for comments below:
diff -uprN
Luben Tuikov wrote:
--- Douglas Gilbert [EMAIL PROTECTED] wrote:
In lk 2.6.20-rc2 (and probably earlier) the phy_identifier
attribute in the /sys/class/sas_device/end_device-*
directory is showing the wrong end of the point to point
link.
Phy identifiers on (dual ported) SAS disks
Stefan Richter wrote:
Delete some incorrect code, left over from the initial driver submission
in March 2001.
SBP-2 targets should provide sense data via the SBP-2 status block
(autosense). We have to pass the REQUEST_SENSE command through to
targets which don't implement autosense, if
This message is generated by sd when a disk is larger
than 2 TB. Does it need to be? Could it be a logging
message?
It is also badly worded as the imperative try suggests
that the user needs to find a utility that sends a READ
CAPACITY(16). And I was recently contacted by a user with
that in
In lk 2.6.20-rc2 (and probably earlier) the phy_identifier
attribute in the /sys/class/sas_device/end_device-*
directory is showing the wrong end of the point to point
link.
Phy identifiers on (dual ported) SAS disks are typically
0 and 1. For SATA disks the phy identifier should be 0.
# lsscsi
smp_utils is a package of command line utilities for invoking
SMP functions to monitor and manage SAS expanders. SMP is the
Serial Attached SCSI (SAS) Management Protocol (SMP). A SAS Host
Bus Adapter (HBA) includes a SMP initiator (along with a SSP and
STP initiator). A SAS expander contains a
James Bottomley wrote:
On Thu, 2006-12-07 at 01:10 -0500, Douglas Gilbert wrote:
The change proposed by James Bottomley that prompted
the beta has not materialized.
You'll have to remind me: which change was this?
James,
Yes, I'm fuzzy on the details as well. Here is part of
the lsscsi
Jeff Garzik wrote:
Darrick J. Wong wrote:
The Quantum GoVault SATAPI removable disk device returns ATA_ERR in
response to a REPORT LUNS packet. If this happens to an ATAPI device
that is attached to a SAS controller (this is the case with sas_ata),
the device does not load because SCSI won't
James Bottomley wrote:
On Mon, 2006-12-04 at 15:32 -0800, Darrick J. Wong wrote:
The Quantum GoVault SATAPI removable disk device returns ATA_ERR in
response to a REPORT LUNS packet. If this happens to an ATAPI device
that is attached to a SAS controller (this is the case with sas_ata),
the
wasting keystrokes.
On Tue, 5 Dec 2006, Douglas Gilbert wrote:
Apart from sensibly yielding the max size in bytes, your patch
has the added benefit of allowing non-block devices (e.g. tape,
processor and enclosure services) to find out what limit the
OS/host has placed on each command's maximum
James Bottomley wrote:
On Wed, 2006-12-06 at 18:49 +0100, Joerg Schilling wrote:
Please keep in mind: all CD/DVD burners are SCSI devices.
This is probably semantics, but nowadays, SCSI means SPI (or parallel
SCSI). I think you're trying to say that they're all devices that obey
the MMC
James Bottomley wrote:
On Wed, 2006-12-06 at 13:38 -0500, Douglas Gilbert wrote:
SPI is dead. Get used to it. SCSI has not meant SPI for
years. We should be in the business of disabusing people
of that idea, not reinforcing it.
I don't believe I said anything in favour of or against SPI
The last announcement I made to this list about lsscsi
was back in March and that was a beta for lsscsi version
0.18 . The change proposed by James Bottomley that prompted
the beta has not materialized. So I decided to release
version 0.18 without fanfare a week ago and start adding
transport
Alan Stern wrote:
I decided to do this by email instead of bugzilla so that it would be
visible to everyone on the linux-scsi mailing list.
Re: http://bugzilla.kernel.org/show_bug.cgi?id=7026
To recap: Joerg Schilling needs to be able to retrieve the max_sectors
value for a SCSI device's
Bernd Schubert wrote:
Hi,
we have not bought the device yet, but presently in the process to do so.
Before we buy it, I want to know about problems in advance...
None that I'm aware of from the point of view of the
Linux SCSI subsystem (starting at about half way through
the lk 2.4 series or
Mark Haverkamp wrote:
I got this panic when loading the aic94xx module. The adapter is
connected to an HP MSA50 SAS enclosure with 3 72GB SAS disks.
Kernel 2.6.19-rc6-scsi-misc on an x86_64
---
aic94xx: Adaptec aic94xx SAS/SATA driver version 1.0.2 loaded
aic94xx: found Adaptec
James Bottomley wrote:
On Sun, 2006-11-26 at 17:31 +0100, roland wrote:
VMWare ESX refuses to create VMFS Filesystem on SATA disk, attached to a
onBoard SAS controller (lsi1068).
When i raid1 two SATA disks, it works, if i use a single SATA disk, the
controller seems to expose the disk
Mark Haverkamp wrote:
On Tue, 2006-11-28 at 13:46 -0800, Mark Haverkamp wrote:
On Tue, 2006-11-28 at 13:44 -0500, Douglas Gilbert wrote:
[ ... ]
I don't know if this helps, but I found the verbose option. Here is a
little debug output.
./smp_discover -v -p 12 -s
601 - 700 of 784 matches
Mail list logo
