From: Andreas Dilger <adilger@sun.com>
To: Eric Sandeen <sandeen@redhat.com>
Cc: "Ricardo M. Correia" <Ricardo.M.Correia@sun.com>,
"Theodore Ts'o" <tytso@mit.edu>,
linux-ext4@vger.kernel.org, Karel Zak <kzak@redhat.com>
Subject: Re: [PATCH e2fsprogs] Add ZFS detection to libblkid
Date: Mon, 06 Apr 2009 00:25:02 -0600 [thread overview]
Message-ID: <20090406062502.GE3199@webber.adilger.int> (raw)
In-Reply-To: <49D7D537.50502@redhat.com>
On Apr 04, 2009 16:46 -0500, Eric Sandeen wrote:
> Andreas Dilger wrote:
> > On Apr 04, 2009 08:04 -0500, Eric Sandeen wrote:
> >> And from another report, another user's zfs partition:
> >>
> >> # hexdump -C first_400K | grep "0c b1 07 b0 f5 02 00 00"
> >> # hexdump -C first_400K | grep "00 00 02 f5 b0 07 b1 0c"
> >> # hexdump -C first_400K | grep "0c b1 ba 00"
> >> 00015e30 30 e8 ff ff 85 c0 5b 75 48 8b 06 35 0c b1 ba 00
> >>
> >> Should we be looking for 0x00babloc at offset 00015e30?
> >
> > In probe.c I see the magic (that I've been assuming is correct, because
> > it isn't really that easy to read):
> >
> > { "zfs", 8, 0, 8, "\0\0\x02\xf5\xb0\x07\xb1\x0c", probe_zfs },
> > { "zfs", 8, 0, 8, "\x0c\xb1\x07\xb0\xf5\x02\0\0", probe_zfs },
> > { "zfs", 264, 0, 8, "\0\0\x02\xf5\xb0\x07\xb1\x0c", probe_zfs },
> > { "zfs", 264, 0, 8, "\x0c\xb1\x07\xb0\xf5\x02\0\0", probe_zfs },
>
> Yep and that's different from the patch you originally submitted, Andreas...
>
> > but looking at this I have no idea what this magic value is supposed
> > to represent, from reading the ondiskformat0822.pdf (ZFS spec) document.
>
> VDEV_BOOT_MAGIC ...
>
> 333 /* ZFS boot block */
> 334 #define VDEV_BOOT_MAGIC 0x2f5b007b10cULL
>
> but I can't find much in that spec about where it's supposed to be, at
> least from a very quick skim.
According to ondiskformat0822.pdf this is supposed to be at an 8kB
offset in each of the 4 per-disk labels, but it isn't clear that this
will be in every ZFS filesystem:
Section 1.3.2: Boot Block Header
The boot block header is an 8K structure that is reserved for
future use. The contents of this block will be described in a
future appendix of this paper.
so I'd prefer to just stick with the überblock magic, which should
be present in all versions of ZFS.
> I'll let you IBM er... SUN guys sort it out ;)
I'll defer to Ricardo, he is the ZFS expert.
Cheers, Andreas
--
Andreas Dilger
Sr. Staff Engineer, Lustre Group
Sun Microsystems of Canada, Inc.
--
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2009-04-06 6:25 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-30 18:20 [PATCH e2fsprogs] Add ZFS detection to libblkid Ricardo M. Correia
2008-06-02 7:41 ` Karel Zak
2008-06-02 15:03 ` Ricardo M. Correia
[not found] ` <1212418863.7337.34.camel@localhost>
2008-06-02 20:58 ` Karel Zak
2008-06-02 21:38 ` Andreas Dilger
2008-06-02 22:31 ` Karel Zak
2008-06-02 23:11 ` Andreas Dilger
2008-06-03 0:05 ` Theodore Tso
2008-06-03 1:11 ` Theodore Tso
2009-04-04 2:39 ` Eric Sandeen
2009-04-04 13:04 ` Eric Sandeen
2009-04-04 21:25 ` Andreas Dilger
2009-04-04 21:46 ` Eric Sandeen
2009-04-06 6:25 ` Andreas Dilger [this message]
2009-04-06 19:22 ` Ricardo M. Correia
2009-04-06 20:13 ` Eric Sandeen
2009-04-13 19:18 ` Ricardo M. Correia
2009-04-13 19:27 ` Eric Sandeen
2009-04-06 20:35 ` Karel Zak
2009-04-07 7:40 ` Andreas Dilger
2009-04-13 19:29 ` Ricardo M. Correia
2009-04-17 9:51 ` Karel Zak
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=20090406062502.GE3199@webber.adilger.int \
--to=adilger@sun.com \
--cc=Ricardo.M.Correia@sun.com \
--cc=kzak@redhat.com \
--cc=linux-ext4@vger.kernel.org \
--cc=sandeen@redhat.com \
--cc=tytso@mit.edu \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).