From mboxrd@z Thu Jan 1 00:00:00 1970 From: Ben Myers Subject: Re: XFS dirty after sync/reboot? Date: Fri, 25 Jan 2013 12:50:40 -0600 Message-ID: <20130125185040.GC27055@sgi.com> References: <5102CFD7.20400@ubuntu.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: xfs@oss.sgi.com, linux-fsdevel To: Phillip Susi Return-path: Received: from relay2.sgi.com ([192.48.179.30]:50430 "EHLO relay.sgi.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1755459Ab3AYSuo (ORCPT ); Fri, 25 Jan 2013 13:50:44 -0500 Content-Disposition: inline In-Reply-To: <5102CFD7.20400@ubuntu.com> Sender: linux-fsdevel-owner@vger.kernel.org List-ID: Hey Philip, On Fri, Jan 25, 2013 at 01:32:55PM -0500, Phillip Susi wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > While triaging a bug filed in Ubuntu involving odd reboot failures, it > appears that XFS leaves the filesystem in a corrupt state that > requires journal playback to fix after a sync or reboot. Grub2 > doesn't seem to understand the journal, leading to all kinds of > confusion after the reboot. > > Shouldn't a full sync or remount to r/o flush the journal transactions > and leave the fs fully clean? It should. We have a bug in xfs in that area. > Original bug report: https://launchpad.net/bugs/1103187 Try this patch which was recently proposed for 3.5-3.7 stable trees: http://oss.sgi.com/archives/xfs/2012-12/msg00324.html Regards, Ben