From: Matthew Harrell <lists-sender-14a37a@bittwiddlers.com>
To: Christoph Hellwig <hch@infradead.org>,
Kernel List <linux-kernel@vger.kernel.org>
Subject: Re: 2.5.65 jaz drive devfs oops
Date: Wed, 19 Mar 2003 18:57:52 -0500 [thread overview]
Message-ID: <20030319235752.GA18086@bittwiddlers.com> (raw)
In-Reply-To: <20030319214522.GA7397@bittwiddlers.com>
Well, the second test just now didn't work right.
/dev/scsi/host0/bus0/target4/lun0/disc did exist this time around but I got
the same error as before trying to get anything going on it and I can no
longer get the jaz drive to work.
: So far it's looking good. I waited until the drive had totally spun down
: then tried going to it's automount directory and it spun up and mounted fine
:
: sdb: Spinning up disk...........ready
: SCSI device sdb: 2091050 512-byte hdwr sectors (1071 MB)
: sdb: Write Protect is off
: sdb: Mode Sense: 39 00 10 08
: SCSI device sdb: drive cache: write back
: SCSI device sdb: 2091050 512-byte hdwr sectors (1071 MB)
: sdb: Write Protect is off
: sdb: Mode Sense: 39 00 10 08
: SCSI device sdb: drive cache: write back
: /dev/scsi/host0/bus0/target4/lun0: p4
: found reiserfs format "3.6" with standard journal
: Reiserfs journal params: device sd(8,20), size 8192, journal first block 18, max trans len 1024, max batch 900, max commit age 30, max trans age 30
: reiserfs: checking transaction log (sd(8,20)) for (sd(8,20))
: Using r5 hash to sort names
:
: I'll try it again in an hour or so with some different tests. Thanks for the
: patch
--
Matthew Harrell If you can't convince them,
Bit Twiddlers, Inc. confuse them...
mharrell@bittwiddlers.com
next prev parent reply other threads:[~2003-03-19 23:52 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-19 19:14 2.5.65 jaz drive devfs oops Matthew Harrell
2003-03-19 19:34 ` Christoph Hellwig
2003-03-19 21:45 ` Matthew Harrell
2003-03-19 23:57 ` Matthew Harrell [this message]
2003-03-21 2:53 ` Matthew Harrell
2003-03-21 9:05 ` Christoph Hellwig
2003-03-21 12:14 ` Matthew Harrell
2003-03-21 14:38 ` Matthew Harrell
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=20030319235752.GA18086@bittwiddlers.com \
--to=lists-sender-14a37a@bittwiddlers.com \
--cc=hch@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mharrell-dated-1048550276.2a57f2@bittwiddlers.com \
/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