From: Marco Gerards <metgerards@student.han.nl>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: [DISCUSSION] Journal playback
Date: Mon, 08 Aug 2005 16:14:03 +0200 [thread overview]
Message-ID: <87wtmwbjo4.fsf@student.han.nl> (raw)
In-Reply-To: <42F74FAF.8020005@gmail.com> (Vladimir Serbinenko's message of "Mon, 08 Aug 2005 14:27:27 +0200")
Vladimir Serbinenko <phcoder@gmail.com> writes:
> It'll give for sure considerable amount of work but the question if
> it'll give real advantages? Journaling was made to keep *FS* from
> the corruption. *Not* the data. So even if data needed by GRUB is
> corrupted (that is not very probable because kernels, initrds and
> GRUB data) there is a high probability that journaling will simply
> remove this corrupted data. On the other hand it can perhaps create
> strange bugs and make maintnaining harde
Right, I know what journaling is used for. But this makes it possible
to boot from a corrupted filesystem that can not be used without
journaling support.
About how hard it is, we will see about it when we will work on it.
It is not an important feature; at least not to me. But it is
something we have to keep in mind because, unlike lilo, GRUB does
depend on the consistency of the metadata.
--
Marco
next prev parent reply other threads:[~2005-08-08 14:35 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-08 9:47 [DISCUSSION] Journal playback Vladimir Serbinenko
2005-08-08 11:34 ` Vincent Pelletier
2005-08-08 11:46 ` Marco Gerards
2005-08-08 12:27 ` Vladimir Serbinenko
2005-08-08 14:14 ` Marco Gerards [this message]
2005-08-08 14:54 ` Yoshinori K. Okuji
2005-08-08 14:49 ` Yoshinori K. Okuji
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=87wtmwbjo4.fsf@student.han.nl \
--to=metgerards@student.han.nl \
--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.