From owner-freebsd-stable@FreeBSD.ORG Mon May 30 10:10:54 2011 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id B6C5B1065670 for ; Mon, 30 May 2011 10:10:54 +0000 (UTC) (envelope-from O.Seibert@cs.ru.nl) Received: from kookpunt.science.ru.nl (kookpunt.science.ru.nl [131.174.30.61]) by mx1.freebsd.org (Postfix) with ESMTP id 488DC8FC1D for ; Mon, 30 May 2011 10:10:53 +0000 (UTC) Received: from twoquid.cs.ru.nl (twoquid.cs.ru.nl [131.174.142.38]) by kookpunt.science.ru.nl (8.13.7/5.31) with ESMTP id p4UAApTj009587; Mon, 30 May 2011 12:10:51 +0200 (MEST) Received: by twoquid.cs.ru.nl (Postfix, from userid 4100) id 853352E03C; Mon, 30 May 2011 12:10:51 +0200 (CEST) Date: Mon, 30 May 2011 12:10:51 +0200 From: Olaf Seibert To: freebsd-stable@freebsd.org Message-ID: <20110530101051.GA49825@twoquid.cs.ru.nl> References: <20110530093546.GX6733@twoquid.cs.ru.nl> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20110530093546.GX6733@twoquid.cs.ru.nl> User-Agent: Mutt/1.5.19 (2009-01-05) X-Spam-Score: -1.799 () ALL_TRUSTED,BAYES_50 X-Scanned-By: MIMEDefang 2.63 on 131.174.30.61 Subject: Re: ZFS I/O errors X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 30 May 2011 10:10:54 -0000 On Mon 30 May 2011 at 11:35:46 +0200, Olaf Seibert wrote: > How do I identify which files it is listing here? The nighly 'find' has found the files for me. It is actually a bunch of directories, that were likely in use when the crash occurred. They give an "interesting" error when you try to ls them: find: /tank/vol-fourquid-1/evadh/CLEF-IP11/PARSED_CORPUS/EP/000000/45/97: Illegal byte sequence The file system is compressed, that may be the reason it can identify "illegal byte sequence"s. It isn't even possible to rm -r the directories, or even to mv them... (fortunately the standard trick works: move the parent directory instead, create a new one in its old place, and move the old, good, contents back). but now I seem to be left with some directories (elsewhere) that I still can't remove... > -Olaf. > -- > Pipe rene = new PipePicture(); assert(Not rene.GetType().Equals(Pipe));