From owner-freebsd-fs@FreeBSD.ORG Wed Jun 12 17:59:42 2013 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id D10D55FC for ; Wed, 12 Jun 2013 17:59:42 +0000 (UTC) (envelope-from dieterbsd@gmail.com) Received: from mail-ie0-x242.google.com (mail-ie0-x242.google.com [IPv6:2607:f8b0:4001:c03::242]) by mx1.freebsd.org (Postfix) with ESMTP id AC70216FC for ; Wed, 12 Jun 2013 17:59:42 +0000 (UTC) Received: by mail-ie0-f194.google.com with SMTP id 9so1834772iec.5 for ; Wed, 12 Jun 2013 10:59:42 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type; bh=5m7cEcPBUjlr+wRt2UuWBIGRBr3N16Jvwkxs5XAVqdI=; b=d7Ce8tGAZejQZ0XNCNXEAs6lLQxCAbDTmgkrM/HYZyLdposbmeWlVeWIQCtW9lyuD9 YZrIslEk0TT8ObGqKGNjhiF0fiwZCBVMX6ueo9ASxCxr8uR52q0Ut8+1EEIO/ccRat13 t/ZSMFmL0b5+ot/xTpl4+bUbkS5DOFPFYnoFpsp83C9cGTU/SpUQ+BoOKo7pQcx/mJs8 pbexftTIwj/lx9hPM93bT/HdRACZajRFc+jHxqpuHGfD+fNVsDEj7rItIfiFWqHYuUse AjpbSzbf+6OX11PL6x5SbnSGfoVXc0zeTn3DpZFZt8Dz6RY+TS3uHarN+8VxRl4fgz8w 7s9g== MIME-Version: 1.0 X-Received: by 10.50.83.37 with SMTP id n5mr4022003igy.44.1371059982336; Wed, 12 Jun 2013 10:59:42 -0700 (PDT) Received: by 10.64.139.34 with HTTP; Wed, 12 Jun 2013 10:59:42 -0700 (PDT) Date: Wed, 12 Jun 2013 10:59:42 -0700 Message-ID: Subject: FFS: fsck doesn't match doc From: Dieter BSD To: freebsd-fs@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 12 Jun 2013 17:59:42 -0000 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?