From owner-freebsd-current@FreeBSD.ORG Sun Jan 8 07:09:17 2006 Return-Path: X-Original-To: current@freebsd.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E98C716A41F for ; Sun, 8 Jan 2006 07:09:17 +0000 (GMT) (envelope-from fullermd@over-yonder.net) Received: from mail.localelinks.com (web.localelinks.com [64.39.75.54]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7C5B343D45 for ; Sun, 8 Jan 2006 07:09:16 +0000 (GMT) (envelope-from fullermd@over-yonder.net) Received: from draco.over-yonder.net (adsl-072-148-013-213.sip.jan.bellsouth.net [72.148.13.213]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.localelinks.com (Postfix) with ESMTP id 22826AD for ; Sun, 8 Jan 2006 01:09:16 -0600 (CST) Received: by draco.over-yonder.net (Postfix, from userid 100) id 5509B61C21; Sun, 8 Jan 2006 01:09:15 -0600 (CST) Date: Sun, 8 Jan 2006 01:09:15 -0600 From: "Matthew D. Fuller" To: current@freebsd.org Message-ID: <20060108070915.GA98507@over-yonder.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline X-Editor: vi X-OS: FreeBSD User-Agent: Mutt/1.5.11-fullermd.2 Cc: Subject: nmount() issues X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 08 Jan 2006 07:09:18 -0000 I just updated from an October 1 -CURRENT, and I'm having some issues from nmount(). SOME (but not all, and with no pattern I can see) of my filesystems react poorly to `mount -u`. I keep getting: % mount -u /usr/ports mount: /dev/da0s1e: Bad address All my filesystems have been through a good fsck'ing. I can even newfs ports, and it'll still have that issue. /depot fails too. /depot2 goes through without a hitch. So do / and /usr. A ktrace is pretty uninformative; it just shows the EFAULT return from nmount(). Some of the filesystems are UFS1, some UFS2, and the split isn't along those lines. Anybody else seen anything like this? -- Matthew Fuller (MF4839) | fullermd@over-yonder.net Systems/Network Administrator | http://www.over-yonder.net/~fullermd/ On the Internet, nobody can hear you scream.