From: Andrei Borzenkov <arvidjaar@gmail.com>
To: Toomas Soome <tsoome@me.com>
Cc: The development of GNU GRUB <grub-devel@gnu.org>
Subject: Re: [PATCH 5/5] zfs extensible_dataset and large_blocks feature support
Date: Sat, 30 May 2015 08:56:19 +0300 [thread overview]
Message-ID: <20150530085619.0e3f523f@opensuse.site> (raw)
In-Reply-To: <2FF20C30-47E0-4360-AA77-CF7EBFF582AB@me.com>
В Fri, 15 May 2015 10:50:59 +0300
Toomas Soome <tsoome@me.com> пишет:
>
> hi!
> so what is the status of this last feature pair? its the final bundle to get full support of modern openzfs to grub and since zfs on all major players (illumos/zol/freebsd) support this feature, its only question of time when someone will step on this missing piece;)
Committed with additional explanatory commit text scraped from this
discussion.
Thanks!
>
> rgds,
> toomas
>
> > On 04.05.2015, at 9:49, Toomas Soome <tsoome@me.com> wrote:
> >
> >
> >> On 04.05.2015, at 7:32, Andrei Borzenkov <arvidjaar@gmail.com> wrote:
> >>
> >> В Sun, 03 May 2015 22:47:40 +0300
> >> Toomas Soome <tsoome@me.com> пишет:
> >>
> >>>
> >>>> On 03.05.2015, at 22:23, Andrei Borzenkov <arvidjaar@gmail.com> wrote:
> >>>>
> >>>>>>
> >>>>>
> >>>>> they do implement read support extensible dataset… instead of fixed DMU types they dont specify type, making it possible to use fat zap objects from bonus area.
> >>>>>
> >>>>> reference commit:
> >>>>> https://github.com/illumos/illumos-gate/commit/2acef22db7808606888f8f92715629ff3ba555b9
> >>>>>
> >>>>
> >>>> OK; just to be sure - there are several remaining uses of
> >>>> DMU_OT_DSL_DATASET and DMU_OT_DSL_DIR; are these intentional?
> >>>
> >>>
> >>> they *should* be ok. at least browsing and loading files from datasets haven’t revealed other instances over the test time. but problem is, the cases of zapify (when “normal” structure is wrapped as zap object) I have seen, have been related to datasets using >128k recordsize, and its possible some cases may have been missed - the grub zfs code and real zfs code are not exactly easy to compare. at least so far I haven’t seen bugs related to this nor received any reports. the basic symptom can be either message about wrong type or “missing” directory entry in listing.
> >>>
> >>
> >>
> >> Can https://savannah.gnu.org/bugs/?44448 be somehow related?
> >
> > without grub debug=zfs its impossible to say - guessing there is not really helpful:) altho in general, feature check for label should generate error message if pool has enabled features not supported by version of grub used there.
> >
> > basically, my first suggestion to cases like that is to set debug=zfs in grub and ask user to provide that debug output.
> >
> > rgds,
> > toomas
> >
> >
>
prev parent reply other threads:[~2015-05-30 5:56 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-16 5:24 [PATCH 5/5] zfs extensible_dataset and large_blocks feature support Toomas Soome
2015-04-19 19:40 ` Andrei Borzenkov
2015-04-19 19:53 ` Toomas Soome
2015-04-20 3:40 ` Andrei Borzenkov
2015-04-20 5:41 ` Toomas Soome
2015-05-03 19:23 ` Andrei Borzenkov
2015-05-03 19:47 ` Toomas Soome
2015-05-04 4:32 ` Andrei Borzenkov
2015-05-04 6:49 ` Toomas Soome
2015-05-15 7:50 ` Toomas Soome
2015-05-30 5:56 ` Andrei Borzenkov [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=20150530085619.0e3f523f@opensuse.site \
--to=arvidjaar@gmail.com \
--cc=grub-devel@gnu.org \
--cc=tsoome@me.com \
/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).