From owner-freebsd-bugs  Tue Jun  2 20:48:41 1998
Return-Path: <owner-freebsd-bugs@FreeBSD.ORG>
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id UAA13408
          for freebsd-bugs-outgoing; Tue, 2 Jun 1998 20:48:41 -0700 (PDT)
          (envelope-from owner-freebsd-bugs@FreeBSD.ORG)
Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.15.68.22])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA13388;
          Tue, 2 Jun 1998 20:48:23 -0700 (PDT)
          (envelope-from bde@godzilla.zeta.org.au)
Received: (from bde@localhost)
	by godzilla.zeta.org.au (8.8.7/8.8.7) id NAA23512;
	Wed, 3 Jun 1998 13:48:21 +1000
Date: Wed, 3 Jun 1998 13:48:21 +1000
From: Bruce Evans <bde@zeta.org.au>
Message-Id: <199806030348.NAA23512@godzilla.zeta.org.au>
To: bde@zeta.org.au, freebsd-bugs@FreeBSD.ORG, grog@lemis.com, phk@FreeBSD.ORG
Subject: Re: bin/6794
Sender: owner-freebsd-bugs@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org

>>> The WARNING line is printed by the kernel.  A normal mount(8) would try
>>> 31 slices here and the kernel would print 31 identical WARNING lines.
>>
>>Why that?  It knows the slice it's trying to mount: it's /dev/sd0s1e,
>>which fsck has just cleaned.  Under what circumstances would mount(8)
>>try to mount every possible slice on the disk?
>
>Whenever the mount point is "/", mount(8) is an unhacked -current or
>-stable mount(8), and there are no mountable slices (with the given unit
>and partition) on the disk.

Oops.  It only tries multiple slices if the device name is for a
partition on the compatibility slice.

This means that the problem is probably entirely in fsck.

Bruce

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-bugs" in the body of the message