Search:

From lsmod, I'm guessing the qlogic driver ?

qla2xxx 182945 11 qla2400

do you mean the actual volume manager such as LVM or Veritas Volume Manager?
sorry if I'm missing your question.

I checked in lsmod but didn't see anything that stuck out.

/proc/scsi/scsi shows:

Host: scsi1 Channel: 00 Id: 02 Lun: 00
Vendor: DGC Model: LUNZ Rev: 0219
Type: Direct-Access ANSI SCSI revision: 04

this is a disk which is part of an EMC CLARion array:

an inquiry on the disk shows (when its not pulled out):

Vendor Identification : DGC
Product Identification : RAID 0
Revision Number :...

thanks for that very important explanation. I really appreciate it.

one last bit of information. I was able to drop into the kernel via kdb during the hang and this is the stack trace:

RSP RIP Function (args)
0x100b2ed9b08...

thanks for all your help guys....I'll see what I find and post the result here. thanks again.

my mistake, it is still hanging on the read(), been staring at this too long :(

tried with fcntl(), I got passed the read() but then hang on the close(fd).

I'm sure I missed something here. Can someone have a look?
Not that familiar with fcntl()




int ...

tried with the open()/read() and the open with O_NONBLOCK but no luck.
wondering if adding O_NDELAY would help.

was just looking at that, going to try it but been reading that its not recommended...thanks

any idea how I would go about putting it in a non-blocking mode?
I've been looking around but haven't had much success....

I had tried an open() (read-only) and read() and got the same result....

thanks much for the pointers. Hopefully I can report back with what worked.

My apologizes, guess that's why email/internet is tough to hear tone in someone's voice. :)

Thanks for your help, I'll try to figure out the better way to do this.

very hostile.....thanks for the help?

in addition to my last response, what about in scenarios where we have failover and such.
If a disk goes bad, we should be able to recover.

thought maybe it would timeout at some point so any application doing a read or scan of devices wouldn't end up hanging.

I'm opening up a disk device. Trying to figure out if its a dos disk or not (on linux)

ran with sizeof(buffer) instead. Got same result. (hung in fread())

I printed the sizeof(buffer) in gdb before the hang, it was 512 as expected.

that was just a hack for now. I never get to that line anyway since I hang in the fread()....

I will try that, but I'm guessing you mean for future.
Or do you think me assuming the size is 512 might be wrong?

I have it defined as:



unsigned char buffer[512]

I tried using read() instead but still get the hang..... :(

fyi, this is on Redhat linux.....