Date: Wed, 12 Jun 2013 10:59:42 -0700 From: Dieter BSD <dieterbsd@gmail.com> To: freebsd-fs@freebsd.org Subject: FFS: fsck doesn't match doc Message-ID: <CAA3ZYrD5sj=wr3biX0%2BkDZABeuZVoZcuuyQ3YvHu01G75E_8=w@mail.gmail.com>
next in thread | raw e-mail | index | archive | help
Anyone have thoughts on bin/166499: fsck(8) behaviour does not match doc (PARTIALLY TRUNCATED INODE)? This PR has been sitting around for over a year with no comments or action. Seems to me it should appear on the list of open fs bugs, but it doesn't? A process is running, appending data to a file (*NOT* truncating the file as the doc claims!). Machine panics or otherwise goes down badly. Fsck whines about PARTIALLY TRUNCATED INODE and that fs doesn't get mounted until I run fsck manually. This happens nearly every time the machine goes down. More details are in the PR. Would it be safe to have fsck automagically fix this problem, as the doc (incorrectly) says it does?
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAA3ZYrD5sj=wr3biX0%2BkDZABeuZVoZcuuyQ3YvHu01G75E_8=w>