From: Jason White <jason@jasonjgw.net>
To: xfs@oss.sgi.com
Subject: Re: Installing grub onto a system with XFS root fs
Date: Mon, 17 Dec 2007 12:46:27 +1100 [thread overview]
Message-ID: <20071217014627.GA13692@jdc.jasonjgw.net> (raw)
In-Reply-To: <4765CBBF.1020207@sandeen.net>
On Sun, Dec 16, 2007 at 07:07:11PM -0600, Eric Sandeen wrote:
> Hard to say - in a nutshell, grub just sucks w.r.t. how it (ab)uses the
> filesystem it's trying to install on.
>
> In some invocations, it actually writes directly to the block device
> *while it is mounted* - this leads to data corruption and/or filesystem
> corruption.
>
> In other cases, in a "verification" phase, it tries to directly read
> filesystem structures off the disk *while it is mounted* after a couple
> of wishful sync; sync;'s - this often can lead to a grub hang when it
> goes off in the weeds on inconsistent disk data that it finds.
>
> I think various distros have tried to hack around these problems in
> different ways; the freeze above is probably an effort to coalesce the
> filesystem before grub goes groveling around the disk to verify what it
> just wrote(!).
>
Thanks for the background. The most up to date bug report and discussion I
could find is here:
https://bugs.launchpad.net/debian/+source/grub/+bug/8058
(for Ubuntu).
There are also Debian bugs for this, such as
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=239111
Manually unfreezing the file system with xfs_freeze -u /
worked for me on one machine. (This was done while grub-install was executing,
after it executed xfs_freeze).
next prev parent reply other threads:[~2007-12-17 1:48 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-17 0:49 Installing grub onto a system with XFS root fs Jason White
2007-12-17 1:07 ` Eric Sandeen
2007-12-17 1:46 ` Jason White [this message]
2007-12-17 3:12 ` Eric Sandeen
2007-12-17 13:28 ` Martin Steigerwald
2007-12-17 23:04 ` Jason White
2007-12-18 0:35 ` David Chinner
2007-12-18 22:03 ` Martin Steigerwald
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=20071217014627.GA13692@jdc.jasonjgw.net \
--to=jason@jasonjgw.net \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox