From owner-freebsd-questions@FreeBSD.ORG Wed Jun 3 21:20:13 2009 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 7D691106564A for ; Wed, 3 Jun 2009 21:20:13 +0000 (UTC) (envelope-from wojtek@wojtek.tensor.gdynia.pl) Received: from wojtek.tensor.gdynia.pl (wojtek.tensor.gdynia.pl [IPv6:2001:4070:101:2::1]) by mx1.freebsd.org (Postfix) with ESMTP id C089E8FC24 for ; Wed, 3 Jun 2009 21:20:11 +0000 (UTC) (envelope-from wojtek@wojtek.tensor.gdynia.pl) Received: from wojtek.tensor.gdynia.pl (localhost [IPv6:::1]) by wojtek.tensor.gdynia.pl (8.14.3/8.14.3) with ESMTP id n53LK6ld027910; Wed, 3 Jun 2009 23:20:06 +0200 (CEST) (envelope-from wojtek@wojtek.tensor.gdynia.pl) Received: from localhost (wojtek@localhost) by wojtek.tensor.gdynia.pl (8.14.3/8.14.3/Submit) with ESMTP id n53LK6xn027907; Wed, 3 Jun 2009 23:20:06 +0200 (CEST) (envelope-from wojtek@wojtek.tensor.gdynia.pl) Date: Wed, 3 Jun 2009 23:20:06 +0200 (CEST) From: Wojciech Puchar To: Reid Linnemann In-Reply-To: <4A26E7CA.6020306@cs.okstate.edu> Message-ID: References: <4A26DBAD.6000005@cs.okstate.edu> <4A26E7CA.6020306@cs.okstate.edu> User-Agent: Alpine 2.00 (BSF 1167 2008-08-23) MIME-Version: 1.0 Content-Type: MULTIPART/MIXED; BOUNDARY="1626729238-11495294-1244064006=:27885" Cc: freebsd-questions Subject: Re: An adage for gmirror users X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 03 Jun 2009 21:20:13 -0000 This message is in MIME format. The first part should be readable text, while the remaining parts are likely unreadable without MIME-aware tools. --1626729238-11495294-1244064006=:27885 Content-Type: TEXT/PLAIN; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 8BIT >> >> or bad cables. >> > > I'll have to try different cables sometime, you may very well be correct. i had such problems many times. it always was cables or disk drive. Disk drive - check with smartmontools from ports. >> i simply have in crontab a script running once per hour: >> >> #!/bin/sh >> /sbin/gmirror status|grep -q DEGRADED && \\ >> mail -s "gmirror failure" myphonenumber@mygsmoperator.pl > Surely you jest! You presume that I have access to cheap, unrestrictive > communications technology ;) In the US, ISPs prevent clients routing > their own mail and text messages are outrageously expensive with our > cell carriers! Seriously though, that's a good idea. Maybe I could have so just send it to your mail! Actually - only one operator in Poland still work this way, and doesn't officially say it's supported. And it's the only reason i still use it, as others are bit cheaper. > Touché! I set up my mirror after my last disk started dying and I How about regular backups? mirroring is only protection agains downtime, not loss of data that, as you may lose data because of other reasons. Like accidental deletion, someone cracking into, hardware failure causing reading nonsense from disk and then writing nonsense results to both drives etc. etc. > realized I needed at least some minimal fault protection. Mirroring > seemed expedient. My ideal situation would be additionally backing up > things I can't bear to lose on optical or tape media, but as this is my DVDs are not expensive. and usually really small part of disk space needs to be backed up. --1626729238-11495294-1244064006=:27885--