From owner-freebsd-questions@freebsd.org Mon Feb 8 23:46:14 2016 Return-Path: Delivered-To: freebsd-questions@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 3A9A4AA14E3 for ; Mon, 8 Feb 2016 23:46:14 +0000 (UTC) (envelope-from paulbeard@gmail.com) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id 195E4186C for ; Mon, 8 Feb 2016 23:46:14 +0000 (UTC) (envelope-from paulbeard@gmail.com) Received: by mailman.ysv.freebsd.org (Postfix) id 16EFCAA14E2; Mon, 8 Feb 2016 23:46:14 +0000 (UTC) Delivered-To: questions@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 F0D80AA14E1 for ; Mon, 8 Feb 2016 23:46:13 +0000 (UTC) (envelope-from paulbeard@gmail.com) Received: from mail-pf0-x22c.google.com (mail-pf0-x22c.google.com [IPv6:2607:f8b0:400e:c00::22c]) (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 C256F186B for ; Mon, 8 Feb 2016 23:46:13 +0000 (UTC) (envelope-from paulbeard@gmail.com) Received: by mail-pf0-x22c.google.com with SMTP id e127so21964574pfe.3 for ; Mon, 08 Feb 2016 15:46:13 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=content-type:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references; bh=eodboNEn4lcMcR8ZtOazsf3gWcS7btuWDGtE3pwO/JY=; b=WciC43trF9wxIJTx4G8raAhPKQ0fzh7QUynQ7cAk2nkJLU6xzsAzF5oAtq1CF3H48/ eav0n3SytaDryCQPuTlV1cDFV2d6GwTI2Z8YhFoMJS24O831+75dNLk+FjtOwfdE1neD Nt7Ica9VWhPL7n83GEicxdf5dCexvfJs61VtlnsZU8/Bq+bnBS2rpFIK/ayjyLPjzyvM AIcxEtRspo+HgS2bwIBFjir2VvyYrLJ0AL8BmM4s9BoEsSOCb8IGdXou1U6aPR6JC3o9 zD+WsqQm+YbJtjOElUgcJUM/nkcXggvhA+oiRAxOyFO1EtigMtV2d0+9fviFQakNJ6VQ LC2Q== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:content-type:mime-version:subject:from :in-reply-to:date:cc:content-transfer-encoding:message-id:references; bh=eodboNEn4lcMcR8ZtOazsf3gWcS7btuWDGtE3pwO/JY=; b=Aw0ACZWETVGlMk5lik0pt945GXzNU/447EkQ8CLSfNpIgI+YL7GtomTC2ZC4V4erTg Vq9JAs4tgOjx648oaEzulHJ3BsCQeG/zcQtqFsEaeV92bq81Ys47uZzMCO6tz8f4DC6N /Io2G0UpK1F1zvQs1ZlBlCgfBfWbdLE4AoLsnMdvcJf3/cjPljDaG5zn3MQx25Wn163E +Fu8Y5SlKumrjKXtoyT1D5RG9XP0pVjhRtQa0p2mN6D7VNjDHhuz8cNvtDhmcpDjzl5y zMsamWfhxg8BY0pFwskRxtc/E/5UWt2s3on98uRhU9zT6xzz7bG4ICid7xzKVxubxgkm t99Q== X-Gm-Message-State: AG10YOTE2JMEFvk0zpgpQLrGBM9Vpy2rcESH/nFK4rRAbhbe7t7LRBdhpVd7PiCJpFSgVA== X-Received: by 10.98.71.92 with SMTP id u89mr46262459pfa.122.1454975173471; Mon, 08 Feb 2016 15:46:13 -0800 (PST) Received: from ?IPv6:2001:470:b:839:6430:b21f:cd92:c24c? ([2001:470:b:839:6430:b21f:cd92:c24c]) by smtp.gmail.com with ESMTPSA id 3sm45774775pfb.64.2016.02.08.15.46.11 for (version=TLS1 cipher=ECDHE-RSA-AES128-SHA bits=128/128); Mon, 08 Feb 2016 15:46:12 -0800 (PST) Content-Type: text/plain; charset=utf-8 Mime-Version: 1.0 (Mac OS X Mail 9.2 \(3112\)) Subject: Re: fsck is failing to clean a filesystem From: Paul Beard In-Reply-To: <20160209003715.86885013.freebsd@edvax.de> Date: Mon, 8 Feb 2016 15:46:09 -0800 Cc: FreeBSD-questions Content-Transfer-Encoding: quoted-printable Message-Id: <7AC022B6-1922-4377-B1B4-1720F88E4205@gmail.com> References: <201B1734-C8F3-439A-B788-AC177D1280C3@gmail.com> <15664107-4DD3-4717-9E3E-128507A3434B@gmail.com> <20160209003715.86885013.freebsd@edvax.de> X-Mailer: Apple Mail (2.3112) X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 08 Feb 2016 23:46:14 -0000 > On Feb 8, 2016, at 3:37 PM, Polytropon wrote: >=20 > However, the fsck output indicates a quite heavy file system > inconsistency problem. In worst case, mount -o ro, copy all > files, re-initialize the filesystem with newfs, and then copy > the files back. Use tar or rsync or cpio to make sure all the > file attributes are properly transferred. This should be possible > in case you cannot resolve the filesystem problem. That=E2=80=99s the course I=E2=80=99m, creating a new virtual disk to = copy everything to.=20 > This indicates that the inode entry for "..", the parent directory, > does not have a valid node type (file, directory, special, link, = etc.). > So fsck doesn't know how to "re-instantiate" this particular ".." > entry, as it seems. >=20 I couldn=E2=80=99t make sense of the original message or more = accurately, what the=20 solution might be. Sounds like there isn=E2=80=99t one ;-/=