From: Ben Myers <bpm@sgi.com>
To: Phillip Susi <psusi@ubuntu.com>
Cc: xfs@oss.sgi.com, linux-fsdevel <linux-fsdevel@vger.kernel.org>
Subject: Re: XFS dirty after sync/reboot?
Date: Fri, 25 Jan 2013 12:50:40 -0600 [thread overview]
Message-ID: <20130125185040.GC27055@sgi.com> (raw)
In-Reply-To: <5102CFD7.20400@ubuntu.com>
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
prev parent reply other threads:[~2013-01-25 18:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-25 18:32 XFS dirty after sync/reboot? Phillip Susi
2013-01-25 18:50 ` Ben Myers [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20130125185040.GC27055@sgi.com \
--to=bpm@sgi.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=psusi@ubuntu.com \
--cc=xfs@oss.sgi.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.