Date: Mon, 8 Feb 2016 15:46:09 -0800 From: Paul Beard <paulbeard@gmail.com> Cc: FreeBSD-questions <questions@freebsd.org> Subject: Re: fsck is failing to clean a filesystem Message-ID: <7AC022B6-1922-4377-B1B4-1720F88E4205@gmail.com> In-Reply-To: <20160209003715.86885013.freebsd@edvax.de> References: <201B1734-C8F3-439A-B788-AC177D1280C3@gmail.com> <CAA2O=b9oPKX7yq4DaC2hdNY_dxFbqH9Twz42x64oRnhX5i0t4A@mail.gmail.com> <15664107-4DD3-4717-9E3E-128507A3434B@gmail.com> <20160209003715.86885013.freebsd@edvax.de>
next in thread | previous in thread | raw e-mail | index | archive | help
> On Feb 8, 2016, at 3:37 PM, Polytropon <freebsd@edvax.de> 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 ;-/=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?7AC022B6-1922-4377-B1B4-1720F88E4205>