From owner-freebsd-fs@FreeBSD.ORG Fri May 9 20:22:23 2014 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 83FEADA1 for ; Fri, 9 May 2014 20:22:23 +0000 (UTC) Received: from mail-lb0-x230.google.com (mail-lb0-x230.google.com [IPv6:2a00:1450:4010:c04::230]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id EF4D9F68 for ; Fri, 9 May 2014 20:22:22 +0000 (UTC) Received: by mail-lb0-f176.google.com with SMTP id p9so5755046lbv.21 for ; Fri, 09 May 2014 13:22:20 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type; bh=mcuRBFyLDeDZPzmoHJ8bG9Mj7z+9gLcdK7ibHy86OX0=; b=H3TZusJnVSYsl/G13h1FFJbr/W8iGNPQb4ikJ16/jK/0pDF0WGobd/C8be+DnGSPa2 hc/3O83WQRnd3IDF4zf5fjFeK2DM64+1NHmHLZKwkwzOGfxhAXsY8gBzWJ2Y5cE/vJnx CxMCr4TbUn23YkbgEBUXH3PCryaLvZ5Dt17FBTviPtfoSgdqR41PRksRXzmRz4+MhTO6 kBtS8FYJXP/BLvQ9TD4QFwZUQJQVDjBUQY7W4tpq5jP7GWRp3VuMaKMHGgFvPfR+xMBQ vAHuhtGQ1B92sqSiBh1m5sdvw1ijM+ylQ8wkuwI1w/aPCFwU0qP2+5uuEEZeho/Uc6eB 1uCA== MIME-Version: 1.0 X-Received: by 10.112.26.199 with SMTP id n7mr12374866lbg.27.1399666940760; Fri, 09 May 2014 13:22:20 -0700 (PDT) Received: by 10.114.78.102 with HTTP; Fri, 9 May 2014 13:22:20 -0700 (PDT) Date: Fri, 9 May 2014 13:22:20 -0700 Message-ID: Subject: Data loss in ZFS filesystem: directory disappears after extattr issues From: javocado To: FreeBSD Filesystems Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.18 X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 09 May 2014 20:22:23 -0000 OS: freebsd 8.3-RELEASE I am seeing an issue where a directory in a ZFS filesystem has just disappeared. When I do an 'ls' in that filesystem, I get: # ls ls: backup: No such file or directory regular_file1 regular_file2 regular_file3 # ... so the OS knows it is there, but then it can't show it. Note that I was running just a plain old 'ls' command, so if it really wasn't there, it would just show nothing. Also, I can autocomplete the "backup" directory from the shell ... so somehow it sees it there, but won't do anything with it. This behavior also appears in the snapshots I am making. Unfortunately I did not notice this before several older snapshots had been destroyed. So I'll never know whether the snapshots (rotated daily) taken before this directory became inaccessible were also affected. I have tried the following, but nothing has fixed the issue: - rebooting - scrub'ing the pool - zfs send | receive to a new filesystem The only interesting thing about this filesystem, and this directory, is that it contains a lot of files with extended attributes. Further, these extattrs were crashing the system regularly until we applied a patch from Pawel: http://pastebin.com/0mu50B7T ... now the crashing has stopped, but that directory has ... disappeared. This directory that is now gone is absolutely the directory whose contents were causing the crashes. We have a lot of questions about this, but maybe we can start with: What in the world is going on here ? Thanks.