From owner-freebsd-hackers Mon Jun 18 21:48:32 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from relay.butya.kz (butya-gw.butya.kz [212.154.129.94]) by hub.freebsd.org (Postfix) with ESMTP id 0B21737B406 for ; Mon, 18 Jun 2001 21:48:27 -0700 (PDT) (envelope-from bp@butya.kz) Received: by relay.butya.kz (Postfix, from userid 1000) id 2506A28C46; Tue, 19 Jun 2001 11:48:23 +0700 (ALMST) Received: from localhost (localhost [127.0.0.1]) by relay.butya.kz (Postfix) with ESMTP id 155CB28BC1; Tue, 19 Jun 2001 11:48:23 +0700 (ALMST) Date: Tue, 19 Jun 2001 11:48:22 +0700 (ALMST) From: Boris Popov To: Attila Nagy Cc: freebsd-hackers@freebsd.org Subject: Re: Data corruption in 4.3-STABLE (a long standing bug) In-Reply-To: <20010617235733.V17072-100000@scribble.fsn.hu> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Mon, 18 Jun 2001, Attila Nagy wrote: > I have a mid-loaded server which runs each daemon in jail()-ed > environments. The data space is union-mounted, because nullfs paniced the > kernel when someting did a chroot on it (this was the case with > 4.2-STABLE). > > On friday I upgraded from 4.3-RC to the latest 4.3-STABLE and noticed that > nullfs actually works, but I get a lot of errors, similar to these: Not all of nullfs fixes MFCed to -stable. Please wait a little bit more. -- Boris Popov http://www.butya.kz/~bp/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message