From owner-freebsd-stable@FreeBSD.ORG Thu Jul 7 09:50:07 2005 Return-Path: X-Original-To: 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 A362116A41C for ; Thu, 7 Jul 2005 09:50:07 +0000 (GMT) (envelope-from Philippe.Pegon@crc.u-strasbg.fr) Received: from mailhost.u-strasbg.fr (mailhost.u-strasbg.fr [130.79.200.158]) by mx1.FreeBSD.org (Postfix) with ESMTP id 31F7B43D58 for ; Thu, 7 Jul 2005 09:50:06 +0000 (GMT) (envelope-from Philippe.Pegon@crc.u-strasbg.fr) Received: from sokaris.u-strasbg.fr (sokaris.u-strasbg.fr [IPv6:2001:660:2402::101]) by mailhost.u-strasbg.fr (8.13.3/jtpda-5.5pre1) with ESMTP id j679o5kK063672 ; Thu, 7 Jul 2005 11:50:05 +0200 (CEST) Received: from [192.168.0.100] (crc.u-strasbg.fr [IPv6:2001:660:2402:1001::1]) by sokaris.u-strasbg.fr (8.12.9/jtpda-5.5pre1) with ESMTP id j679o3tt087615 ; Thu, 7 Jul 2005 11:50:04 +0200 (CEST) Message-ID: <42CCFC56.3090809@crc.u-strasbg.fr> Date: Thu, 07 Jul 2005 11:56:38 +0200 From: Philippe PEGON User-Agent: Mozilla Thunderbird 1.0.2 (X11/20050602) X-Accept-Language: fr, en MIME-Version: 1.0 To: Claus Guttesen References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 8bit X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-1.6 (mailhost.u-strasbg.fr [IPv6:2001:660:2402::158]); Thu, 07 Jul 2005 11:50:05 +0200 (CEST) X-Virus-Scanned: ClamAV 0.86.1/970/Wed Jul 6 18:00:45 2005 on mr8.u-strasbg.fr X-Virus-Status: Clean X-Antivirus: scanned by sophos at u-strasbg.fr Cc: freebsd-stable@freebsd.org Subject: Re: FreeBSD as nfs-server X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 07 Jul 2005 09:50:07 -0000 Claus Guttesen a écrit : > Hi. Hi, > > Last week I phased out my remaining trusty FreeBSD nfs-server. The > first was phased out three weeks ago. They have served me well for > about two year and I have been *very* satisfied with the performance > and stability. The below mentioned reasons made the decision easier to > migrate to veritas volume manager on solaris. > > 1. Lack of a journaling filesystem. > 2. Lack of a logical volume manager. > > My intent is *not* to start a flamewar, simpy stating why I had to migrate. > > Additional comments to item #1: > We have background-fsck, what's wrong with that? > > Well, there is nothing wrong with that in a way. Background-fsck does > work, but my nfs-server have had three unplanned reboots during that > time, none of them was caused by the nfs-server itself, but caused by > other factors. The server comes back up as it should and detects that > the volumes wasn't unmounted in an orderly fashion and defers the > volume to background-fsck. So far so good. > > When the background-fsck is done with one volume and it jumps to the > next, my webservers connected to the nfs-server are unable to read and > write to the nfs-volumes for a period of 15-30 minutes. The smallest > (of several) volume is 400 GB and the largest (of several) is 2 TB. > The outcome is that my website is seen as being inaccessible. This was > with FreeBSD 5.2 beta through 5.4 I saw this behaviour. we switched our mail server to Linux for your first reason : see http://lists.freebsd.org/mailman/htdig/freebsd-stable/2005-June/thread.html#15751 > > So I'm delighted to read that the initial work on a journaling > filesystem has started. > > Additional comments to item #2: > Use vinum! > > Is it vinum or gvinum which is the future of FreeBSD? > > The docs related to vinum refers to some parameters in newfs not > present in the manual-pages. > > As more volumes are added the task of configuring (g)vinum will become > more and more timeconsuming and errorprone. Does it recover correctly > in the event of a crash, how about fsck/newfs on volumes larger than 2 > TB? > > > The camcontrol program on FreeBSD is a very robust tool. This is one > program I miss. Some parameters to the find- and date-commands on > FreeBSD aren't there on solaris, so I'll keep the old nfs-server > around for doing day2day maintenance. > > I'm keeping FreeBSD as webservers (of course). > > regards > Claus -- Philippe PEGON