linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Guillaume Laures <guillaume.laures@noos.fr>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Tony Mantler <nicoya@apia.dhs.org>,
	Linux/PPC Development <linuxppc-dev@lists.linuxppc.org>
Subject: Re: st corruption
Date: 25 Mar 2001 22:08:13 +0200	[thread overview]
Message-ID: <200103252008.OAA17663@lists.linuxppc.org> (raw)
In-Reply-To: <Pine.LNX.4.05.10103252120020.13875-100000@callisto.of.borg>


Le 25 Mar 2001 21:21:20 +0200, Geert Uytterhoeven a écrit :
> On 25 Mar 2001, Guillaume Laures wrote:
> > > merida:/home/nicoya# md5sum testfile
> >
> > 13b37214355ea84d906a54bb14c1c0be  testfile
> >
> > > merida:/home/nicoya# tar -c testfile >/dev/st0
> > > merida:/home/nicoya# mv testfile testfile.1
> > > merida:/home/nicoya# tar -x </dev/st0
> > > merida:/home/nicoya# md5sum testfile
> >
> > 13b37214355ea84d906a54bb14c1c0be  testfile
> >
> > uname -a :
> > Linux shiner.gom.net 2.2.18-snd-bkport #26 Wed Feb 28 23:19:57 CET 2001
> > ppc unknown
> >
> > So no prob here either with close hardware.
>
> Thanks! Do you also have a 2.4.x kernel around?

Not yet for this machine, but soon. I'll keep you tuned.

I may do test on my G4 with an external enclosure (2.4.3-pre3, scsi =
sym53c1010-33-0 through sym53c8xx-1.7.3a-20010304)

Later,


--
GoM


** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/

  reply	other threads:[~2001-03-25 20:08 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-03-22 19:41 st corruption Geert Uytterhoeven
2001-03-22 23:14 ` Tony Mantler
2001-03-23  7:20   ` Geert Uytterhoeven
2001-03-23 13:22     ` Tony Mantler
2001-03-25 15:08   ` Guillaume Laures
2001-03-25 19:21     ` Geert Uytterhoeven
2001-03-25 20:08       ` Guillaume Laures [this message]
2001-03-27 18:26         ` Geert Uytterhoeven

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=200103252008.OAA17663@lists.linuxppc.org \
    --to=guillaume.laures@noos.fr \
    --cc=geert@linux-m68k.org \
    --cc=linuxppc-dev@lists.linuxppc.org \
    --cc=nicoya@apia.dhs.org \
    /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;
as well as URLs for NNTP newsgroup(s).