From: Nathan Scott <nscott@aconex.com>
To: Chris Wedgwood <cw@f00f.org>
Cc: Peter Gervai <grinapo@gmail.com>, xfs@oss.sgi.com
Subject: Re: how to sync / commit data to disk?
Date: Wed, 24 Jan 2007 09:24:29 +1100 [thread overview]
Message-ID: <1169591069.18017.143.camel@edge> (raw)
In-Reply-To: <20070123165050.GA28720@tuatara.stupidest.org>
On Tue, 2007-01-23 at 08:50 -0800, Chris Wedgwood wrote:
> On Tue, Jan 23, 2007 at 04:16:59PM +0100, Peter Gervai wrote:
>
> > This problem seem to have arisen in grub bootloader under Debian
> > linux (and most probably everywhere else): it must be sure that the
> > copied files are there, and can be addressed by C/H/S and modified
> > there, at the given sector address.
>
> grub is broken
>
> this comes up all the time, there are various work-arounds but it
> doesn't change the fact that GRUB IS BROKEN
>
> it would be nice if someone would just address it from that end
>
> > xfs_freeze -f
> > sync
> > xfs_freeze -u
>
> sync before freeze (actually, I'm not sure a sync there is necessary
> but it can't hurt)
Its not necessary (would be a bug if so).
FWIW, this hack can be better achieved in a filesystem independent way
by doing a remount,ro ... remount,rw instead of freeze/thaw.
cheers.
--
Nathan
next prev parent reply other threads:[~2007-01-23 22:26 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-23 15:16 how to sync / commit data to disk? Peter Gervai
2007-01-23 15:58 ` Geir A. Myrestrand
2007-01-23 16:08 ` Eric Sandeen
2007-01-23 20:33 ` Peter Gervai
2007-01-23 21:43 ` Eric Sandeen
2007-01-24 6:21 ` Chris Wedgwood
2007-01-23 16:50 ` Chris Wedgwood
2007-01-23 22:24 ` Nathan Scott [this message]
2007-01-23 22:58 ` Chris Wedgwood
2007-01-23 16:58 ` Iustin Pop
-- strict thread matches above, loose matches on Subject: below --
2007-01-24 16:28 James Pearson
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=1169591069.18017.143.camel@edge \
--to=nscott@aconex.com \
--cc=cw@f00f.org \
--cc=grinapo@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox