From owner-freebsd-arm@FreeBSD.ORG Tue Jul 1 11:33:41 2014 Return-Path: Delivered-To: freebsd-arm@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 84C9ABCE; Tue, 1 Jul 2014 11:33:41 +0000 (UTC) Received: from smarthost1.greenhost.nl (smarthost1.greenhost.nl [195.190.28.81]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 45DCC24AD; Tue, 1 Jul 2014 11:33:40 +0000 (UTC) Received: from smtp.greenhost.nl ([213.108.104.138]) by smarthost1.greenhost.nl with esmtps (TLS1.0:RSA_AES_256_CBC_SHA1:32) (Exim 4.72) (envelope-from ) id 1X1wJd-0002mU-19; Tue, 01 Jul 2014 13:33:37 +0200 Content-Type: text/plain; charset=iso-8859-15; format=flowed; delsp=yes To: mexas@bris.ac.uk, rene@freebsd.org Subject: Re: /tmp, /var/log, /var/tmp as /dev/md - why? References: <201407011046.s61AkJpj006890@mech-cluster241.men.bris.ac.uk> Date: Tue, 01 Jul 2014 13:33:35 +0200 MIME-Version: 1.0 Content-Transfer-Encoding: 7bit From: "Ronald Klop" Message-ID: In-Reply-To: <201407011046.s61AkJpj006890@mech-cluster241.men.bris.ac.uk> User-Agent: Opera Mail/12.17 (Win32) X-Authenticated-As-Hash: 398f5522cb258ce43cb679602f8cfe8b62a256d1 X-Virus-Scanned: by clamav at smarthost1.samage.net X-Spam-Level: - X-Spam-Score: -1.0 X-Spam-Status: No, score=-1.0 required=5.0 tests=ALL_TRUSTED, BAYES_20 autolearn=disabled version=3.3.1 X-Scan-Signature: 788438cbfdc4dc137ce560360a3a99c7 Cc: freebsd-arm@freebsd.org X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 01 Jul 2014 11:33:41 -0000 On Tue, 01 Jul 2014 12:46:19 +0200, Anton Shterenlikht wrote: >> From r.c.ladan@gmail.com Tue Jul 1 11:37:35 2014 >> >> 2014-07-01 11:25 GMT+02:00 Anton Shterenlikht : >> >>> Why is it a good idea to mount /tmp and some var dirs on memory disks: >>> >>> root@raspberry-pi:/usr/ports # df -m >>> Filesystem 1M-blocks Used Avail Capacity Mounted on >>> /dev/mmcsd0s2a 14694 777 12742 6% / >>> devfs 0 0 0 100% /dev >>> /dev/mmcsd0s1 16 3 13 20% /boot/msdos >>> /dev/md0 28 4 22 16% /tmp >>> /dev/md1 14 0 12 0% /var/log >>> /dev/md2 4 0 4 0% /var/tmp >>> root@raspberry-pi:/usr/ports # >>> >>> Is this about speed or power, or maybe space? >>> >>> Mostly write tear because you're using an SD card, and it improves >>> speed >> too. > > "write tear"? > Is this a joke, or some technical term? > I cannot find what it means. If you search for "write tear ssd" you get a lot of hits. It means that a lot of people like to reduce the number of writes to flash disks. > I get these messages on the console (well, on hdmi port...): > > pid ... (svnlite), uid 0 inumber 13 on /tmp: filesystem full > > If I unmount /tmp from md and leave it on sd card, > then I don't see these anymore. What does this mean? That the default setup is not suitable for your use case, because you write more to /tmp than the person who made the installation. And that you can change the /tmp mount as you like. Regards, Ronald.