From owner-freebsd-fs@FreeBSD.ORG Mon Apr 16 18:43:52 2012 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 07D30106564A for ; Mon, 16 Apr 2012 18:43:52 +0000 (UTC) (envelope-from rysto32@gmail.com) Received: from mail-wg0-f50.google.com (mail-wg0-f50.google.com [74.125.82.50]) by mx1.freebsd.org (Postfix) with ESMTP id 8DF4C8FC08 for ; Mon, 16 Apr 2012 18:43:51 +0000 (UTC) Received: by wgbds12 with SMTP id ds12so5446933wgb.31 for ; Mon, 16 Apr 2012 11:43:50 -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=EnziAQZCoAIkgcR8oL/aZmIp7el6coBQ1UZSPqYjiCU=; b=X5i1qUtgVgwvFFTkYZDVviBC18qdg7MQ5WhFAH+cnoeqRiCJAo0utgf53EHLVqDslk AbSwbFeNbT2CgeCAZFa2I88xpqVvna/J+dSZdsJj3i3rUpYJvLwEw1UYYLsVxuYvGeI2 Z88laVRsngfAkq1Z9J1horgD08+cmsBRhUpxNq5J3Fmc9cJN+0SftNTy0q6xhsXFmF0d PhSqxJSzBcyb5NYlGH2w5lC5yKV+ccEh5OBhljAeN2S7bNPM3/Iwb6XUo+r0kh/3aWJU nssjdzHBtTscROWcoP5F0QQCw/XS7O6A6/ordcP46VKNd7tyVblPiUk2Z5r3FymC2PwJ U/EA== MIME-Version: 1.0 Received: by 10.180.104.137 with SMTP id ge9mr21078425wib.20.1334601830765; Mon, 16 Apr 2012 11:43:50 -0700 (PDT) Received: by 10.180.85.71 with HTTP; Mon, 16 Apr 2012 11:43:50 -0700 (PDT) Date: Mon, 16 Apr 2012 14:43:50 -0400 Message-ID: From: Ryan Stone To: freebsd-fs@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 Subject: SU: Could an unclean shutdown cause a file with outstanding writes to become sparse after fsck? X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 16 Apr 2012 18:43:52 -0000 Today I encountered a system running a very old version of FreeBSD (6.1-ish) that was stuck in a reboot loop. I was eventually able to discover that the system was running into a long-since fixed bug where the system would panic if you tried to execute a sparse file. From what I've been able to get from the owner of this system, it sounds like the machine reset during a system upgrade. I suspect that the initial reset was unrelated (a different long-since fixed panic or a power loss, maybe), and that some executables that had outstanding writes before the reset ended up becoming sparse when fsck was run. Is this possible? The filesystem was running soft-updates, and I'm really not familiar enough with either soft-updates or even the UFS on-disk metadata to say whether this is reasonable.