From owner-freebsd-current@freebsd.org Sat Jan 9 09:00:36 2016 Return-Path: Delivered-To: freebsd-current@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 B06E4A68C54 for ; Sat, 9 Jan 2016 09:00:36 +0000 (UTC) (envelope-from ohartman@zedat.fu-berlin.de) Received: from outpost1.zedat.fu-berlin.de (outpost1.zedat.fu-berlin.de [130.133.4.66]) (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 7621C1AA1 for ; Sat, 9 Jan 2016 09:00:36 +0000 (UTC) (envelope-from ohartman@zedat.fu-berlin.de) Received: from inpost2.zedat.fu-berlin.de ([130.133.4.69]) by outpost.zedat.fu-berlin.de (Exim 4.85) with esmtp (envelope-from ) id <1aHpNy-003CB5-DZ>; Sat, 09 Jan 2016 10:00:34 +0100 Received: from f052010042.adsl.alicedsl.de ([78.52.10.42] helo=thor.walstatt.dynvpn.de) by inpost2.zedat.fu-berlin.de (Exim 4.85) with esmtpsa (envelope-from ) id <1aHpNy-003EAw-5r>; Sat, 09 Jan 2016 10:00:34 +0100 Date: Sat, 9 Jan 2016 10:00:29 +0100 From: "O. Hartmann" To: "Ranjan1018 ." <214748mv@gmail.com> Cc: FreeBSD CURRENT Subject: Re: [zfs] Cache on SD stops working after updating to 11-CURRENT r291458 amd64 Message-ID: <20160109100029.524a69ee.ohartman@zedat.fu-berlin.de> In-Reply-To: References: Organization: FU Berlin X-Mailer: Claws Mail 3.13.1 (GTK+ 2.24.29; amd64-portbld-freebsd11.0) MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; boundary="Sig_/T3A7YPbt4ebfZrDdrHo7N4j"; protocol="application/pgp-signature" X-Originating-IP: 78.52.10.42 X-ZEDAT-Hint: A X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 09 Jan 2016 09:00:36 -0000 --Sig_/T3A7YPbt4ebfZrDdrHo7N4j Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable Am Sat, 9 Jan 2016 09:01:48 +0100 "Ranjan1018 ." <214748mv@gmail.com> schrieb: > Hi, >=20 > I use a SD card as cache for a laptop pool sys: >=20 > # zpool status -v >=20 > pool: sys >=20 > state: ONLINE >=20 > scan: scrub repaired 0 in 1h13m with 0 errors on Mon Jan 4 00:02:42 2016 >=20 > config: >=20 > NAME STATE READ WRITE CKSUM >=20 > sys ONLINE 0 0 0 >=20 > gpt/sys0 ONLINE 0 0 0 >=20 > cache >=20 > gpt/cache ONLINE 0 0 0 >=20 >=20 > After updating 11.0-CURRENT from r291458 to r293055 the cache stops worki= ng. >=20 > I am running: >=20 > # uname -a >=20 > FreeBSD ativ 11.0-CURRENT FreeBSD 11.0-CURRENT #0 r293055: Sun Jan 3 > 00:15:33 CET 2016 root@ativ:/usr/obj/usr/src/sys/GENERIC amd64 >=20 > Fault cache status after the boot: >=20 > # zpool status -v >=20 >=20 > pool: sys >=20 > state: ONLINE >=20 > status: One or more devices could not be opened. Sufficient replicas exi= st > for >=20 > the pool to continue functioning in a degraded state. >=20 > action: Attach the missing device and online it using 'zpool online'. >=20 > see: http://illumos.org/msg/ZFS-8000-2Q >=20 > scan: scrub repaired 0 in 1h13m with 0 errors on Mon Jan 4 00:02:42 2016 >=20 > config: >=20 > NAME STATE READ WRITE CKSUM >=20 > sys ONLINE 0 0 0 >=20 > gpt/sys0 ONLINE 0 0 0 >=20 > cache >=20 > 1553023247900193278 UNAVAIL 0 0 0 was /dev/gpt/ca= che >=20 > errors: No known data errors >=20 >=20 > Trying to online the cache I have the error: >=20 > # zpool online sys gpt/cache >=20 > warning: device 'gpt/cache' onlined, but remains in faulted state >=20 > use 'zpool replace' to replace devices that are no longer present >=20 >=20 > To use the cache I need to remove & add it: >=20 > # zpool remove sys gpt/cache >=20 > # zpool add sys cache gpt/cache >=20 > -- > Maurizio > _______________________________________________ > freebsd-current@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" I have the very same problem here, I had this before Christmas, but I thoug= ht it happened due to a defective disk! This is quite awsome having another person experiencing the very(!) same pr= oblem. I experimented a while and there was no way to get the caching SD to work a= gain. In my case, even removing and adding the disk/partition for caching didn't = work. Kind regards, oh --Sig_/T3A7YPbt4ebfZrDdrHo7N4j Content-Type: application/pgp-signature Content-Description: OpenPGP digital signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQEcBAEBCAAGBQJWkMwtAAoJEOgBcD7A/5N84OIH/0Fv7IVw/i5OEwy0a1SaMbJh FCVVWUeQcDjBahWEGuUhTN/pADFkWRHT29GDA8ZmBx9PuCxxM9Tm1ekTPxrnnayJ 2nyaD14X0KoqR33Awbg1qGclqrFmnju1tI6UD0649oriH4lC7Vyy4wFmc21ed+9j O2q7DjkyOu5N0xCm7r17hpv0rY7rjUhCpd6eqcxlzL6VVbGZW+qeMhg6W5bX/aNu AOLBT2Ag0bVTYbKzLsywXeSTFOShdLU2mCsFLVhlf9Xq5njemkRg0ub/Hu/9ewP5 93x6I6GdgkWe+KUCIiXtMIEn4Jzo0WATjiXJXi5wWw12FJ8/VlFbx8uzbPK57NU= =Qm4S -----END PGP SIGNATURE----- --Sig_/T3A7YPbt4ebfZrDdrHo7N4j--