From: Pavel Roskin <proski@gnu.org>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: Some concern about the journal support
Date: Fri, 13 Jun 2008 11:55:59 -0400 [thread overview]
Message-ID: <1213372559.29669.14.camel@dv> (raw)
In-Reply-To: <ca0f59980806130205g1d54b349o5e110ba6ab57bb13@mail.gmail.com>
On Fri, 2008-06-13 at 17:05 +0800, Bean wrote:
> Hi,
>
> I think we need to disable journal sometimes. Tools like grub-setup
> and grub-install is run in an active system, that means sectors could
> easily end up in the journal. However, journal is a temperately
> buffer, space can be reused after a while. In this case, we should
> bypass the journal and access the underlying file system directly.
> Perhaps we can use a variable like no_journal to control the journal
> support, any suggestions ?
If we are going to hardcode block locations somewhere, hardcoding a
journal location is a serious bug. It will be overwritten.
If we are just reading from a live filesystem, there is no 100% correct
solution, but avoiding the journal seems safer to me. We load the
mappings once, but we read from the journal when the need arises. The
journal can be overwritten by background activity that the administrator
doesn't control. If we ignore the journal, inconsistencies would
normally arise only if any files used by grub are modified in the
meantime. Those should be owned by root, and no reasonable
administrator would touch them while grub-install is running.
We still want journal support for testing purposes, so perhaps
grub-fstest should have a switch to use the journal.
--
Regards,
Pavel Roskin
next prev parent reply other threads:[~2008-06-13 15:56 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-13 9:05 Some concern about the journal support Bean
2008-06-13 10:01 ` Bean
2008-06-13 12:14 ` Bean
2008-06-13 15:55 ` Pavel Roskin [this message]
2008-06-13 17:05 ` Bean
2008-06-13 19:45 ` Isaac Dupree
2008-06-13 20:40 ` Pavel Roskin
2008-06-13 21:49 ` Isaac Dupree
2008-06-13 22:06 ` Pavel Roskin
2008-06-14 3:32 ` Bean
2008-06-14 4:11 ` Bean
2008-06-13 20:14 ` Pavel Roskin
2008-06-14 11:43 ` Robert Millan
2008-06-14 16:17 ` Bean
2008-06-14 17:32 ` Bean
2008-06-14 18:06 ` Robert Millan
2008-06-14 18:29 ` Bean
2008-06-14 18:48 ` Robert Millan
2008-06-14 18:14 ` Javier Martín
2008-06-16 1:27 ` Pavel Roskin
2008-06-16 19:02 ` Bean
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=1213372559.29669.14.camel@dv \
--to=proski@gnu.org \
--cc=grub-devel@gnu.org \
/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.