From owner-freebsd-current Sun Sep 5 13:45:58 1999 Delivered-To: freebsd-current@freebsd.org Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.40.131]) by hub.freebsd.org (Postfix) with ESMTP id 2F43B14CC8 for ; Sun, 5 Sep 1999 13:45:51 -0700 (PDT) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.9.3/8.9.2) with ESMTP id WAA21476; Sun, 5 Sep 1999 22:44:54 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) To: jtaillan@cybercable.fr Cc: current@FreeBSD.ORG Subject: Re: umount problem In-reply-to: Your message of "Sun, 05 Sep 1999 22:37:52 +0200." <19990905223752.A354@fugue.noisy.ratp> Date: Sun, 05 Sep 1999 22:44:54 +0200 Message-ID: <21474.936564294@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <19990905223752.A354@fugue.noisy.ratp>, Janick Taillandier writes: >With a very recent kernel (less than a day), when I halt my >Dell laptop, I get the following message: > syncing disks... 4 done > umount of /users failed (19) > umount of /usr failed (19) > umount of / failed (19) I fixed this a few hours ago. It's harmless. -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." FreeBSD -- It will take a long time before progress goes too far! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message