public inbox for linux-scsi@vger.kernel.org
 help / color / mirror / Atom feed
From: Thomas Mueller <thomas@chaschperli.ch>
To: "Srinivas Naga Venkatasatya Pasagadugula - ERS,
	HCL Tech" <satyasrinivasp@hcl.com>
Cc: "linux-scsi@vger.kernel.org" <linux-scsi@vger.kernel.org>,
	"Geetha Gopalan, ERS-HCLTech" <geethagp@hcl.com>
Subject: Re: mvsas: blocked task on writing to tape
Date: Thu, 19 Aug 2010 19:41:09 +0200	[thread overview]
Message-ID: <4C6D6CB5.5030806@chaschperli.ch> (raw)
In-Reply-To: <6B62480106F2B34D8404CF2FDAA4D9EF96D9C4CBFF@CHN-HCLT-EVS06.HCLT.CORP.HCL.IN>

On 19.08.2010 17:40, Srinivas Naga Venkatasatya Pasagadugula - ERS, HCL 
Tech wrote:
 > Hi Thomas,
 > Need below information.
 > 1. Dmesg or /var/log/messages

partial output from dmesg from 2.6.35.2 kernel -> see my last mail. have 
no access to the system anymore today. can provide more tomorrow.

 > 2. Which kernel version you are using?

2.6.32-bpo.4-amd64 (debian pacakge, IMHO 2.6.32.11 with debian patches) 
is OK
2.6.32-bpo.5-amd64 (debian package, IMHO 2.6.32.15 with debian patches) 
is NOT OK
2.6.34-1-amd64 (debian package) is NOT OK
2.6.35.2  (compiled from kernel.org source) is NOT OK

 > 3. Are you running any applications?

as i told i was writing to a tape with btape (Bacula tape test tool, 
btape command "speed file_size=50"). It was writing the 4th file (50gb 
per file) when it stopped working

 > 4. Whether tape drive is discovered or not? As I was working with 
this same drive only. I never faced any problem with this drive.

see answer 3. i suspect the the SAS card (mvsas) not the drive to be the 
problem.

 > 5. Check whether this is working with 2.6.33 kernels or not?

no 2.6.33 kernel handy yet, could compile one tomorrow.

- Thomas

  reply	other threads:[~2010-08-19 17:47 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-08-19 13:34 mvsas: blocked task on writing to tape Thomas Mueller
2010-08-19 15:40 ` Srinivas Naga Venkatasatya Pasagadugula - ERS, HCL Tech
2010-08-19 17:41   ` Thomas Mueller [this message]
2010-08-20  6:47     ` Mikael Abrahamsson
2010-08-20  8:40       ` Thomas Mueller
     [not found]     ` <AANLkTi=q0q0UOq8gw6O1Q7aoD-X0VKcOST1r0AsOUtt=@mail.gmail.com>
     [not found]       ` <4C6E132F.40207@chaschperli.ch>
     [not found]         ` <AANLkTik2R0e__9W0bkvat0Ma95KgkUKBfe2cp=G-s=pQ@mail.gmail.com>
2010-08-20  9:26           ` Thomas Mueller
2010-08-20  8:56   ` Thomas Mueller

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4C6D6CB5.5030806@chaschperli.ch \
    --to=thomas@chaschperli.ch \
    --cc=geethagp@hcl.com \
    --cc=linux-scsi@vger.kernel.org \
    --cc=satyasrinivasp@hcl.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox