From owner-freebsd-bugs@FreeBSD.ORG Wed Oct 26 08:20:13 2005 Return-Path: X-Original-To: freebsd-bugs@hub.freebsd.org Delivered-To: freebsd-bugs@hub.freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C788716A41F for ; Wed, 26 Oct 2005 08:20:13 +0000 (GMT) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6425F43D49 for ; Wed, 26 Oct 2005 08:20:13 +0000 (GMT) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.3/8.13.3) with ESMTP id j9Q8KDE6067766 for ; Wed, 26 Oct 2005 08:20:13 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.13.3/8.13.1/Submit) id j9Q8KD3w067765; Wed, 26 Oct 2005 08:20:13 GMT (envelope-from gnats) Date: Wed, 26 Oct 2005 08:20:13 GMT Message-Id: <200510260820.j9Q8KD3w067765@freefall.freebsd.org> To: freebsd-bugs@FreeBSD.org From: "Poul-Henning Kamp" Cc: Subject: Re: kern/87255: Large malloc-backed mfs crashes the system X-BeenThere: freebsd-bugs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Poul-Henning Kamp List-Id: Bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 26 Oct 2005 08:20:13 -0000 The following reply was made to PR kern/87255; it has been noted by GNATS. From: "Poul-Henning Kamp" To: Yar Tikhiy Cc: freebsd-bugs@freebsd.org Subject: Re: kern/87255: Large malloc-backed mfs crashes the system Date: Tue, 11 Oct 2005 16:55:09 +0200 In message <200510111450.j9BEoLEB006718@freefall.freebsd.org>, Yar Tikhiy write s: >The following reply was made to PR kern/87255; it has been noted by GNATS. > >From: Yar Tikhiy >To: FreeBSD-gnats-submit@FreeBSD.org >Cc: >Subject: Re: kern/87255: Large malloc-backed mfs crashes the system >Date: Tue, 11 Oct 2005 18:44:36 +0400 > > Just for the record: > > The problem seems to involve vfs-md interaction > as filling just a bogusly large malloc-backed md > device results in harmless ENOSPC at some point. ENOSPC may be a problem for filesystems, try changing it to EIO and see if they cope better with that. In all cases it is a "don't do that then" class of problem. -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence.