From owner-freebsd-fs@freebsd.org Fri May 26 11:11:04 2017 Return-Path: Delivered-To: freebsd-fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 85DD9D7BA41 for ; Fri, 26 May 2017 11:11:04 +0000 (UTC) (envelope-from lukasz@wasikowski.net) Received: from mail.freebsd.systems (mail.freebsd.systems [5.196.167.1]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 01082178D for ; Fri, 26 May 2017 11:11:03 +0000 (UTC) (envelope-from lukasz@wasikowski.net) Received: from mail.freebsd.systems (mail.freebsd.systems [IPv6:2001:41d0:2:1276::1]) by mail.freebsd.systems (Postfix) with ESMTP id 65168D8E; Fri, 26 May 2017 13:10:30 +0200 (CEST) X-Virus-Scanned: amavisd-new at freebsd.systems Received: from mail.freebsd.systems ([IPv6:2001:41d0:2:1276::1]) by mail.freebsd.systems (scan.freebsd.systems [IPv6:2001:41d0:2:1276::1]) (amavisd-new, port 10026) with ESMTP id 8Bh2hF6EDKSf; Fri, 26 May 2017 13:10:30 +0200 (CEST) Received: from [192.168.138.100] (unknown [194.181.68.244]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by mail.freebsd.systems (Postfix) with ESMTPSA id 086ADD88; Fri, 26 May 2017 13:10:28 +0200 (CEST) Authentication-Results: mail.freebsd.systems; dmarc=none header.from=wasikowski.net Authentication-Results: mail.freebsd.systems; spf=pass smtp.mailfrom=lukasz@wasikowski.net DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=wasikowski.net; s=default; t=1495797029; bh=EsOYUdRlqAwdoQbnBTFwd3KzUAJOWoleA5JWcgXbdDw=; h=To:Cc:References:From:Date:In-Reply-To; b=SG+gLicVKxeSdeSU3whWldGrxjoY90nkFbQGXp8pQiji0Oahxm2b8mHQCg97SSP5k 0f5QocFXEuoyWXAdug91OZs01eJLWypfE+BtpF7ct9CQ0Eccelem4uvQPmpT5zKZ9w DhwJWxMMsK+dQXYn8wly7CXL6HshtYem0CD7s0FlUyT1012VyI9Kax6hHFj3Pv7HGm 6D3rwjNR7e4bYulQuFkkCLb+uG0wtjuJSH5q1a0LivSEi6jchb4+mYczcbGIi6dqgM 28EUx62tQGRzbD3XO/mknhtWBdo2lFq57YqUaTeXSF8rCTXTRg4Q0QB1GftaNhlu/v hrhxComuH2ryA== Subject: Re: Problem with zpool remove of log device To: =?UTF-8?Q?Karli_Sj=c3=b6berg?= Cc: freebsd-fs@freebsd.org References: <7fc4a6f3-df1b-47b4-9399-0dd6614ddf94@email.android.com> From: =?UTF-8?Q?=c5=81ukasz_W=c4=85sikowski?= Message-ID: Date: Fri, 26 May 2017 13:10:16 +0200 User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.1.1 MIME-Version: 1.0 In-Reply-To: <7fc4a6f3-df1b-47b4-9399-0dd6614ddf94@email.android.com> Content-Type: text/plain; charset=utf-8 Content-Language: pl Content-Transfer-Encoding: 8bit X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 26 May 2017 11:11:04 -0000 W dniu 2017-05-26 o 12:46, Karli Sjöberg pisze: > > > Den 26 maj 2017 12:43 em skrev Łukasz Wąsikowski : > > W dniu 2017-05-26 o 12:37, Karli Sjöberg pisze: > > > Den 26 maj 2017 12:30 em skrev Łukasz Wąsikowski : > > > > W dniu 2017-05-26 o 12:20, Karli Sjöberg pisze: > > > > > > > > > Den 26 maj 2017 11:47 fm skrev Łukasz Wąsikowski : > > > > > > Hi, > > > > > > I cant remove log device from pool - operation ends ok, but log > device > > > is still in the pool (bug?). > > > > > > # uname -a > > > FreeBSD xxx.yyy.com 11.0-STABLE FreeBSD 11.0-STABLE #0 r316543: > > Thu Apr > > > 6 08:22:43 CEST 2017 root@xxx.yyy.com:/usr/obj/usr/src/sys/YYY amd64 > > > > > > # zpool status tank > > > pool: tank > > > state: ONLINE > > > status: One or more devices are configured to use a non-native block > > > size. > > > Expect reduced performance. > > > action: Replace affected devices with devices that support the > > > configured block size, or migrate data to a properly configured > > > pool. > > > scan: scrub repaired 0 in 22h21m with 0 errors on Thu May 25 > > > 02:26:36 2017 > > > config: > > > > > > NAME STATE READ WRITE CKSUM > > > tank ONLINE 0 0 0 > > > mirror-0 ONLINE 0 0 0 > > > ada2p3 ONLINE 0 0 0 > > > ada3p3 ONLINE 0 0 0 > > > logs > > > mirror-1 ONLINE 0 0 0 > > > gpt/tankssdzil0 ONLINE 0 0 0 block size: > > > 512B configured, 4096B native > > > gpt/tankssdzil1 ONLINE 0 0 0 block size: > > > 512B configured, 4096B native > > > > > > errors: No known data errors > > > > > > When I try to remove log device operation ends without errors: > > > > > > # zpool remove tank mirror-1; echo $? > > > 0 > > > > > > > > > You are missing the actual disk you want to remove from the mirror: > > > # zpool remove tank gpt/tankssdzil1 > > > > # zpool remove tank gpt/tankssdzil0 > > cannot remove gpt/tankssdzil0: operation not supported on this type > > of pool > > > > > > Yeah, that's because you're booting off of it right? Boot from CD or > > whatev, should work. Or if it was the "bootfs" zpool option, can't > > remember, but it's something along those lines. Really silly, but > anyway... > > Yes, it's root-on-zfs. But as I said on other box with similar > configuration it works. Strange. > > It's production box so boot from CD is not an easy option. I'll check it > during next service window. Thank you for your help. > > > AFAIR you just need to null the bootfs zpool option, remove the log disk > and then reset bootfs to what it was before. No luck. # zpool get bootfs NAME PROPERTY VALUE SOURCE tank bootfs tank/ROOTFS local tankssd bootfs - default # zpool set bootfs='' tank # zpool get bootfs tank NAME PROPERTY VALUE SOURCE tank bootfs - default # zpool remove tank mirror-1; echo $? 0 # zpool status tank pool: tank state: ONLINE status: One or more devices are configured to use a non-native block size. Expect reduced performance. action: Replace affected devices with devices that support the configured block size, or migrate data to a properly configured pool. scan: scrub repaired 0 in 22h21m with 0 errors on Thu May 25 02:26:36 2017 config: NAME STATE READ WRITE CKSUM tank ONLINE 0 0 0 mirror-0 ONLINE 0 0 0 ada2p3 ONLINE 0 0 0 ada3p3 ONLINE 0 0 0 logs mirror-1 ONLINE 0 0 0 gpt/tankssdzil0 ONLINE 0 0 0 block size: 512B configured, 4096B native gpt/tankssdzil1 ONLINE 0 0 0 block size: 512B configured, 4096B native errors: No known data errors # zpool remove tank gpt/tankssdzil0; echo $? cannot remove gpt/tankssdzil0: operation not supported on this type of pool 1 -- best regards, Lukasz Wasikowski