From owner-freebsd-hackers@freebsd.org Wed Dec 14 16:14:32 2016 Return-Path: Delivered-To: freebsd-hackers@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 B07F0C66DA1 for ; Wed, 14 Dec 2016 16:14:32 +0000 (UTC) (envelope-from asomers@gmail.com) Received: from mailman.ysv.freebsd.org (unknown [127.0.1.3]) by mx1.freebsd.org (Postfix) with ESMTP id 8D4591730 for ; Wed, 14 Dec 2016 16:14:32 +0000 (UTC) (envelope-from asomers@gmail.com) Received: by mailman.ysv.freebsd.org (Postfix) id 899D7C66D9D; Wed, 14 Dec 2016 16:14:32 +0000 (UTC) Delivered-To: hackers@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 8945EC66D9A for ; Wed, 14 Dec 2016 16:14:32 +0000 (UTC) (envelope-from asomers@gmail.com) Received: from mail-qk0-x244.google.com (mail-qk0-x244.google.com [IPv6:2607:f8b0:400d:c09::244]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4704E172A for ; Wed, 14 Dec 2016 16:14:32 +0000 (UTC) (envelope-from asomers@gmail.com) Received: by mail-qk0-x244.google.com with SMTP id h201so3732301qke.3 for ; Wed, 14 Dec 2016 08:14:32 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc:content-transfer-encoding; bh=Tk8r9S72fn6zb0eFlJFjSohT3yqzHe+mnoDOKiQvLWk=; b=mXtoCMHWHO2WqkPc8DN/xt/dZR1KiVbzkDwaL/rL4hOjFb5XrKMDaI8mXSprhbS9pv /JSGrgIR/G3qgprpEejU5FqRTtWq6eUmf+0s8IQxGz+fpw9BQkPPbR6uUYORmuPM4Zw1 BdQcg5CsjaUGsjQfvco+fkndNvHfjkguhlRiOfbSs38WaVbFXV7V2zdSe/nsKuAnZhtj xKQEmwoztHUHZSWr6tq8cNHM7W6Ip3QHPiWuQvBqk1GjLT0QBQ4KxYjVw0Ez25A9cro9 /DQELC/CfSxxzH+2FrOrn1/c4XQpNV3wsWrR3cUZZYubNu0THsoy8y3VfD4aJxB54pmL E+gA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to:cc:content-transfer-encoding; bh=Tk8r9S72fn6zb0eFlJFjSohT3yqzHe+mnoDOKiQvLWk=; b=LkbVrkxF+h15gMecXmOvIlzsq+HisRXqY/RJGnIs93hx0Wzvzr3QjTOQoaktz8Kzc6 KHDgvYG2Z0YD+cQHb2hsgSaOQcxtCZr+LSN64BqO02ePUtR38Cjs8yz8bv2CtjI5bG3d ccyOWpPV7s7jdUuM8E9XiVi0+vnFRRUHGWDx36ASIJOJ2cfC6orBMFv9I2Ea3U4IzV7W ez5Zdjzdln5IaSlAT81w6qie+9FCXFx6amDpnlzVrqfqGmUtxieZ3H0RwBJ1COPsfxtU 0kMVSrKC4oPOs6FE7WkdIlDnwt4bux5KVw49BescRi8tlXk8N+U3InJqQ8E1ovvQdoG/ UpUA== X-Gm-Message-State: AKaTC00bfUwL8mJ52M5BOPLHd3gH9wne06SvMSA+Z3s9wY02JoJXCMgg9XGB7pTiZl/WVaSh4tH2ZXvWKpSApQ== X-Received: by 10.55.140.132 with SMTP id o126mr100165561qkd.227.1481732071299; Wed, 14 Dec 2016 08:14:31 -0800 (PST) MIME-Version: 1.0 Sender: asomers@gmail.com Received: by 10.12.174.145 with HTTP; Wed, 14 Dec 2016 08:14:30 -0800 (PST) In-Reply-To: References: From: Alan Somers Date: Wed, 14 Dec 2016 09:14:30 -0700 X-Google-Sender-Auth: 7k8N1I3Gnu4m-OCyTVidUTWNfKU Message-ID: Subject: Re: ZFS - directory entry To: Dirk-Willem van Gulik Cc: FreeBSD Hackers Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 14 Dec 2016 16:14:32 -0000 On Wed, Dec 14, 2016 at 8:27 AM, Dirk-Willem van Gulik wrote: > A rather odd directory entry (in /root, the home dir of root/toor) appear= ed on a bog standard FreeBSD 10.2 (p18) lightly loaded machine under ZFS du= ring/post a backup: > > $ ls -la /root | tail -q > ---------- 1 root wheel 9223372036854775807 Jan 1 1970 ?%+?kD?H???x= ,?5?Dh;*s!?h???jw??????\h?:????????``?13?@?????OA????????Puux???? > OS and ZFS is installed with a bog standard sysinstall. =E2=80=98SMART=E2= =80=99 nor smartd have reported anything. nothing in dmesg, syslog of boot = log. Any suggestions as how to debug or get to the root of this ? > > And in particular - what is a risk of a reboot (to get a kernel with debu= g, etc) causing the issue to =E2=80=98go away=E2=80=99 - and hence stopping= the forensic ? > > Dw. > > sudo zpool list -v > NAME SIZE ALLOC FREE EXPANDSZ FRAG CAP DEDUP HEALTH A= LTROOT > tank 25.2T 9.27T 16.0T - 17% 36% 1.53x ONLINE - > raidz3 25.2T 9.27T 16.0T - 17% 36% > ada0p3 - - - - - - > ada1p3 - - - - - - > ada2p3 - - - - - - > ada3p3 - - - - - - > ada4p3 - - - - - - > ada5p3 - - - - - - > ada6p3 - - - - - - Two things to try: 1) zpool scrub. This will reveal any corrupt metadata objects 2) Maybe the filename is created in an encoding not supported by your current terminal. Try "LANG=3Den_US.UTF-8 ls -l" 3) Use zdb to examine the file. First, do "ls -li /root" to get the object id. It's the same as the inode number. Then, assuming /root is in the tank/root filesystem, do "zdb -ddddd tank/root ". That might reveal some clues. -Alan