From owner-freebsd-current  Thu Nov 16 12:19:46 1995
Return-Path: owner-current
Received: (from root@localhost)
          by freefall.freebsd.org (8.6.12/8.6.6) id MAA11028
          for current-outgoing; Thu, 16 Nov 1995 12:19:46 -0800
Received: from pilhuhn.de (pilhuhn.de [193.141.89.1])
          by freefall.freebsd.org (8.6.12/8.6.6) with SMTP id MAA11022
          for <current@freebsd.org>; Thu, 16 Nov 1995 12:19:39 -0800
Received: by pilhuhn.de id <m0tGAla-0005KXC> ; Thu, 16 Nov 95 21:18 MET
Message-Id: <m0tGAla-0005KXC@pilhuhn.de>
From: hwr@pilhuhn.de (Heiko W.Rupp)
Subject: Re: 2.1-stable bombs at umount
To: terry@lambert.org (Terry Lambert)
Date: Thu, 16 Nov 1995 21:18:38 +0100 (MET)
Cc: hwr@pilhuhn.de, joerg_wunsch@uriah.heep.sax.de, current@freebsd.org
In-Reply-To: <199511161951.MAA03640@phaeton.artisoft.com> from "Terry Lambert" at Nov 16, 95 12:51:27 pm
X-Mailer: ELM [version 2.4 PL20]
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit
Content-Length: 683       
Sender: owner-current@freebsd.org
Precedence: bulk

Terry Lambert:
| Let me guess: You are running with quotas on this file system.

No. This is a news spool filesystem - I did not set up any quota at
all.

| If you aren't running with quotas, reverting the unmount code to forward
| traverse the mountlist, focing each unmount, will fix the problem, or
| at least put the behaviour back the way it was before the problem became
| obvious.

Will look into this, but at the moment I don't have enough spare time
(and want a _stable_ system ..)

-- 
Heiko W.Rupp        Gerwigstr.5        D-76131  Karlsruhe    +49 721 9661524
... den 80 Mark Fuerst auf den Schaedel und dann in die Eier hau'n, dann 
fuehlt der Typ sich wie ein Maedel.