►
From YouTube: May 2021 OpenZFS Leadership Meeting
Description
At this month's meeting we discussed: new maintainers; vdev properties; userland zfs; FreeBSD summit; OSX port
meeting notes: https://docs.google.com/document/d/1w2jv2XVYFmBVvG1EGf-9A5HBVsjAYoLIFZAnWHhV-BM/edit#
A
All
right,
good
afternoon,
good
morning,
good
evening,
wherever
you
are
it's,
the
may,
2021
open,
zfs
leadership
meeting
have
a
bunch
of
things
on
the
topic
for
today,
I'm
going
to
kick
it
off
with
new
maintainers.
A
I
sent
an
email
about
this.
You
may
have
seen
it
but,
as
you
guys
probably
know,
brian
bellandorf
has
been
doing
like
almost
all
of
the
work
of
maintaining
the
the
prs
and
issues
in
opengfs
for
the
past.
I
don't
know
close
to
a
decade
now
and
as
the
project's
grown
we
have
you
know
more
and
more
volume
of
contributions
which
is
great
and
but
it's
it's
quite
a
workload
for
one
person
to
do
so.
We've
recruited
a
few
new
maintainers.
A
In
addition
to
myself,
who
I
have
not
done
a
lot
of
that
work
recently,
but
we
have
three
new
folks,
tony
nguyen
mark,
maybe
and
john
kennedy
who,
who
have
been
working
on
zfs
for
quite
some
time
and
they're
gonna,
be
helping
us
out
by
ushering
the
prs
through
the
review
process.
A
I'm
helping
to
get
reviewers
nag
reviewers
make
sure
that
everybody
knows
kind
of
what
the
next
steps
are
to
get
pull
requests
integrated
and
give
feedback
when
your
pull
requests
are
not
able
to
be
integrated
and
then
actually
doing
the
integration.
A
So
I
see
a
few
of
you
on
here
mark
and
tony
welcome
in
the
email
I
outlined
the
different
areas
so
we're
it's
not
like
round
robin
it's
kind
of
areas
of
the
code
base
that
are
assigned
to
each
each
maintainer,
so
you'll,
see
like
mark
is
responsible
for
all
of
the
core
generic
non-shared
kernel
code,
and
then
tony
has
most
of
the
like
platform
specific
in
other
kernel
code
as
well
as
documentation
and
some
of
the
other
user
land
commands
and
john.
A
Has
the
test
suite
and
a
couple
of
the
kind
of
core
user
line,
components
the
and
it's
consumers
like
the
z-form
zfs
commands
and
the
z-pool
and
the
it's
consumers
like
z-test
and
nzdb,
as
well
as
developer
tools
like
the
makefiles
packaging,
github
workflows
that
kind
of
stuff,
so
brian
and
I
and
tony
hudder
will
continue
on
as
maintainers.
A
Hopefully,
brian
will
be
able
to
remain
in
kind
of
a
catch-all,
consulting
role
and-
and
I
will
probably
continue
on
like
helping
out
other
folks
but
not
owning
areas.
Myself
and
tony
hutter
will
continue
managing
the
back
ports
and
doing
the
back
ports
yeah,
as
well
as
the
zed,
the
event
daemon
cool.
A
So
thanks
to
our
three
new
volunteers,
hopefully
you
will
find
it
rewarding
to
contribute
to
the
community
in
this
way
and
thanks
for
your
efforts,
so
you
probably
saw
a
few
of
those
integrations
happen.
I
think
just
yesterday
starting
but
look
out,
you
know.
Oh,
the
last
thing
I
should
mention
is
that
we're
using
the
assignee
of
each
pr
to
indicate
which
maintainer
is
responsible
for
it?
A
So
shortly
after
you
open
the
pr,
you
should
see
that
somebody
one
of
the
maintainers
was
assigned
to
it
and
they're
kind
of
your
point
of
contact
if
you're
like,
why
is
my
request
not
getting
integrated,
or
what
do
I
need
to
do
next?
How
do
I
find
people
to
review
this?
The
the
assigned
code
reviewer
there
in
github
is
a
person
that
you
should
ask
those
questions
of.
B
B
A
A
Yeah
concrete
thing
that
that
would
apply
to
today
would
be
like
a
shift.
For
example,
where
I
mean.
Maybe
this
is
not
a
good
idea,
but,
like
day
shift
is
specific
to
each
v
dev.
It
may
not
be
a
good
idea
to
have
different
ones
for
different.
You
know
normal
class
v
devs,
but
you
can
do
it
and
right
now
you
have
the
like
dash
o
a
shift
equals
whatever,
and
that
applies
to
at
least
all
the
normal
class
ones.
I
don't
know
if
it
applies
to
other
ones,.
A
Yeah
yeah
with
just
pool
properties,
so
it
might
be
helpful
to
think
about
like
how
would
you
want
to
create
a
pool
or
add
v
devs
while
specifying
the
shift
per
v
dev
right?
It.
C
D
A
A
little
tricky
in
terms
of
like
how
you
would
want
to
parse
the
command
line.
It
would
be
much
easier
if,
if,
like
you
had
to
add,
add
v
devs
one
at
a
time.
You
know
if
there
was
a
like
zip,
create
that
created
some
like
empty
v
dev
and
then
you
would
like
add
each
veto.
Sorry,
an
empty
pool
with
no
v
devs
and
then
afterwards,
like
add
one
video
at
a
time,
but
that's
not
how
it
works.
Today,
I
guess
we
could.
A
B
A
Especially
when
you
have
like
you
have
to
handle
both
like
properties
that
keep
that
are
set
on
a
top
level,
vita
versus
ones
that
are
on
leafs
yeah
and
you
might
have
both
or
neither
you
might
have
one
vita,
which
is
both
the
top
level
and
the
leaf.
So
that
seems
pretty
tricky.
So
I
mean
maybe
what.
E
A
E
B
E
B
Right
now,
most
of
the
properties
that
the
bdf
property
stuff
is
adding
are
read
only
or
whatever,
or
would
be
able
to
be
set
after
without
a
disadvantage.
But
at
some
point
you
could
see
it
being
different
like
even
I
don't
know
if
it
makes
sense,
but
controlling
the
number
of
meta,
slabs
or
the
size
of
the
meta
slabs
or
something
or
anything,
that's
create
time.
Only
like
that.
E
B
A
Yeah,
I
think
that
we
can
definitely
integrate
what
you
have
in
the
pr
without.
A
A
Cool
then
the
next
one
is
nice.
This
is
also
you
getting
sql
status
via
pool
properties
like
scrub,
progress
and
other
stuff.
B
Yeah
so
some
of
the
stuff
you
can
get
with
what's
in
the
zipl
or
the
vida
properties.
Pr
now
you
can
get
the
counters
like
the
checksum
errors
and
read,
write
errors
and
that
kind
of
thing
most
of
those
counters
you
can
get
as
properties.
B
But
you
know
getting
just
the
the
pool
status
other
than
online
or
degraded
is,
is
one
of
the
properties
of
the
pool,
but
that
you
know
the
scan,
progress
or
just
the
there's
the
action
line.
If
something
is
wrong
and
a
bunch
of
other
ones,
there's
no
way
to
extract
those
other
than
you
know
pursing
the
human
readables
equal
status.
B
I
looked
at
doing
it,
but
a
lot
of
the
logic
for
it
all
lives
in
the
user
space
side,
which
is
a
little
weird
to
do
with
properties
like
I
think
for
some
of
them.
You
know
we
can
pass
the
enum
or
whatever
value
as
the
property,
and
then
libsetfs
can
convert
that
into
the
string,
but
for
some
of
them
it
it
looks
a
little
harder
to
do.
Just
all
the
text
comes
from
either
the
z-pool
command
or
lib
zfs,
not
from
the
other
side
of
zfs.
A
B
Like
I
think,
specifically,
action,
errata
and
like
scan
and
one
two
others
are
the
ones
that
are
a
bit
hairier.
A
Yeah
I
mean
I
feel
like
action
especially
is
like
complicated
but
scan
and
those
related
ones,
I
think,
could
probably
be
made
machine
personable
pretty
straightforwardly.
I
mean
they
are.
Basically
all
those
numbers
are
just
coming
up
from
the
kernel
and,
like
I
wouldn't
bother
with
say
the
estimate,
but
just
which
is
calculated
in
user
land,
but
being
able
to
report
like
there
is
a
scan
in
progress
and
like
this
is
how
much
it's
done,
and
this
is
how
much
it
has
to
do.
G
G
I
think
it's
a
good
idea
and
then
you
can
carry
forward
as
a
property.
That's
more
or
less
stable.
A
Yeah,
so
I
think
it's
a
good
idea.
I
I
think
that
we
can
definitely
approach
it
incrementally,
and
I
look
forward
to
your
pr
ella.
A
Cool
the
next
thing
was
about.
A
I
think
that
get
all
is
already
extremely
verbose,
yeah
and
not
that
it
like
it's
clearly
not
useful
programmatically,
and
so
I
would
say,
like
pylon.
B
A
And
to
not
worry
about
that
too
much,
and
then
you
know,
I
think
that
we
should
kind
of
separately
address
the
problem
of
like
having
some
user-friendly
easy-to-read
output.
That's,
like
hey,
tell
me
about
this
thing
and
which
you
know
might
include
some
properties,
but
not
all
of
them
like
we
could.
A
Come
up
with
some
aliases
like
that
or
you
know,
come
up
some
new
sub
command,
that's
like
zfs
info
data
set
and
then
it's
like
a
full
screen
text.
Display
of
you
know
various
stuff
about
it.
You
know
I'm
just
making
stuff
up,
but
you
know
like
I
would
solve
that
problem
separately.
Then
then,
making
like
get
all
be
pretty
because
it's
clearly
not
as
it
stands
today.
A
Cool
so
may
may
yank.
Are
you
here
to
talk
about
uzland,
zfs.
H
A
A
Yeah,
apologies
yeah
I'd
love
to
hear
about
userland,
zfs
and
kind
of
where
you're
at
with
the
process
and
what
you
like.
What
what
you
know,
what
problem
this
solved
for
you
and
and
how
you
see,
integrating
with
the
rest
of
the
ecosystem.
H
H
So
we
disabled
this
file
system,
jfs
file
system
and
exported
this
zfs
volume
through
the
ice
casing,
so
that
iscsi
part
we
have
returned
and
they
have
also
added
support
for
the
application
and
the
rebuilding.
So
with
that,
actually
we
can
run
this
multiple
jfs
process
in
user
space,
which
provides
the
replication
and
also
the
rebuilding
if
any
replica
gets
out
or
if
you
want
to
add
any
new
replica.
So
that
way,
it
adds
support
for
the
multi-tenancy
environment.
A
Cool,
so
you
mentioned
the
exp
exports
over
iscsi.
Is
that
part
of
how
like
how
did
what
I
schedule
server
does
that
use
and
how
does
that
work.
H
H
No
there's
vision
some
other
cases
service,
I
think,
but
we
have
added
this
replication
and
rebuilding
module
into
that
skg,
which
provides
basically
which
access
the
api
is
exported
from
the
database,
so
that
is
on
actually
tcp.
A
A
So
I
I
guess
a
couple
of
questions
I
had
were
like.
Do
you
have
any
performance
measurements
like
with
this
iscsi
server
compared
to
zfs,
with
the
in
kernel
in
kernel,
zfs
within
kernel,
skz
server,.
A
Yeah,
I
think
that
would
I
think
that
people
probably
have
a
opinion
on
what
on
the
perform.
They
probably
have
a
preconceived
notion
on
the
performance
of
user
land
file
systems
and
zfs
due
to
experience
with
fuse,
and
if,
if
we
can
help
to
dispel
that
I
mean
if
it
is
faster,
then
that
would
definitely
be
helpful
to
you
know:
inform
people
that
hey
this
is.
This
is
not
just
like
a
toy.
It
can
be
used
for
production
and
get
good
get
performance.
A
That's
you
know
in
the
same
ballpark
as
the
internalized
scuzzy
server.
That
would
be.
You
know
that
would
really
be
helpful
in
in
terms
of
showing
that
this
is
useful
and
valuable.
A
Aside
from
that,
I
guess
what's
the
status
like
are
you,
I
saw
you
open
the
blue
request,
it's
like
not
huge.
It's
only
about
a
little
more
than
a
thousand
lines
of
code.
Would
you
is
this
ready
for
review?
Is
this
like
the
whole
thing,
or
are
we
waiting
for
additional
changes
that
you're
planning
to
make.
H
Yeah,
so
actually
initially,
I
have
added
only
few
iota,
mainly
I
think,
create
and
the
list,
so
we
are
already
supporting
the
director
also
basically
creating
the
snapshot
and
send
our
jfs
and
receive
so.
H
H
F
H
A
Cool
and
it
you
mentioned
that,
there's
changes
required
to
the
useless
iscsi
server
have
have
you
engaged
with
whatever
the
community
is
that
maintains
that
to
see
you
know
if
they
would
accept
those
changes
upstream,
because
that's
kind
of
you
know
for
folks
who
are
not.
You
know
you
using
in
your
product.
It
would
be
nice
if
there
was
like
a
stan.
You
know
we
need
some
way
to
actually
use
this.
A
Otherwise,
it's
kind
of
similar
to
z-test
or
zdb,
in
that
it's
interesting
for
development
purposes
or
for
playing
around
with,
but
you
kind
of
need
to
hook
it
up
with
something
to
be
able
to
actually
consume
that
in
production
or
testing
environments.
A
Good
idea,
yeah,
hopefully
they
use
github
as
well,
and
you
can
kind
of
link
the
you
know
point
each
pull
request
at
the
other
one
so
that
we
can
keep
track
of
how
they're
how
that's
doing
as.
D
A
D
A
All
right
so
mark
was
assigned
as
the
maintainer
for
this.
So
there's
a
lot
of
kernel
stuff
here
yeah,
so
I
don't
know
if
mark.
If
you
have
any
thoughts
on
code
reviewers,
if
not,
then
we
can,
I
guess,
work
together
to
try
and
find
folks
yeah.
D
A
Yeah
I
mean
I'd,
be
happy
to
take
a
look
at
it.
F
A
A
And
yeah
I
mean,
I
think
that
I
would
love
to
see
this
idea
of
userland
zfs
become
more
useful
for
more
use
cases,
I'm
also
interested
in
portability
of
the
userland
zfs.
Like
I
I'm
assuming
that
you're
just
running
this
on
z
on
linux,
it
would
be
really
cool
if
we
could,
if
we
could,
you
know
if
we're
only
using
like
posix
interfaces,
then
in
theory
it'll
work
on
any
unix
which
would
be
really
cool.
A
I'm
not
sure
if
that's
true
of
even
like
the
you
know
lib
spl
stuff
today,
but
it
should
at
least
be
a
lot
easier
to
report
than
the
kernel
part.
A
Cool
were
there
other
things
that
you
wanted
to
discuss
about
this.
H
That
was
also
the
rest
of
the
participle.
I
will
edit
in
using,
like
maybe
separate
pr
or
in
this
pr.
H
A
Integrated
and
you
know,
if
that,
if
we
decide
yeah,
we
do
want
to
have
more
actuals,
then
then
it
would
need
to
be
part
of
this
pr.
A
I
think
we
need
to
figure
out
like
it
sounds
like
you
know,
integrating
it
with
the
iscsi
server
nice,
because
the
server
is
not
something.
That's
you
know
part
of
our
code
base.
Obviously,
so
we
need
to
figure
out
like
what
that
is,
how
universal
it
is,
or
would
we
integrate
this
and
kind
of
be
like
if
you
want
to
use
this,
you
have
to
be
using
this
other.
A
B
Hacky
way,
I
think
one
thing
we
talked
about
a
couple
years
ago
me
you
and
paul
dodeck
was
being
able
to
do
send
receives
in
user
space
for
even
just
for
the
to
improve
the
send
receive
tests,
and
that
might
be
a
relatively
straightforward
thing
and
something
that
wouldn't
be
too
complicated
for
the
user
space
one
because
it's
mostly
just
you
know,
doing
the
zfs
bits
and
reading
or
writing
to
a
file.
Descriptor.
A
Yeah,
that's
that
might
be
a
good
minimum.
A
H
So
we
are
just
exposing
the
api
through
the
tcp,
so
if
the
changes
are
in
skz
or
nfs,
then
we
can
access
it,
but
yeah.
We
need
to
have
some
code.
There.
A
Yeah,
okay,
so,
like
you,
have
your
own
protocol
for
reading
and
writing
z
vols
that
the
iscsi
server
talks
to
right.
Yes,
yeah,
okay!
So
then
I
mean,
if
that's
going
to
be
integrated,
then
we
would
need
some
way
of
testing
that
either
with
a
dependency
on
this
external
isolde
server
or
with
you
know,
some
kind
of
test
programs.
That
would
talk
the
protocol
that
that
you've
invented.
H
Yes,
so
we
have
actually
written
sometimes
dummy
client
which
basically
like
send
this
protocol,
send
this
up
code
or
rewrite
snapshot.
So
that's
where
we
are
testing
it.
A
Cool
yeah.
That
would
be
great,
I
mean
I
think,
that
it
probably
wouldn't
be
too
hard
to
actually
hook
that
up
with
the
there's
seraphim.
You
might
remember
what
the
name
of
this
thing
is,
but
the
you
know
on
linux,
there's
something
like.
Oh
it's
there's.
One
of
them
is
called
views,
buse,
that's
like
block
driver
and
user
space.
A
It
lets
you
basically
implement
like
a
volume
that
shows
up
in
slash
dev,
but
it's
handled
by
a
user
space
process
so
like
it,
probably
wouldn't
be
that
hard
to
get
that
wired
up
to
you
know
a
client
for
your
user
land
zfs.
I
One
other
throw
in
there's
also
qmu
mbd,
I
think
that's
another
protocol.
That
is
basically
allowing
the
like
the
kernel,
spx
protocol
to
a
user
space
daemon,
and
I
think
it's
fairly
popular
in
other
systems.
I
A
A
We
need
reviewers
to
review
what
the
code
that's
already
posted,
and
then
we
want
to
get
just
a
little
bit
more
info
from
you
about
like
how
how
we
can
test
this
and
potentially
hooking
it
up
with
you
know,
with
a
internal
like
a
block
device
driver
mechanism.
A
Cool
anything
else
on
this
subject.
C
F
G
Opening
and
and
then
the
iscsi
targets
they're
using
is
also
user
land.
In
fact,
if
I'm
not
mistaken,
mike
it's
written
in
go
and
runs
in
a
container,
so
it
should
be
nicely
portable
as
well.
A
G
But
yeah,
I
I
think
I'm
happy
to
see
this
come
in,
so
it
would
be
very
useful
for
especially
for
containerized
people.
A
Yeah
yeah,
I
agree.
My
impression
was
that
kind
of
that
was
that,
like
I
scheduled
servers
or
are
one
of
those
things
that
sounds
simple
like
you're
just
you
know,
reading
writing
blocks
but
in
reality
is
hilariously
complicated.
A
A
It
might
you
know
it
might
only
be
like
a
couple
hundred
lines
of
code
to
get
to
to
hook
it
up
with
the
existing
like
buse
driver,
that's
in
the
kernel
already
to
be
able
to
make
that
available
in
slash
dev,
and
then
that
enables
a
lot
of
testing.
G
A
F
One
thing
I
came
across
when
I
was
playing
around
with
this
before
was
like:
what
do
you
do
for
tuna
bowls
and,
like
case
stats,
and
things
like
that
procfs?
How
do
you
mimic
proctofess
in
in
user
land.
A
Yeah,
I
think
that
to
make
this
like
a
first
class,
you
know
like
another,
basically
we're
talking
about
making
this
another
platform.
A
That
is
another
open,
zfs
platform
right
in
addition
to
linux
and
previoust,
I
think
we
would
want
to
see
kind
of
similar
at
least
a
plan
for
getting
to
similar
level
of
functionality,
including
like
support
for
tunables
and
observability,
like
for
example.
Well,
I
guess
things
like
a
lot
of
that.
Stuff
is
just
through
iactal.
So
as
long
as
you
implement
all
the
actuals,
then
things
like
xepo
xepo
iostat
use
the
iactals,
so
that
might
be
sufficient.
A
A
Is
there
is
a
very
rudimentary
way
to
set
tunables
in
in
user
land
that
I
think
zdb
or
z
test
has
like
a
dash
o
and
then
it
basically
like
sets.
It
uses
like
the
runtime
linker,
to
look
up
the
symbol
with
that
name
and
then
sets
it.
So
it's
like
very
janky,
but
it's
kind
of
analogous
to
what
we
have
on
had
or
had
on
solaris,
which
is
like
you
can
use
the
debugger
to
book
values
into
global
variables.
J
While
working
on
this,
I
think
we
should
also
try
to
keep
in
mind
like
how
we
can
build
up
this
functionality
to
something
like
eventually,
maybe
a
full
fuse
file
system
or
or
that
kind
of
thing,
just
as
we
go
lay
the
groundwork
we
might
need
for
that.
A
Yeah
yeah,
I
totally
agree,
and
I
realize
that
we're
you
know
we're
asking
for
some
stuff
that
you
haven't
implemented.
A
I
think
some
of
that
is
probably
pretty
straightforward
to
do,
but
we
may
you
know,
I
think,
there's
probably
some
excitement
about
this
from
some
quarters,
at
least
for
me
for
sure,
and
so
maybe
we
can
recruit
some
people.
You
know
additional
people
to
help
out
on
implementing
some
of
this.
A
So
I
guess
if
people
are
interested,
then
you
know,
let's
coordinate
on
the
pr,
and
we
can
work
on
kind
of
enumerating
these
things
that
are
still
to
do
or
to
implement,
and
then,
if
folks
are,
if
other
folks
are
interested,
it
would
be
super
helpful
if
you
want
to
pick
those
up.
A
All
right,
so
next
alec
you
want
to
talk
about
the
corrective
zfs
receive.
C
Yes,
I
mentioned
at
the
last
leadership
meeting
and
I've
been
trying
to
drum
up
some
interest
in
reviewing
this
since
then,
and
we
figured
out
the
problem
with
the
freebsd
test.
That
was
failing.
So
it's
ready
for
review
again,
so
I'm
just
trying
to
get
some
reviewers
and
maybe,
in
light
of
the
stuff
you
announced
in
the
beginning
of
this
call,
we
can
figure
out.
Who
should
be
this?
I
need
to
this
and
the
point
of
contact
that
I
should
be
bugging.
A
Yeah,
I
only
said
the
assignee
on
things
that
had
been
submitted
this
year.
This
calendar
year,
which
I'm
not
yours,
may
not
have
fallen
into
that,
but
I
think
mark
would
be
the
the
person
yeah
there's
substantial
kernel
components
here,
I'm
just
looking
it
up.
A
Well,
looking
up
the
pr
cool,
yeah,
wow
2019,
I'm
going
to
link
it
to
it
in
the
meeting
doc.
A
Looks
like
several
people
have
commented
on
that
already
so
mark
get
your
reminder:
emails
ready
to
send
to
those
folks,
oh
yeah,.
A
Cool
and
then
looks
like
the
last
thing
that
we
have
on
the
agenda
is
the
blake
3
checksum
from
tino?
I'm
not
sure.
Are
you
on
here.
K
A
Cool
thanks,
we'll
we'll
put
you
on
the
jennifer
sas
update
for
the
next
one
or
we'll
look
for
your
pr
even
better.
A
Cool,
that's
all
the
things
that
we
had
on
the
agenda.
I
will
mention
one
more
thing,
which
is
there's
a
freebsd
developer
summit,
which
is
going
to
be
in
two
weeks
june,
9th
through
11th.
A
It's
online.
I
think
it's
on
zoom
and
it's
free
to
attend
and
I'll.
Be
I'm
going
to
be
giving
a
talk
on
friday
that
friday,
the
11th
about
raids,
the
expansion
hopefully
featuring
at
least
announcements
that
might
be
interesting
to
developers,
if
not
end,
users
of
redzig's
expansion,
hoping
to
have
the
final
pr
out
by
then.
D
B
A
B
It
I
don't
think
so.
There's
one
talk
on
thursday
about
a
kind
of
recorder
for
our
storage
subsystem,
cam,
that
you
know
not
really
zfs,
but
if
you're
into
storage
and
finding
out
what
happened
to
your
storage
or
whatever.
That
might
be
interesting,
and
then
the
continuous
integration,
brainstorming
and
planning
might
be
of
interest
to
some
people
figuring
out
how
to
improve
previously
integration
with
open
zfsci
and
so
on.
B
B
A
Okay,
well,
that's
the
end
of
the
scheduled
agenda.
What
other
questions
are
comments?
Do
folks
have
or
things
they
want
to
solicit
reviews
or
other
work
on.
B
Of
jails
or
zones,
but
for
linux
containers
and
so
we'll
definitely
be
interested
in
testers
and
reviewers.
For
that
cool.
B
And
I
just
reached
out
to
mark,
but
if
anybody
we're
also
looking
to
finish
reviewing
and
land
the
forced
export
stuff,
I
think
we
have
the
last
failing
test
sorted.
Finally,
and
that
will
be
handy
if
encountered
a
couple
of
people
in
chat
over
the
last
couple
of
months,
who
would
have
benefited
from
being
able
to?
You
know,
force
export
the
the
pool
that
was
on
the
usb
stick,
that
the
cat
stole
or
whatever
things
of
that
nature.
A
A
All
right,
so
it's
currently
we
have
the
work
in
progress
label
on
that
is
that
no
longer
accurate,
you're
yeah.
A
B
A
Cool
other
questions,
comments.
A
Cool,
well,
I
I
suspect
it
must
be
summer
now
because,
like
the
view
out
of
jorgen's
window
looks
almost
the
same
as
mine,
which
is
like
it's
like:
it's
not
the
sun
isn't
rising.
It
looks
like
it's
daytime
there.
It's
also
daytime
here,
I'm
sure
it's
like
still
really
early
in
the
morning,
but.
A
Nice
cool
well,
the
the
next
meeting.
We
probably
will
not
see
your
sunny
window
because
the
next
meeting,
I
think,
is
the
earlier
time.
L
Actually
well,
I'm
here
since
we've
been
working
fairly
hard
on
the
mac
version
and
we
had
to
re-push
the
pr
again
because
we
and
we're
at
the
stage
where
we're
pretty
happy
with
it,
it
you
know,
pretends
to
work
even
on
the
m1,
which
is
quite
surprising.
So
now
we're
kinda.
L
A
That's
great,
I'm
super
impressed.
What
did
we
figure
out
as
far
as
automated
testing
for
this?
For
for.
L
We
run
the
zfs
tester
thing
that
you
guys
do
we're
only
up
to
71
or
so
pass
right,
but
we're
getting
there.
There's
there's
a
lot
of
fiddly
things
with
the
testing
because
it
yeah.
A
L
L
But
we've
been
using
appvayer,
which
has
been
okay.
It
has
a
90
minute
limit,
which
is
obviously
not
good
enough
for
a
full
test
run,
but
I
believe
amazon
has
max
yeah.
L
J
L
With
the
only
concern
is
the
disabling
sip,
you
know
the
security
protection
thing
or
finding
a
way
of
signed
code
signing
it
before
you
load
it,
which
I'm
not
sure
you
want
to
do
that.
A
Infrastructural
challenges
that
we'll
want
to
figure
out.
L
A
Yeah-
and
you
know
we
would
like
to
have
that
like,
if
that's
you
know
cloud
servers
or
whatever,
like
you
know,
the
project
should
be
the
open.
Zfs
project
should
be,
you
know,
running
and
paying
for
those,
rather
than
it
coming
out
of
your
pocket
or
you
know.
Oh,
you
know.
B
One
other
thing
was:
somebody
found
a
problem
with
the
zed
standard.
The
way
the
the
little
header
we
store
is
stored
on
big
endian,
so
spark
and
power
pc.
D
B
Yeah,
the
the
user
ping
me
on
irc
and
I
was
like
oh
yeah-
that
might
be
an
issue.
I
think
it
was
the
way
we
yeah.
I.
B
Yeah,
the
layout
of
the
the
structure
we
use
to
store
the
version
of
zed
standard
and
the
level
together
in
one
32-bit
number
gets
messed
up
because
of
the
indian-ness.
A
Solution,
yeah,
I'm
guessing
that
we're
gonna
probably
choose
to
if
we
have
to
just
break
big
endian
z
standard.
Does
that
like
make
it
make
it
read
and
write
stuff
using
the
way
that
we're
doing
on
little
endian
yeah?
So
maybe
that's
pretty
sure,
and
it.
B
I
think
the
right
thing
to
do
probably
is
just
instead
of
what
the
the
if
deaths
they
have
here
is
just
make
a
macro
that
decodes
it
properly
and
use
that
for
accessing
it.
Instead
of
the
struct
we
had
been
using
because
the
struct
is
the
wrong
way
around
on
the
opposite,
endian,
but
yeah,
I
think
we
should
be
able
to
just
make
it
always
be
the
way
it
is
now
and
not
like.
We
did
the
right
thing
and
wrote
it
to
the
disc
forced
to
be
in
big
endian.
It's
just
when
we
were.
B
B
A
Yeah,
I'm
just
taking
a
quick
look
at
the
well
I'll
give
the
feedback
on
the
pr
it
looks
like
there's
some
some
introducing
code-
that's
already
there
for
like
by
swapping
and
stuff.
So
we
can
simplify
that,
but
it'll
be
good
to
have
this
fixed.