[Top] [All Lists]

Re: [Bisected] Corruption of root fs during git bisect of drm system han

To: Markus Trippelsdorf <markus@xxxxxxxxxxxxxxx>
Subject: Re: [Bisected] Corruption of root fs during git bisect of drm system hang
From: Stefan Ring <stefanrin@xxxxxxxxx>
Date: Fri, 19 Jul 2013 14:41:29 +0200
Cc: Dave Chinner <david@xxxxxxxxxxxxx>, Ben Myers <bpm@xxxxxxx>, Mark Tinguely <tinguely@xxxxxxx>, Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>, Linux fs XFS <xfs@xxxxxxxxxxx>
Delivered-to: xfs@xxxxxxxxxxx
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=WDofBQcF7m5VwY9/4dqRW3aT69FqFVuG0bf7TI5MOb0=; b=BfRR7ke1ZFnhyEHJd55p9eUKipjl6rnYVVJbbLwi8IPaf2BjHiNiw/BEB2L8KJzvNy RCGUrtJrMRcnWf2RmDAhbB4BFbUCAM6xToEcMNiI6mJk4u2xGTLBbFt2CZOgBawwPPOm GQfCQN0JnpcFjWYXe41eeWKI4Wt07WmWKv1vJXY1Oj+M9LHHzrtjqBAwU9nEcR7OCcaQ QYSB8HiPef4kFmJ7rEn3/zOtEjUPFC0UMlWgqiHSLOzhxb0g6jeRR34V1urg7g7zRj+f 9igUGM0T7qVgMhcMIkL2D8CT1PqKJNACfmklxnZsmnyWdAlKcTkFFzmrn42kOoAGRwlb h7XA==
In-reply-to: <20130719122235.GA360@x4>
References: <20130713090523.GA362@x4> <20130712070721.GA359@x4> <20130715022841.GH5228@dastard> <20130715064734.GA361@x4> <20130719122235.GA360@x4>
> I've bisected this issue to the following commit:
>  commit cca9f93a52d2ead50b5da59ca83d5f469ee4be5f
>  Author: Dave Chinner <dchinner@xxxxxxxxxx>
>  Date:   Thu Jun 27 16:04:49 2013 +1000
>      xfs: don't do IO when creating an new inode
> Reverting this commit on top of the Linus tree "solves" all problems for
> me. IOW I no longer loose my KDE and LibreOffice config files during a
> crash. Log recovery now works fine and xfs_repair shows no issues.
> So users of 3.11.0-rc1 beware. Only run this version if you have
> up-to-date backups handy.

What I miss in this thread is a distinction between filesystem
corruption on the one hand and a few zeroed files on the other. The
latter may be a nuisance, but it is expected behavior, while the
former should never happen, period, if I'm not mistaken.

<Prev in Thread] Current Thread [Next in Thread>