From: "Vladimir 'φ-coder/phcoder' Serbinenko" <phcoder@gmail.com>
To: Jiro SEKIBA <jir@unicus.jp>,
The development of GRUB 2 <grub-devel@gnu.org>
Subject: NILFS2 in GRUB with blocksize=1024
Date: Wed, 25 Apr 2012 21:12:07 +0200 [thread overview]
Message-ID: <4F984C87.8050506@gmail.com> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1099 bytes --]
Hello, with the attached script grub-fstest fails completely with
blocksize=1024 and partially with 2048. Do you have any idea why? I
tried to debug and my finding is that grub_nilfs2_read_checkpoint reads
garbage. pptr makes sense but it points inside a file instead of to the
metadata. If I load the other superblock I'm able to read empty disk
(what's there before script starts putting files). The function calls
follow as:
grub_nilfs2_mount
grub_nilfs2_load_sb
grub_nilfs2_read_last_checkpoint
grub_nilfs2_read_checkpoint
grub_nilfs2_bmap_lookup
grub_nilfs2_direct_lookup
grub_nilfs2_dat_translate
grub_nilfs2_bmap_lookup
grub_nilfs2_btree_lookup
grub_nilfs2_btree_node_lookup
grub_nilfs2_btree_node_lookup
grub_nilfs2_btree_node_lookup
<---here it's already wrong--->
grub_nilfs2_read_inode
grub_nilfs2_bmap_lookup
grub_nilfs2_direct_lookup
grub_nilfs2_dat_translate
grub_nilfs2_bmap_lookup
grub_nilfs2_btree_lookup
grub_nilfs2_btree_node_lookup
grub_nilfs2_btree_node_lookup
grub_nilfs2_btree_node_lookup
--
Regards
Vladimir 'φ-coder/phcoder' Serbinenko
[-- Attachment #1.2: fstest.sh --]
[-- Type: application/x-shellscript, Size: 39977 bytes --]
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 294 bytes --]
next reply other threads:[~2012-04-25 19:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-25 19:12 Vladimir 'φ-coder/phcoder' Serbinenko [this message]
2012-04-26 0:36 ` NILFS2 in GRUB with blocksize=1024 Vladimir 'φ-coder/phcoder' Serbinenko
2012-04-26 9:19 ` Vladimir 'φ-coder/phcoder' Serbinenko
2012-04-26 10:40 ` Vladimir 'φ-coder/phcoder' Serbinenko
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=4F984C87.8050506@gmail.com \
--to=phcoder@gmail.com \
--cc=grub-devel@gnu.org \
--cc=jir@unicus.jp \
/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.