From owner-freebsd-current@FreeBSD.ORG Tue Nov 25 16:05:22 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4327C16A4CE for ; Tue, 25 Nov 2003 16:05:22 -0800 (PST) Received: from moutng.kundenserver.de (moutng.kundenserver.de [212.227.126.171]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3F96543FBF for ; Tue, 25 Nov 2003 16:05:21 -0800 (PST) (envelope-from max@love2party.net) Received: from [212.227.126.206] (helo=mrelayng.kundenserver.de) by moutng.kundenserver.de with esmtp (Exim 3.35 #1) id 1AOnBG-0004A8-00; Wed, 26 Nov 2003 01:05:18 +0100 Received: from [217.83.15.56] (helo=max2400) by mrelayng.kundenserver.de with asmtp (Exim 3.35 #1) id 1AOnBG-0002dU-00; Wed, 26 Nov 2003 01:05:18 +0100 Date: Wed, 26 Nov 2003 01:05:14 +0100 From: Max Laier X-Mailer: The Bat! (v2.00) UNREG / CD5BF9353B3B7091 Organization: n/a X-Priority: 3 (Normal) Message-ID: <9137677687.20031126010514@love2party.net> To: Eric Anderson In-Reply-To: <3FC387EC.5020804@centtech.com> References: <360351187.1069749585@[192.168.1.20]> <3FC387EC.5020804@centtech.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Provags-ID: kundenserver.de abuse@kundenserver.de auth:4b2e7ab3d2b0288c188cf4bdedd09034 cc: freebsd-current@freebsd.org Subject: Re[2]: requesting vinum help X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: Max Laier List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 26 Nov 2003 00:05:22 -0000 >> Could a vinum guru please contact me via email? >> >> I've lost 2 vinum volumes as a result of the latest fiasco and naturally >> am eager to figure out what's going on and recover the data. EA> This isn't necessarily directed at you - I'm just using this email as a EA> footstep to send this general comment - EA> I am kind of under the assumption that -current is more of a test bed, EA> and anything can happen at any time, which is why it's bad to run EA> -current on a machine you care deeply about (at least its data). I EA> think I've seen at least 5 mails in the past few weeks about people EA> getting jammed into a corner with (what sounds like) production type EA> boxes, or at least important boxes (or they wouldn't need a vinum?) There is the point! If no-one would ever take the risk of running -current on a bigger, more important box no-one would have the capabilities to test vinum and other large scale stuff in realistic environments. No my suggestion is to help those (brave) guys rather than screaming: "Fool, don't you know it's -current!?" The not so good point about the original request is that he is looking for private assistance, while the problem and - even more - the solution of it might be very interesting to all of us (more than much of the other ongoing threads, for sure). EA> .. It seems odd to me that they wouldn't give it a whirl first EA> before attempting to use it on a box they seem so protective of. EA> Anyway, I'm just stating that running -current is for testing and EA> developing, not really for production - at least I'm fairly certain. There's the magic keyword again: testing! Who should do it if not guys like him? If vinum had crossed my way before, I'd try to help - sorry. -- Best regards, Max mailto:max@love2party.net