public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Will McDonald <will@cs.wisc.edu>
To: linux-kernel@vger.kernel.org
Subject: Re: 2.6.4: Mount of /dev/hdb1 impssible
Date: Tue, 24 Aug 2004 11:21:47 -0500	[thread overview]
Message-ID: <20040824162147.GG24167@cs.wisc.edu> (raw)

For the benefit of those searching list archives:

I had this problem while upgrading from 2.6.2 to 2.6.6 (and 2.6.7/2.6.8), so
the problems seems to have arrision in either 2.6.3 or 2.6.4.

The solution (at least for a few people who have experienced this) is to
remove the evms package. Look for the existence of (on my system) /dev/evms/.

Not strictly necessary, but can anyone in the know explain why this broke?

-will

On Thu, 11 Mar 2004 21:29:53 +0200, Markus Hstbacka wrote:
> Hi list,
> I upgraded from 2.6.4-rc2 to 2.6.4 today, a few minutes before reboot I
> noticed that my /dev/hdb1 hadn't been mounted on last reboot, so I tried
> to mount it by hand:
> # mount /work
> mount: /dev/hdb1 already mounted or /work/ busy
> 
> Then I thought it'll be fixed when I boot up my 2.6.4, it wasn't, I
> tried to mount it to various locations (/mnt/ /mnt/work etc..) and it
> didn't want to mount, I'm totally out of ideas with this. according to
> df it's not mounted, according to mount it's not mounted and according
> to mtab it's not mounted, so what's going on?
> 
> It mounts fine on my 2.6.1-mm4 kernel that I use for SCSI burning and
> fallback if something fails.


             reply	other threads:[~2004-08-24 16:21 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-24 16:21 Will McDonald [this message]
  -- strict thread matches above, loose matches on Subject: below --
2004-03-11 19:29 2.6.4: Mount of /dev/hdb1 impssible Markus Hästbacka

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=20040824162147.GG24167@cs.wisc.edu \
    --to=will@cs.wisc.edu \
    --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