From owner-freebsd-fs@FreeBSD.ORG  Fri May 25 08:19:02 2007
Return-Path: <owner-freebsd-fs@FreeBSD.ORG>
X-Original-To: freebsd-fs@freebsd.org
Delivered-To: freebsd-fs@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52])
	by hub.freebsd.org (Postfix) with ESMTP id 49D2616A400
	for <freebsd-fs@freebsd.org>; Fri, 25 May 2007 08:19:02 +0000 (UTC)
	(envelope-from cristi@net.utcluj.ro)
Received: from bavaria.utcluj.ro (bavaria.utcluj.ro [193.226.5.35])
	by mx1.freebsd.org (Postfix) with ESMTP id 0356613C458
	for <freebsd-fs@freebsd.org>; Fri, 25 May 2007 08:19:01 +0000 (UTC)
	(envelope-from cristi@net.utcluj.ro)
Received: from localhost (localhost [127.0.0.1])
	by bavaria.utcluj.ro (Postfix) with ESMTP id 528B650856;
	Fri, 25 May 2007 11:19:00 +0300 (EEST)
X-Virus-Scanned: by the daemon playing with your mail on bavaria.utcluj.ro
Received: from bavaria.utcluj.ro ([127.0.0.1])
	by localhost (bavaria.utcluj.ro [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id QxKAhWDCXqvC; Fri, 25 May 2007 11:18:37 +0300 (EEST)
Received: from [172.20.100.73] (unknown [217.73.161.129])
	(using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))
	(No client certificate requested)
	by bavaria.utcluj.ro (Postfix) with ESMTP id 7D38750821;
	Fri, 25 May 2007 11:18:37 +0300 (EEST)
Message-ID: <46569BDF.3030700@net.utcluj.ro>
Date: Fri, 25 May 2007 11:18:39 +0300
From: Cristian KLEIN <cristi@net.utcluj.ro>
Organization: Data Communication Center - Technical University of Cluj-Napoca
User-Agent: Thunderbird 1.5.0.10 (X11/20070306)
MIME-Version: 1.0
To: Ollivier Robert <roberto@keltia.freenix.fr>
References: <475187.33232.qm@web63006.mail.re1.yahoo.com>	<86r6p9xf2c.fsf@dwp.des.no>
	<20070522131107.GA73155@keltia.freenix.fr>
In-Reply-To: <20070522131107.GA73155@keltia.freenix.fr>
X-Enigmail-Version: 0.94.0.0
Content-Type: text/plain; charset=ISO-8859-15
Content-Transfer-Encoding: 8bit
Cc: freebsd-fs@freebsd.org
Subject: Re: VERY frustrated with FreeBSD/UFS stability - please help
	or	comment...
X-BeenThere: freebsd-fs@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Filesystems <freebsd-fs.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-fs>,
	<mailto:freebsd-fs-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-fs>
List-Post: <mailto:freebsd-fs@freebsd.org>
List-Help: <mailto:freebsd-fs-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-fs>,
	<mailto:freebsd-fs-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Fri, 25 May 2007 08:19:02 -0000

Ollivier Robert wrote:
> According to Dag-Erling Smørgrav:
>> client2% rsync --archive --delete /vol server:/backup/client2
>> server% for vol in /backup/* ; do mksnap_ffs $vol $vol/.snap/`date` ; done
> 
> My experience with the sysutils/freebsd-snapshot, which enable automatic
> snapshot creation (à la NetApp) is that after a few created snapshots, the
> whole system just locks up.  This was in 6.0-6.1 days, maybe 6.2 has
> improved but they seem very fragile :(

Nope. They did not. :)

I had a server which crashed a few hours after enabling snapshots. Now
that I removed them, the system is rock solid again.

I have been unable to reproduce the problem (interesting how some
problems show up only on production systems), so I was unable to file a PR.

IMHO, all these issues should be written in the errata. I can affort not
using snapshot, but having an instable system (and an angry boss) is
killing me.