From owner-freebsd-fs@FreeBSD.ORG Sun Jun 15 22:24:29 2014 Return-Path: Delivered-To: freebsd-fs@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 B829185C for ; Sun, 15 Jun 2014 22:24:29 +0000 (UTC) Received: from na01-bn1-obe.outbound.protection.outlook.com (mail-bn1blp0187.outbound.protection.outlook.com [207.46.163.187]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (Client CN "mail.protection.outlook.com", Issuer "MSIT Machine Auth CA 2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 7AC1328BC for ; Sun, 15 Jun 2014 22:24:27 +0000 (UTC) Received: from CH1PRD0310HT001.namprd03.prod.outlook.com (10.255.137.36) by BN1PR0301MB0689.namprd03.prod.outlook.com (25.160.171.26) with Microsoft SMTP Server (TLS) id 15.0.949.11; Sun, 15 Jun 2014 22:24:20 +0000 Received: from [10.0.0.114] (98.240.141.71) by pod51008.outlook.com (10.255.137.36) with Microsoft SMTP Server (TLS) id 14.16.459.0; Sun, 15 Jun 2014 22:24:18 +0000 Message-ID: <539E1D11.9070004@my.hennepintech.edu> Date: Sun, 15 Jun 2014 17:24:17 -0500 From: Andrew Berg User-Agent: Mozilla/5.0 (Windows NT 6.2; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.6.0 MIME-Version: 1.0 To: Subject: Re: ZFS pool permanent error question -- errors: Permanent errors have been detected in the following files: storage: <0x0> References: <20140615211052.GA63247@neutralgood.org> In-Reply-To: <20140615211052.GA63247@neutralgood.org> Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit X-Originating-IP: [98.240.141.71] X-Microsoft-Antispam: BL:0; ACTION:Default; RISK:Low; SCL:0; SPMLVL:NotSpam; PCL:0; RULEID: X-Forefront-PRVS: 0243E5FD68 X-Forefront-Antispam-Report: SFV:NSPM; SFS:(6009001)(428001)(199002)(189002)(24454002)(74662001)(85852003)(92726001)(92566001)(4396001)(21056001)(65806001)(102836001)(83072002)(85306003)(83506001)(74502001)(101416001)(59896001)(75432001)(23676002)(33656002)(80022001)(65956001)(64706001)(99396002)(81342001)(54356999)(19580405001)(76176999)(81542001)(87266999)(46102001)(65816999)(83322001)(86362001)(20776003)(47776003)(64126003)(66066001)(87936001)(76482001)(50466002)(88552001)(19580395003)(50986999)(105586001)(31966008)(77982001); DIR:OUT; SFP:; SCL:1; SRVR:BN1PR0301MB0689; H:CH1PRD0310HT001.namprd03.prod.outlook.com; FPR:; MLV:sfv; PTR:InfoNoRecords; A:0; MX:1; LANG:en; Received-SPF: None (: my.HennepinTech.edu does not designate permitted sender hosts) Authentication-Results: spf=none (sender IP is ) smtp.mailfrom=aberg010@my.HennepinTech.edu; X-OriginatorOrg: my.hennepintech.edu X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 15 Jun 2014 22:24:29 -0000 On 2014.06.15 16:10, kpneal@pobox.com wrote: > It looks like you are running ZFS with pools consisting of a single disk. > In cases like this if ZFS detects that a file has been corrupted ZFS is > unable to do anything to fix it. Run with the option "copies=2" to have > two copies of every file if you want ZFS to be able to fix broken files. > Of course, this doubles the amount of space you will use, so you have to > think about how important your data is to you. A proper mirror with another disk would protect against disk failure and give better performance with the same space cost, so doing that is recommended over using copies=2. > Running ZFS in a partition or on the entire disk is fine either way. But > you have to be consistent. Partitioning a disk and then writing outside > of the partition creates errors like the above GEOM one. I recommend using a partition solely to take advantage of GPT labels. Identifying disks is much easier when you create a pool using devices from labels (/dev/gpt/yourlabel). Even more so if you have a matching physical label on the disk.