From: "Glover George" <dime@gulfsales.com>
To: <linux-kernel@vger.kernel.org>
Subject: st0: Block limits 1 - 16777215 bytes.
Date: Tue, 19 Feb 2002 11:57:07 -0600 [thread overview]
Message-ID: <000201c1b96e$d8921d00$0300a8c0@yellow> (raw)
I've been experiencing mysterious lockups since upgrading to kernel
2.4.17. Looking in the /var/log/messages I hadn't seen anything
suspicious until now. I guess the machine hasn't had time to write this
to disk except every now and then. The message
Feb 19 11:29:55 butler kernel: st0: Block limits 1 - 16777215 bytes.
I notice this after rebooting after the crash. So I tried manually
doing a tar to the tape drive and was able to successfully lock the
machine up. Can someone help me understand this and if it is simply a
limit problem, why would the machine lock up?
Thank you.
Glover George
Systems/Networks Admin
Gulf Sales & Supply, Inc.
(228) 762-0268
dime@gulfsales.com
http://www.gulfsales.com
next reply other threads:[~2002-02-19 17:57 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-19 17:57 Glover George [this message]
2002-02-20 1:15 ` st0: Block limits 1 - 16777215 bytes Mr. James W. Laferriere
2002-02-20 14:56 ` Glover George
2002-02-20 15:21 ` Richard B. Johnson
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='000201c1b96e$d8921d00$0300a8c0@yellow' \
--to=dime@gulfsales.com \
--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