Mailinglist Archive: opensuse (868 mails)

[John Andersen <jsamyth@xxxxxxxxx>]

On 5/17/2011 10:34 PM, auxsvr@xxxxxxxxx wrote:

> Regardless of the known kio_slave problems when moving files, your 
> description indicates that there is a problem at the hardware/driver 
> level, since errors are mentioned by the kernel SCSI layer. 

Well, these errors are NEVER triggered at the command line cp operation, and
the copy always completes uneventfully.

As I mentioned, I ran the test several times, tailing the logs all the while.


So removing the kio slaves from the equation eliminates the problem.
That would indicate there is nothing wrong with the hardware, and indeed
it has been operating fine for over a year, and has been connected
to several different linux machines during that time.

My sense is that kio has some timing that causes it to trigger
a scsi bus reset when the drive is busy buffering a large read
operation on a fragmented file system.  Once it gets the
above mentioned abort, it will never resume.

copy command never triggers any scsi bus resets, and it
simply lights up the drive and keeps it lit as it
copies the file, and it never dumps a single log message.

It sure looks to me like one userspace tool triggers log
messages and the other doesn't.



-- 
_____________________________________
---This space for rent---
-- 
To unsubscribe, e-mail: opensuse+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: opensuse+help@xxxxxxxxxxxx