linux-ext4.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Theodore Ts'o <tytso@mit.edu>
To: Andreas Dilger <adilger@dilger.ca>
Cc: linux-ext4@vger.kernel.org, Andreas Dilger <andreas.dilger@intel.com>
Subject: Re: [PATCH 1/6] blkid: fix ZFS device detection
Date: Sun, 6 Mar 2016 18:10:25 -0500	[thread overview]
Message-ID: <20160306231025.GA30238@thunk.org> (raw)
In-Reply-To: <1457224716-72388-1-git-send-email-adilger@dilger.ca>

On Sat, Mar 05, 2016 at 05:38:31PM -0700, Andreas Dilger wrote:
> From: Andreas Dilger <andreas.dilger@intel.com>
> 
> While the main blkid functionality is in util-linux, there is still
> use for blkid on non-Linux platforms.
> 
> Fix the ZFS device detection by looking at multiple uberblocks to
> see if any are present, rather than looking for the ZFS boot block
> which is not always present.
> 
> There are slots for up to 128 uberblocks, but the first 4 are not
> written to disk on a newly-formatted filesystem, so check several
> of them at different offsets within the uberblock array.
> 
> Signed-off-by: Andreas Dilger <andreas.dilger@intel.com>

Thanks, applied.

					- Ted

      parent reply	other threads:[~2016-03-06 23:10 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-06  0:38 [PATCH 1/6] blkid: fix ZFS device detection Andreas Dilger
2016-03-06  0:38 ` [PATCH 2/6] debugfs: improve dump_mmp handling Andreas Dilger
2016-03-06 23:11   ` Theodore Ts'o
2016-03-06  0:38 ` [PATCH 3/6] misc: add missing declarations on maint Andreas Dilger
2016-03-06 23:12   ` Theodore Ts'o
2016-03-06  0:38 ` [PATCH 4/6] lsattr: treat inode generation as an unsigned int Andreas Dilger
2016-03-06 23:13   ` Theodore Ts'o
2016-03-06  0:38 ` [PATCH 5/6] findsuper: improve output if s_mkfs_time unset Andreas Dilger
2016-03-06 23:16   ` Theodore Ts'o
2016-03-06  0:38 ` [PATCH 6/6] debugfs: update to handle newer inode fields Andreas Dilger
2016-03-07  0:54   ` Theodore Ts'o
2016-03-06 23:10 ` Theodore Ts'o [this message]

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=20160306231025.GA30238@thunk.org \
    --to=tytso@mit.edu \
    --cc=adilger@dilger.ca \
    --cc=andreas.dilger@intel.com \
    --cc=linux-ext4@vger.kernel.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 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).