From owner-freebsd-stable@FreeBSD.ORG  Tue May 18 00:23:09 2004
Return-Path: <owner-freebsd-stable@FreeBSD.ORG>
Delivered-To: freebsd-stable@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id A5AAE16A4CE
	for <freebsd-stable@freebsd.org>;
	Tue, 18 May 2004 00:23:09 -0700 (PDT)
Received: from smtp.atlantis.dp.ua (smtp.atlantis.dp.ua [193.108.46.231])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 051F243D48
	for <freebsd-stable@freebsd.org>;
	Tue, 18 May 2004 00:23:07 -0700 (PDT)
	(envelope-from dmitry@atlantis.dp.ua)
Received: from smtp.atlantis.dp.ua (smtp.atlantis.dp.ua [193.108.46.231])
	by smtp.atlantis.dp.ua (8.12.6p2/8.12.6) with ESMTP id i4I7MtFx059600
	for <freebsd-stable@freebsd.org>;
	Tue, 18 May 2004 10:22:55 +0300 (EEST)
	(envelope-from dmitry@atlantis.dp.ua)
Date: Tue, 18 May 2004 10:22:55 +0300 (EEST)
From: Dmitry Pryanishnikov <dmitry@atlantis.dp.ua>
To: freebsd-stable@freebsd.org
Message-ID: <20040518095546.B40144@atlantis.atlantis.dp.ua>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Subject: Re: softupdates can cause crash...
X-BeenThere: freebsd-stable@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Production branch of FreeBSD source code
	<freebsd-stable.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
	<mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable>
List-Post: <mailto:freebsd-stable@freebsd.org>
List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
	<mailto:freebsd-stable-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 18 May 2004 07:23:09 -0000


Hello!

> Date:      Mon, 17 May 2004 16:19:43 -0700
> From:      John-Mark Gurney <gurney_j@efn.org>
>
> Softupdates on -stable currently has a bug when handling large files
> that will cause your machine to panic.  I have filed kern/66781 which
> describes this problem.  The best work around that I can recommend is
> to disable softupdates on any and all FS's.

 There is one line in your sample program which I can't understand. What's
the purpose (question for you) and actual action (question for fs gurus) of
the following line:

device=/dev/da1s1e
...
        fsync "$device" &

??? I thought fsync() call is for regular files, not for special ones, does it
still stand? When I remove this line or replace it with

	sync &

crash no more happens. So, can we call it "foot-shooting"? Of course, bug
should be fixed if possible, but it seems that only root can fsync device,
so the main question, can regular user activity create similar conditions
(again question for fs gurus)?

Sincerely, Dmitry
-- 
Atlantis ISP, System Administrator
e-mail:  dmitry@atlantis.dp.ua
nic-hdl: LYNX-RIPE