mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Matthew Harrell <lists-sender-14a37a@bittwiddlers.com>
To: Kernel List <linux-kernel@vger.kernel.org>
Subject: Re: 2.5.65 jaz drive devfs oops
Date: Fri, 21 Mar 2003 07:14:17 -0500	[thread overview]
Message-ID: <20030321121417.GA31412@bittwiddlers.com> (raw)
In-Reply-To: <20030321090510.A28886@infradead.org>

: > And, even with "devfs=nomount" on the boot line and no devfs used I still
: > get the same error once the jaz drive totally cycles down.  
: 
: Is the OOPS with devfs=nomount exactly the same?  If no or you're
: unsure please post it, too.

Yep, it's always mounted the same but the other thing I just remembered is 
that it's set up to use the automounter every time I go into /mnt/jaz.  So,
if I permenantly mount the jaz drive somewhere and just have /mnt/jaz be 
a intra-system link then it does work.  I guess this means it's a problem
with the jaz drive spinning down and "detaching" itself from the scsi bus?

I decided I would try it that way for the moment since I could then keep 
devfs on the system.  No oops but I'm sure if I unmounted it for about an
hour and then tried to mount it again it would oops

-- 
  Matthew Harrell                          Every morning is the dawn of a
  Bit Twiddlers, Inc.                       new error.
  mharrell@bittwiddlers.com     

  reply	other threads:[~2003-03-21 12:03 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-03-19 19:14 Matthew Harrell
2003-03-19 19:34 ` Christoph Hellwig
2003-03-19 21:45   ` Matthew Harrell
2003-03-19 23:57     ` Matthew Harrell
2003-03-21  2:53       ` Matthew Harrell
2003-03-21  9:05         ` Christoph Hellwig
2003-03-21 12:14           ` Matthew Harrell [this message]
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=20030321121417.GA31412@bittwiddlers.com \
    --to=lists-sender-14a37a@bittwiddlers.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mharrell-dated-1048680858.8a93b4@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

all inboxes | Powered by JetHome®