From owner-freebsd-stable Sun Jun 27 16:26: 7 1999 Delivered-To: freebsd-stable@freebsd.org Received: from pluto.ipass.net (pluto.ipass.net [198.79.53.5]) by hub.freebsd.org (Postfix) with ESMTP id 8B747151BC for ; Sun, 27 Jun 1999 16:26:04 -0700 (PDT) (envelope-from rhh@ipass.net) Received: from stealth.ipass.net. (ppp-1-79.dialup.rdu.ipass.net [209.170.132.79]) by pluto.ipass.net (8.9.3/8.9.3) with ESMTP id TAA27146 for ; Sun, 27 Jun 1999 19:25:56 -0400 (EDT) Received: (from rhh@localhost) by stealth.ipass.net. (8.9.3/8.8.8) id TAA01918 for stable@freebsd.org; Sun, 27 Jun 1999 19:27:40 -0400 (EDT) (envelope-from rhh) Date: Sun, 27 Jun 1999 19:27:40 -0400 From: Randall Hopper To: stable@freebsd.org Subject: 3.2-R mount lockup Message-ID: <19990627192740.A1837@ipass.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.1i Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG 3.2-RELEASE still locks the system hard when a file system is mismounted, just as 3.0-RELEASE did: # mount /dev/wd4s1 /mnt - fails with incorrect superblock (it's a FAT partition) # mount -t msdos /dev/wd4s1 /mnt - locks the system hard If you omit the first (incorrect) mount command, then it mounts successfully. Is this a known problem, or should I file a PR? Thanks, Randall To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message