From owner-freebsd-questions@FreeBSD.ORG Tue Jan 29 12:00:03 2013 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id A35D3198 for ; Tue, 29 Jan 2013 12:00:03 +0000 (UTC) (envelope-from c.kworr@gmail.com) Received: from mail-la0-x236.google.com (la-in-x0236.1e100.net [IPv6:2a00:1450:4010:c03::236]) by mx1.freebsd.org (Postfix) with ESMTP id 32A486D6 for ; Tue, 29 Jan 2013 12:00:03 +0000 (UTC) Received: by mail-la0-f54.google.com with SMTP id gw10so217351lab.41 for ; Tue, 29 Jan 2013 04:00:02 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:message-id:date:from:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=UDmTFxsqn29Y2/Q6YyRlQs2YNowdfcJEds08YVtXtyg=; b=IEJ7gZ8RrUbdhlFehMg62M+A0kVJ9agE9Hqn18GrfYJHAnZ9d8Zm4m9dVHATgho2CX lkqh00Nv1Esu3nWRyp/5mR8ppAB5l5cRVL140cAhynMkpxb1ZiWGxISICz57M9LqgiRJ XT6T8jQdmNsTu8t4CdfmfmMZ6/qPShYMjo8D+e9HCvQ2K/bdkNAap18IL/vWudtCOavV BigqQUiKOEFkj7gDfHDlrxQF+gCdgSPy5Nyv5aPz37134Et5fsmT1VVFx3EfVF7vxH/l kl5R3N1jTdq+nxm+UunV0+7qtLk0RSTlcyefdDvB81r5OcRZ5D5jeagXolgWEmjPcMnz ohFQ== X-Received: by 10.152.105.103 with SMTP id gl7mr857640lab.41.1359460802151; Tue, 29 Jan 2013 04:00:02 -0800 (PST) Received: from [192.168.1.125] (mau.donbass.com. [92.242.127.250]) by mx.google.com with ESMTPS id fj2sm4942162lbb.6.2013.01.29.03.59.59 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 29 Jan 2013 04:00:00 -0800 (PST) Message-ID: <5107B9AB.5090800@gmail.com> Date: Tue, 29 Jan 2013 13:59:39 +0200 From: Volodymyr Kostyrko User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:18.0) Gecko/20100101 Firefox/18.0 SeaMonkey/2.15 MIME-Version: 1.0 To: Thomas Mueller Subject: Re: ZFS - whole disk or partition or BSD slice? References: <05.C7.10746.CD537015@smtp02.insight.synacor.com> In-Reply-To: <05.C7.10746.CD537015@smtp02.insight.synacor.com> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-questions@freebsd.org X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 29 Jan 2013 12:00:03 -0000 29.01.2013 04:37, Thomas Mueller: > 28.01.2013 01:57, james: >> I have a 9.1 system with some SATA disks in RAIDZ, upgraded from 9.0. >> >> The disks are all the same type, and I formatted them for FreeBSD and >> put ZFS in a slice covering most of them. >> >> I have seen suggestions for OpenIndiana etc that it is better to let ZFS >> have the whole raw disk and that this can control the way it manages the >> disk writeback mode. > > Responses from Vladimir Kostyrko ^ : > > ^ My home computer is set up in the dedicated mode. No grave difference. > ^ Not even a scratch. > >> Does this apply to FreeBSD and ZFS too? > > ^ No. > >> Presumably the disks are currently FreeBSD-specific. If I used raw >> disks instead of slices, could I read them from a Solaris system too? > > ^ I'm mostly sure you would be able to read disks from Solaris/x86. > ^ However Solaris/Sparc uses another labeling scheme. If you want to be > ^ fully compatible with other system GPT is a better choice. > > Is GPT compatible with Solaris, can Solaris access a GPT disk? Yes. I'm not sure if it can boot off GPT disk but on Solaris zpool automatically creates boundary GPT partition to protect ZFS vdev. > > I tried OpenIndiana installable live USB stick, and my Western Digital > Caviar Green 3 TB hard disk, partitioned with GPT, was not recognized or > readable; same was true for Western Digital My Book Essential 3 TB USB 3.0 > hard disk, also partitioned GPT. This was on amd64 system. Except OI. https://www.illumos.org/issues/208 -- Sphinx of black quartz, judge my vow.