All of lore.kernel.org
 help / color / mirror / Atom feed
From: Wolfgang Pfeiffer <roto@gmx.net>
To: Stefan Richter <stefanr@s5r6.in-berlin.de>
Cc: linuxppc-dev@ozlabs.org, billfink@mindspring.com,
	linux1394-devel@lists.sourceforge.net
Subject: Re: Broken Firewire 400/SCSI on ppc Powerbook5,8
Date: Sun, 3 Sep 2006 01:26:44 +0200	[thread overview]
Message-ID: <20060902232644.GB2814@localhost> (raw)
In-Reply-To: <44F9D8EF.6010101@s5r6.in-berlin.de>

On Sat, Sep 02, 2006 at 09:18:07PM +0200, Stefan Richter wrote:
> 
> Alas I am out of ideas. Perhaps you should purchase a new enclosure. 
> Before you do that, you could test the AluBook running Linux and TiBook 
> in target disk mode again to exclude the possibility of problems at the 
> AluBook's side. Use "hdparm -tT /dev/sda" to try a few actual block read 
> operations. This should show about 20 MByte/s. It is a read-only test 
> and therefore safe.

OK, I did this test with the unmounted Tibook /dev/sda  
(target mode). So I executed the one-liners below on the
alubook. /dev/sda should be the hard disk on the tibook:

####################################################

# /sbin/hdparm -tT /dev/sda

/dev/sda:
 Timing cached reads:   1244 MB in  2.00 seconds = 620.49 MB/sec
 Timing buffered disk reads:   34 MB in  3.02 seconds =  11.24 MB/sec
[root@ 01:21:02]# /sbin/hdparm -tT /dev/sda

/dev/sda:
 Timing cached reads:   1232 MB in  2.00 seconds = 615.19 MB/sec
 Timing buffered disk reads:   34 MB in  3.04 seconds =  11.17 MB/sec
[root@ 01:21:20]# /sbin/hdparm -tT /dev/sda

/dev/sda:
 Timing cached reads:   1260 MB in  2.00 seconds = 628.93 MB/sec
 Timing buffered disk reads:   36 MB in  3.07 seconds =  11.72 MB/sec
[root@ 01:21:35]#

##############################################################

Looks good, doesn't it?

Thanks again

Best Regards
Wolfgang

-- 
Wolfgang Pfeiffer: /ICQ: 286585973/ + + +  /AIM: crashinglinux/
http://profiles.yahoo.com/wolfgangpfeiffer

Key ID: E3037113
http://keyserver.mine.nu/pks/lookup?search=0xE3037113&fingerprint=on

  parent reply	other threads:[~2006-09-02 23:27 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-08-17 23:03 Broken Firewire 400/SCSI on ppc Powerbook5,8 Wolfgang Pfeiffer
2006-08-18  5:28 ` Bill Fink
2006-08-18 10:17   ` Wolfgang Pfeiffer
2006-08-19  9:32   ` Stefan Richter
2006-08-20  0:18     ` Bill Fink
2006-08-22  8:58       ` Stefan Richter
2006-08-18 23:49 ` Wolfgang Pfeiffer
2006-08-19  9:13   ` Stefan Richter
2006-08-20  1:31     ` Wolfgang Pfeiffer
2006-08-21  7:56       ` Stefan Richter
2006-08-21  0:29     ` Wolfgang Pfeiffer
2006-08-21  0:40       ` Wolfgang Pfeiffer
2006-08-23  0:28     ` Wolfgang Pfeiffer
2006-08-23  0:36       ` Wolfgang Pfeiffer
2006-08-23  1:50         ` [Correction #2] " Wolfgang Pfeiffer
2006-08-24 19:22       ` Wolfgang Pfeiffer
2006-08-24 19:43         ` Stefan Richter
2006-08-24 22:56           ` Wolfgang Pfeiffer
2006-09-02 19:18         ` Stefan Richter
2006-09-02 23:08           ` Wolfgang Pfeiffer
2006-09-02 23:28             ` Stefan Richter
2006-09-02 23:26           ` Wolfgang Pfeiffer [this message]
2006-09-04 16:58             ` Stefan Richter
2006-08-19  8:10 ` Stefan Richter

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=20060902232644.GB2814@localhost \
    --to=roto@gmx.net \
    --cc=billfink@mindspring.com \
    --cc=linux1394-devel@lists.sourceforge.net \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=stefanr@s5r6.in-berlin.de \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.