From owner-freebsd-hackers@freebsd.org  Tue Aug  9 09:17:34 2016
Return-Path: <owner-freebsd-hackers@freebsd.org>
Delivered-To: freebsd-hackers@mailman.ysv.freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org
 [IPv6:2001:1900:2254:206a::19:1])
 by mailman.ysv.freebsd.org (Postfix) with ESMTP id AEB18BB2F03
 for <freebsd-hackers@mailman.ysv.freebsd.org>;
 Tue,  9 Aug 2016 09:17:34 +0000 (UTC) (envelope-from ap00@mail.ru)
Received: from fallback2.mail.ru (fallback2.mail.ru [94.100.179.22])
 by mx1.freebsd.org (Postfix) with ESMTP id 286991390
 for <freebsd-hackers@freebsd.org>; Tue,  9 Aug 2016 09:17:33 +0000 (UTC)
 (envelope-from ap00@mail.ru)
Received: from smtp44.i.mail.ru (smtp44.i.mail.ru [94.100.177.104])
 by fallback2.mail.ru (mPOP.Fallback_MX) with ESMTP id B6DCE75380E6
 for <freebsd-hackers@freebsd.org>; Tue,  9 Aug 2016 11:33:00 +0300 (MSK)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=mail.ru;
 s=mail2; 
 h=Content-Transfer-Encoding:Content-Type:MIME-Version:Subject:To:Message-ID:From:Date;
 bh=7xfcA48I8Q46SsBrPnkWl4IQpRARN3qflFgvuyL/JD4=; 
 b=LkyCJROgNZRsxXOcOVty1Rl9mgFzKpieM5kQI+XDXNG6hJKNIhE/W68IXYoSSs9Xse8MDzEgJz/esl/q6ilSFLgW4yOFp8GFzy+uHAeXiyhIcBnMBVtkmVD+aQNO2mKGhbAjHHefB5etVQN10MU/XqiIo3WN8h//4XwvTTjcJQA=;
Received: from [91.190.121.202] (port=53542 helo=pstation)
 by smtp44.i.mail.ru with esmtpa (envelope-from <ap00@mail.ru>)
 id 1bX2Sx-0004bk-Av
 for freebsd-hackers@freebsd.org; Tue, 09 Aug 2016 11:32:51 +0300
Date: Tue, 9 Aug 2016 11:32:48 +0300
From: Anthony Pankov <ap00@mail.ru>
X-Priority: 3 (Normal)
Message-ID: <747363738.20160809113248@mail.ru>
To: FreeBSD Hackers <freebsd-hackers@freebsd.org>
Subject: Root fs overflow. Updater tools must warn?
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Mailru-Sender: 0489DF6C38DA5EE561E8A477868835DBB961184D07F9964DFAB6D19B86A1E6D652F8A52D7429ABF2ACCB5262BB601CA2
X-Mras: OK
X-BeenThere: freebsd-hackers@freebsd.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Technical Discussions relating to FreeBSD
 <freebsd-hackers.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-hackers>, 
 <mailto:freebsd-hackers-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-hackers/>
List-Post: <mailto:freebsd-hackers@freebsd.org>
List-Help: <mailto:freebsd-hackers-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-hackers>, 
 <mailto:freebsd-hackers-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 09 Aug 2016 09:17:34 -0000

Greetings.

Recently I've got a very bad experience with root filesystem (ufs) overflow.

I  was preparing to install some port and wanted to upgrade ports tree
(ports was on root fs).

I estimated free space that was 1Gb+.
Than I ran
portsnap fetch
portsnap extract

After some time server stoped responding.

On server reboot I see the fatal Error:
 "can't write, filesystem is full"
than kernel messages
 "can't allocate .. soft_.. dep ...
  system going to reboot"

  Rebooting in single user mode show the following:
-  fsck makes the Error;
-  make clean in ports  makes the Error;
-  removing snaphot makes the Error;
-  removing large file makes the Error;

The same was when booting from live cd.

It was very sad.

Of  course  I  think  this is my fault. But tools such as portsnap and
freebsd-update  always  running as root.  System can't preserve
fs  space as in case of unprivileged user. May be, tools that run from
root  and  do  the  fs  space consuming things must estimate available
space and stop in bad case?


-- 
Best regards,
 Anthony Pankov                          mailto:ap00@mail.ru