From: "Vladimir 'φ-coder/phcoder' Serbinenko" <phcoder@gmail.com>
To: The development of GNU GRUB <grub-devel@gnu.org>
Subject: Re: [PATCHv3] a new filesystem module for nilfs2
Date: Sat, 24 Apr 2010 22:12:52 +0200 [thread overview]
Message-ID: <4BD350C4.60501@gmail.com> (raw)
In-Reply-To: <87ochh83jw.wl%jir@sekiba.com>
[-- Attachment #1: Type: text/plain, Size: 1354 bytes --]
Committed. One question:
+ .reserved_first_sector = 1,
This line claims that overwriting first sector of nilfs won't destroy any data or metadata. Is it so?
Jiro SEKIBA wrote:
> Hi,
>
> Thank you very much for the comments!
> I revised the patch to reflect the comments.
>
>
>> + {
>> + grub_error(GRUB_ERR_BAD_FS,"btree corruption\n");
>> + return -1;
>> + }
>> What do you think about possible fallback to iterate over all nodes in case of fs corruption?
>>
>
> The case that btree is corrupted, it's very hard to take any action to recover
> because it is not possible to distinguish which block has meta data
> or which block has data without btree information.
>
> nilfs2 has ability to mount old checkpoint by specifying checkpoint number.
> So using old checkpoint is one of the possible fallback if all the blocks
> belonging to the old checkpoint is healthy. But it requires some more work.
>
> thanks,
>
> regards
>
> ------------------------------------------------------------------------
>
>
> ------------------------------------------------------------------------
>
> _______________________________________________
> Grub-devel mailing list
> Grub-devel@gnu.org
> http://lists.gnu.org/mailman/listinfo/grub-devel
--
Regards
Vladimir 'φ-coder/phcoder' Serbinenko
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 293 bytes --]
next prev parent reply other threads:[~2010-04-24 20:13 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-12 15:44 [PATCHv3] a new filesystem module for nilfs2 Jiro SEKIBA
2010-04-15 16:22 ` Vladimir 'φ-coder/phcoder' Serbinenko
2010-04-18 10:20 ` Jiro SEKIBA
2010-04-24 20:12 ` Vladimir 'φ-coder/phcoder' Serbinenko [this message]
2010-04-26 1:42 ` Jiro SEKIBA
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=4BD350C4.60501@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.