On Mon, Apr 16, 2018 at 8:28 AM, Steven Rostedt wrote:
> On Mon, 16 Apr 2018 14:31:49 +
> "Bean Huo (beanhuo)" wrote:
>
>> Print the request tag along with other information
>> while tracing a command.
>>
>> Signed-off-by: Bean Huo
Acked-by: Ra
Hello,
Currently I don't see any users of aio cancellation facility (except a
USB gadget driver).
I have a SATA controller and disk that both support the NCQ command
aborts, and I am thinking of ways to implement aio cancellation on
these devices in the kernel. The way I see it, at the time user
Hello James,
I haven't heard any feedback on this patch, so I was wondering if this
documentation patch is something you're considering to review?
Many thanks in advance,
Rajat
On Tue, Jun 9, 2015 at 10:43 AM, Rajat Jain wrote:
> Add documentation to describe the various scena
Add documentation to describe the various scenarios that the scsi_cmnd
may go through in its life time in the mid level driver - aborts,
failures, retries, error handling etc. The documentation has lots of
details including examples.
Signed-off-by: Rajat Jain
---
Hello James / linux-scsi
Hello James,
On Tue, May 26, 2015 at 11:15 AM, Rajat Jain wrote:
> Hello James / linux-scsi folks,
>
> On Wed, May 13, 2015 at 12:36 PM, Jonathan Corbet wrote:
>> On Tue, 12 May 2015 14:33:46 -0700
>> Rajat Jain wrote:
>>
>>> Add documentation to des
Hello James,
On Thu, Jun 4, 2015 at 1:27 PM, James Bottomley
wrote:
> On Thu, 2015-06-04 at 11:40 -0700, Rajat Jain wrote:
>> Each cmd timeout should result in scmd->retries++. Currently it happens
>> just only before a command is requeued back. However, if the LLD
>> eh_
at a command is tried.
Once allowed number of retries is reached, we proceed to standard
error handling procedure (abort etc.) by scheduling the command
for EH.
Signed-off-by: Rajat Jain
---
drivers/scsi/scsi_error.c | 11 +++
1 file changed, 11 insertions(+)
diff
Hello,
I was trying to test some failover and reliability features, and had
instrumented the iscsi low level driver to simulate failures when some
one tries to read the disk. I observed that* iscsi disk is discovered
and sd_probe_async() is called that ultimately tries to read the
partition table
Hello James / linux-scsi folks,
On Wed, May 13, 2015 at 12:36 PM, Jonathan Corbet wrote:
> On Tue, 12 May 2015 14:33:46 -0700
> Rajat Jain wrote:
>
>> Add documentation to describe the various scenarios that the scsi_cmnd
>> may go through in its life time in the mid
> > > A similar problem was noted with RHEL4, it seems the modules.pcimap
> > > and pci.ids file were correct, but the pcitable file contained entries
> > > for all ql[ae]23xx based HBAs to load qla2300.ko.
> > >
> > > It's my understanding that this was fixed for RHEL4 U1. Which distro
> > > are
On 7/27/05, Andrew Vasquez <[EMAIL PROTECTED]> wrote:
> On Tue, 26 Jul 2005, Rajat Jain wrote:
> > On 7/26/05, Greg KH <[EMAIL PROTECTED]> wrote:
> > > On Mon, Jul 25, 2005 at 11:02:39AM +0900, Rajat Jain wrote:
> > > > I'm using Kernel 2.
On 7/26/05, Greg KH <[EMAIL PROTECTED]> wrote:
> On Mon, Jul 25, 2005 at 11:02:39AM +0900, Rajat Jain wrote:
> > I'm using Kernel 2.6.9 and am having a Qlogic QLE2362 FC-HBA in my
> > system. I selected all the Qlogic SCSI drivers while buiding the
> > kernel. Now
Hi,
I do not know which list to put this problem on. And hence ...
I'm using Kernel 2.6.9 and am having a Qlogic QLE2362 FC-HBA in my
system. I selected all the Qlogic SCSI drivers while buiding the
kernel. Now the problem is that every time I reboot, I have to
MANUALLY modprobe the qla2322.ko mo
Hi,
I do not know whether this is the corect forum to discuss this, but I
recently saw a post related to qla2xxx driver and thought that I may get
some help. I'm using Linux kernel 2.6 and plan to use the qla2xxx driver.
The driver documentstion says it has the "qlascan" command which can help i
L
the HBAs???
Rajat
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] On Behalf Of Bryan Henderson
> Sent: Friday, April 01, 2005 4:57 AM
> To: Rajat Jain, Noida
> Cc: linux-scsi@vger.kernel.org
> Subject: Re: How to find which (physical) SCSI
"scsi add-single-device" command, but I have to supply Host number, channel,
ID and lun to it. I know that ID is set on the device it self, and hence
I'll be knowing it. But how do I know the host no of the HBA that I've added
the device to. Is it just trial and error?
TIA,
to supply Host number, channel,
ID and lun to it. I know that ID is set on the device it self, and hence
I'll be knowing it. But how do I know the host no of the HBA that I've added
the device to. Is it just trial and error?
TIA,
Rajat Jain
Disclaimer:
This message and any attachm
queue unplug
or
queue is about to get full or after a certain unplug timer value.
Hope it helps.
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] Behalf Of Rajat Jain, Noida
Sent: Tuesday, March 22, 2005 8:31 AM
To: linux-scsi@vger.kernel.org; linux-newbie@vg
Hi list,
Tracing the kernel 2.6.8 code I found that scsi_mod maintains separate
request queues for each SCSI device. It uses the block layer queuing
facility to do this. What I could not find out was that once a request is
queued into a queue (for a particular device), WHEN and HOW is the strate
Hi list,
Tracing the kernel 2.6.8 code I found that scsi_mod maintains separate
request queues for each SCSI device. It uses the block layer queuing
facility to do this. What I could not find out was that once a request is
queued into a queue (for a particular device), WHEN and HOW is the strateg
Bus. But again, I would have to RUN
that script manually, and it will have to ITERATE on the the possible target
Ids. Is there a better way?
Thanx a ton,
Rajat
-Original Message-
From: Bryan Henderson [mailto:[EMAIL PROTECTED]
Sent: Thursday, March 10, 2005 12:16 AM
To: Rajat Jain, Noid
Hi,
I'm new to SCSI. I would appreciate if some one can solve my query:
When a new SCSI device is added to a SCSI channel, how can we find out what
is the target ID of that device?
1) If a channel supports 8 SCSI devices, then each of the 8 ports will have
a specific Target ID. And any device
er to
Documentation/scsi/scsi_mid_low_api.txt).
Thanks & Regards,
Rajat Jain
HCL Technologies,
A-11, Sector 16, Noida-201301.
Ph: +91-120-2510701/702/813 Extn.3159
[EMAIL PROTECTED]
http://www.hcltech.com/
"...one of the main causes of the fall of the Roman Empire was that,
lack
do I
do that? Or how can I achieve this functionality?
Any pointers are welcome.
Thanks & regards,
Rajat Jain
HCL Technologies,
A-11, Sector 16, Noida-201301.
Ph: +91-120-2510701/702/813 Extn.3019
[EMAIL PROTECTED]
http://www.hcltech.com/
"...one of the main causes of the fal
be
called when ever a new SCSI device is detected on an existing HBA. How do I
do that? Or how can I achieve this functionality?
Any pointers are welcome.
Thanks & regards,
Rajat Jain
HCL Technologies,
A-11, Sector 16, Noida-201301.
Ph: +91-120-2510701/702/813 Extn.3019
[EMAIL PROTECTED]
nd lun.
But the removal will fail if the device is busy (e.g. if a file system on
the device is mounted).
Rajat Jain
HCL Technologies,
A-11, Sector 16, Noida-201301.
Ph: +91-120-2510701/702/813 Extn.3019
[EMAIL PROTECTED]
http://www.hcltech.com/
"...one of the main causes
An excerpt from the net ... Didn't ever personally try it though.
---
Description of new logging facility
The logging facility will make it much easier to troubleshoot problems in
the field. The basic idea is that it is possible to request debu
27 matches
Mail list logo
