From: Vladimir Serbinenko <phcoder@gmail.com>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: [DISCUSSION] Journal playback
Date: Mon, 08 Aug 2005 14:27:27 +0200 [thread overview]
Message-ID: <42F74FAF.8020005@gmail.com> (raw)
In-Reply-To: <87fytkfy6l.fsf@student.han.nl>
Marco Gerards wrote:
>Vladimir Serbinenko <phcoder@gmail.com> writes:
>
>
>
>>I've seen that journal playback is one of TODO items. I think it's bad
>>idea because:
>>
>>1) It'll increase the size of FS modules. And fs modules are often embed
>>in core image. So their size is critical
>>
>>
>
>The size of a filesystem module is now about 4KB. We do not know yet
>how much the size will increase when journaling is possible.
>
>
>
>>2) It'll decrease safety because now GRUB doesn't write to FS and then
>>it'll be so the GRUB's bugs could damage FS.
>>3) It'll be impossible to use resume/resume2 because the fs environment
>>is not more the same as at the hibernation.
>>
>>
>
>The data should not be written to the filesystem. Instead the
>journal should be played back for the data that is read. I am not yet
>sure if it is possible, easy and fast enough. But I do think it is
>worthwhile to consider journaling support.
>
>
>
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
Vladimir
next prev parent reply other threads:[~2005-08-08 12:48 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 [this message]
2005-08-08 14:14 ` Marco Gerards
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=42F74FAF.8020005@gmail.com \
--to=phcoder@gmail.com \
--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.