Date: Mon, 8 Feb 2016 22:32:24 -0430 From: Alberto Mijares <amijaresp@gmail.com> To: Polytropon <freebsd@edvax.de> Cc: Paul Beard <paulbeard@gmail.com>, FreeBSD-questions <questions@freebsd.org> Subject: Re: fsck is failing to clean a filesystem Message-ID: <CAGZBXN9nmGm0VLQCdr_9NBivsTo8buoyJLgYX9Xqs26gy1MvcA@mail.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
> 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. > > And check if /usr/lost+found does already contain something. > Just in case. > I wonder if mounting an external disk on /usr/lost+found can help. Don't know, just guessing ;-) Best regards, Alberto Mijares
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAGZBXN9nmGm0VLQCdr_9NBivsTo8buoyJLgYX9Xqs26gy1MvcA>