From: "Geir A. Myrestrand" <geir.myrestrand@falconstor.com>
To: xfs@oss.sgi.com
Cc: Peter Gervai <grinapo@gmail.com>
Subject: Re: how to sync / commit data to disk?
Date: Tue, 23 Jan 2007 10:58:15 -0500 [thread overview]
Message-ID: <45B63097.7020504@falconstor.com> (raw)
In-Reply-To: <d55656c10701230716x1ae7cf49kd8a854fd73429c4f@mail.gmail.com>
Peter Gervai wrote:
> Hello,
>
> [Tried to search archieves, found nothing, probably my keywords are bad.
> :-)]
>
> What is the recommended way to make sure that a file is written
> physically to the disk? (apart from the cache of the disk.)
>
> 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.
>
> My educated guess would be
> xfs_freeze -f
> sync
> xfs_freeze -u
>
> but I give a large chance to be wrong about it.
>
> Ideas?
>
> Please cc on me if possible. Thanks.
Call the sync before you freeze the file system, not after. You can't
write to the file system when it is frozen, so it makes no sense to call
sync after a freeze.
I don't think you have any control of whether the data is written
physically to the disk or is still in the disk(s) buffer, the buffer you
can flush is on the software side. Call sync and freeze.
--
Geir A. Myrestrand
next prev parent reply other threads:[~2007-01-23 16:40 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 [this message]
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
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=45B63097.7020504@falconstor.com \
--to=geir.myrestrand@falconstor.com \
--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