From owner-freebsd-fs@freebsd.org Fri Sep 2 20:16:43 2016 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 10681BCD5E0 for ; Fri, 2 Sep 2016 20:16:43 +0000 (UTC) (envelope-from arcade@b1t.name) Received: from limbo.b1t.name (limbo.b1t.name [78.25.32.206]) by mx1.freebsd.org (Postfix) with ESMTP id B63557DD for ; Fri, 2 Sep 2016 20:16:42 +0000 (UTC) (envelope-from arcade@b1t.name) Received: from [172.29.1.160] (probe.42.lan [172.29.1.160]) by limbo.b1t.name (Postfix) with ESMTPSA id 3DAF7105 for ; Fri, 2 Sep 2016 23:16:39 +0300 (EEST) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=b1t.name; s=mail; t=1472847400; bh=qWf3LT2Wgizndbj1V2gA1snj3/4whN4IlNc1SSOXqxA=; h=Subject:To:References:From:Date:In-Reply-To; b=VWqyScVdOzvinivKM0+LOrfOi2ZTtocuQOnb1MAmYG4Ioyok1yDfHkIghh/SDiR7i vkDiD9dpJNSS3ToZnmNSjYxPLP0dyIN9ohzlRqIX6G1CCqc9GKXQQ4JBi2BVewWat3 3l+0fs/kAycQBBHdL5njqK+dWU7otb3Cpv3BFFPk= Subject: Re: phantom snapshots To: freebsd-fs@freebsd.org References: <58816ff0-3ab2-cbae-3d50-c4d5e89d9773@kateley.com> <57C9D1FB.6040904@b1t.name> From: Volodymyr Kostyrko Message-ID: <57C9DE27.8020806@b1t.name> Date: Fri, 2 Sep 2016 23:16:39 +0300 User-Agent: Mozilla/5.0 (X11; DragonFly x86_64; rv:42.0) Gecko/20100101 Firefox/42.0 SeaMonkey/2.39 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 02 Sep 2016 20:16:43 -0000 Linda Kateley wrote: > > > On 9/2/16 2:24 PM, Volodymyr Kostyrko wrote: >> Linda Kateley wrote: >>> So I think I have isolated this to a phantom snapshot. At the end of >>> this zpool status although the names change everytime I run scrub, it >>> show unrecoverable error of files in a snapshot that doesn't exit. >>> >>> It also has in that zfs dataset it has a .zfs directory with a name of >>> old snaps. >>> >>> Anyone know how to view or clear these phantom snaps? I tried to remove >>> the files in the snapshot directory, but it is read-only. >> >> This looks like pointers to files that were already deleted/purged. I >> once faced this errors but that was on bad controller, I don't think >> this can be caused by bad memory/errors. When that happened I scrubbed >> pool, removed all files noted, cleaned zpool errors (they are >> persistent, even the file was removed and snapshots doen't exist they >> are still shown) and scrubbed the pool again. > How did you remove the files in the snapshot? I keep trying but it is > read-only? Can I remount it read-write? I just removed snapshots. Snapshot can't be remounted r/w. Snapshot can be cloned to obtain writable FS access, but after that snapshots become indestructible until only one snapshot successor remains. -- Sphinx of black quartz judge my vow.