mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Masaki Tsuji <jammasa@ma.nma.ne.jp>
To: linux-kernel@vger.kernel.org
Subject: Re: Can't read SCSI TAPE
Date: Wed, 25 Apr 2001 07:15:55 +0900	[thread overview]
Message-ID: <3AE5FB1B.BFF09D8@ma.nma.ne.jp> (raw)
In-Reply-To: <Pine.LNX.3.95.1010424123227.15270A-100000@chaos.analogic.com>

Dears,

"Richard B. Johnson" wrote:
> 
> Hmmm...
> 
> Masaki Tsuji <jammasa@ma.nma.ne.jp>
>                       ^^^^^^^^^^^^ ____ This address
> 
> ... was the address that did the CA-2000-17 attack on one of
> our machines a few weeks ago.
> 
> This is not an accusation, only an observation. You might
> want to tell your network administrator. Sombody at your
> site may be hacking systems.

We're very sorry!

Probabry it's 10th or 11th Apr, isn't it?
I was attacked too, but from outside.

I asked my network administrator about that on 13th Apr, and catched reason.
They said that their network equipments had some probrems, and fixed it.


> SCSI tape problems or your kind are usually caused by a different
> tape compression being used during record and playback. You should
> try to use `mt` to set the compression to something you like
> before you record, and the same compression when you play back
> the tape.

I tried compression option, but It doesn't work well.

I tried ...

No.1
# mt datcompression 1
... write
# mt datcompression 1
... read

No.2
# mt datcompression 0
... write
# mt datcompression 1
... read

No.3
# mt datcompression 1
... write
# mt datcompression 0
... read

No.4
# mt datcompression 0
... write
# mt datcompression 0
... read

, but can't

'datcompression' isn't correct option ?


> You can use `cat` and `od` to read/write from a tape before you
> waste a lot file time with `tar`. You can even do:
> 
>                 ls >/dev/tape
>                  .... takes a lot of time..
> 
>                 cat /dev/tape  # Read back.
> 
> Blocking/deblocking is done in the driver so you can treat it as
> a "slow-to-start" FIFO.

I tried, and got error message...

-----------------------------------
# ls >/dev/tape
st0: Write not multiple of tape block size.   <----- ???
ls: write error: Input/output error
#
-----------------------------------
# cat /dev/tape
[inclemental-] Tue Apr 24 03: ......          <----- looks like good!
#
-----------------------------------

Something wrong?



Thanks, for your help.

> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/

-- 
Masaki Tsuji

  reply	other threads:[~2001-04-24 22:17 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-04-24 16:06 Masaki Tsuji
2001-04-24 16:51 ` Richard B. Johnson
2001-04-24 22:15   ` Masaki Tsuji [this message]
2001-04-25  1:07 ` Tim Moore
  -- strict thread matches above, loose matches on Subject: below --
2001-04-24 10:54 hundreds of mount --bind mountpoints? Alexander Viro
2001-04-24 16:04 ` Can't read SCSI TAPE Masaki Tsuji

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=3AE5FB1B.BFF09D8@ma.nma.ne.jp \
    --to=jammasa@ma.nma.ne.jp \
    --cc=linux-kernel@vger.kernel.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

all inboxes | Powered by JetHome®