From owner-freebsd-fs@freebsd.org Fri May 26 10:43:13 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 2271BD81BA7 for ; Fri, 26 May 2017 10:43:13 +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 B488E16E3 for ; Fri, 26 May 2017 10:43:12 +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 52D49D0B; Fri, 26 May 2017 12:43:10 +0200 (CEST) X-Virus-Scanned: amavisd-new at freebsd.systems Received: from mail.freebsd.systems ([5.196.167.1]) by mail.freebsd.systems (scan.freebsd.systems [5.196.167.1]) (amavisd-new, port 10026) with ESMTP id Xr9MnKMOXwom; Fri, 26 May 2017 12:43:10 +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 6C8BCD05; Fri, 26 May 2017 12:43:09 +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=1495795389; bh=LceJx8UcWa2MFcOJJb3HUotO0/L+06uOn3KaRJYSMDo=; h=To:Cc:References:From:Date:In-Reply-To; b=h+PmaSz7bDQuyjUjT3PT6RgeVtnbRH30t+OMJmVh5NDo07FQqEKb8cBGM30A6ZSjW 6sditvXUPtG/M8wIy1iXnkqELofw98+8EnnaR4zC4vRgeOpBIffGVlH8MfP5pKMnX+ awdqM4EOFllQZ1N0CYosqgY6xdz5l62fMZW/kFv4txtVfeQL9TTzk1XABfCycXXEKC ++4OtLUTapt6HHxh1RXl4B2F7oloUVFVSWeyraZ3psYpQBolyPfGsr+ZqfV9tKGK4X leyH+HsGzpiO10ImnUBgjkq19uJGpHwB5yxpSyXLZxCpex4c8w1E6lfW9a1vCNMUdb 8opn2atHDTn3A== Subject: Re: Problem with zpool remove of log device To: =?UTF-8?Q?Karli_Sj=c3=b6berg?= Cc: freebsd-fs@freebsd.org References: <2ce18904-9fc6-47f8-945c-ef1270a3b56e@email.android.com> From: =?UTF-8?Q?=c5=81ukasz_W=c4=85sikowski?= Message-ID: <0f7be3c4-de84-527d-95b2-aead2f7d6afa@wasikowski.net> Date: Fri, 26 May 2017 12:42:59 +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: <2ce18904-9fc6-47f8-945c-ef1270a3b56e@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 10:43:13 -0000 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. -- best regards, Lukasz Wasikowski