►
From YouTube: Storiant
Description
No description was provided for this meeting.
If this is YOUR meeting, an easy way to fix this is to add a description to your video, wherever mtngs.io found it (probably YouTube).
A
My
name
is
mark
reese,
I'm
the
cto,
with
historian,
formerly
known
as
sage
cloud
that
you
may
have
heard
of
had
a
name
change
recently
for
reasons
I
won't
go
into
so
we're
building
cold
storage
systems
for
people
who
don't
want
to
store
their
data
in
clouds
and
would
rather
store
them
behind
their
own
firewalls.
A
The
systems
you
know:
cold
storage
is
kind
of
a
new
term
and
not
everybody's
familiar
with
it.
Probably
the
thing
you
may
be
most
familiar
with
is
amazon
glacier,
which
provides
oh
yeah.
It's
gonna
put
my
logo
out.
There
provides
cold
storage
in
the
cloud
and
I
would
say
that's
pretty
much
our
competitor
at
the
moment,
but
a
lot
of
companies
are
not
interested
in
storing
their
proprietary
data
in
a
cloud
at
any
cost,
and
so
we
saw
an
opportunity
to
build
systems
that
they
can
install
themselves.
A
A
Formerly
many
of
us
who
started
the
company
at
story
were
involved
in
a
company
called
carbonite
which
provides
consumer
service
to
back
up
in
the
cloud
to
back
up
your
pc
or
your
mac
into
the
cloud,
and
we
we
ran
our
own
data
centers
and
I
think
there
are
over
100
petabytes
of
storage
at
the
moment
at
carbonite,
and
so
we
learned
a
lot
of
lessons
about
the
mechanics
of
dealing
with
storage
and
how
painful
it
can
be
and
when
we
decided
to
move
along
from
carbonite
and
do
something
new,
we
thought
this
was
really
an
interesting
problem
to
attack,
because
it's
really
very
hard
to
run
big
storage
systems
reliably
for
a
long
time
and
carbonite.
A
A
So
when
we
started
story-
and
those
were
the
the
things
that
we
were
looking
for,
it
had
to
be
cheap
has
to
be
very
reliable
and
it
has
to
be
scalable
and
that's
what
we
set
out
to
do.
We
just
shipped
our
first
product,
it's
being
beta,
tested
by
a
bunch
of
customers
at
the
moment
and
we're
getting
a
lot
of
interest
in
the
market
we
use
opencfs.
For
for
mostly
the
reasons
that
you
know
I
outlined
from
our
carbonite
experience.
A
We
wanted
something
that
could
you
know
deal
with
silent
failures
of
the
disc,
do
with
all
this
kind
of
corruption
that
creeps
in
bit
rot
and
when
you're
in
the
petabyte
scale.
You
know
those
numbers
of
failures
with
all
the
zeros
behind
them
become
real.
I
mean
things
fail,
and
so
you
better
have
a
mechanism
to
deal
with
them,
and
so
zfs
was
really
the
best
system
out
there
on
the
market.
A
It
really
really
does
a
good
job,
we're
running
it
on
linux,
because
in
in
our
market,
that's
what
people
want
to
run,
and
so
it
was
a
bit
of
an
immature
port
at
the
beginning
and
the
guys
at
livermore
did
a
great
job
getting
it
going.
A
We
use
it
in
a
kind
of
limited
way,
so
it's
a
great
big
system
has
all
kinds
of
features
and
we
don't
use
a
lot
of
those
features.
So
I'm
not
saying
that
everything
works
perfectly
on
linux,
but
you
know
for
the
way
we
use
it,
which
is
really
for
the
core
usage.
It
works.
Fine.
We
don't
have
a
myriad
of
file
systems.
A
We
have
kind
of
one
file
system.
We
we're
talking
of
large
amounts
of
storage,
we're
putting
a
couple
of
petabytes
in
a
rack,
so
we're
dealing
with
it
in
it.
We
have
our
system
uses
an
object,
store
interface,
so
that
we
we
tend
to
be
dealing
with
it
in
a
big
scale.
It's
you
know
big
chunks
of
storage.
At
a
time,
but
for
that
it's
it's
working
very
well
and
that's
about
it.
Mark.
B
What's
the
largest
single
file
system
that
you
have.
A
Well,
this
the
single
file
systems,
we,
the
way
we
arrange
it.
We
have
a
bunch
of
different
pools
because
it's
cold
storage,
and
so
we
spin
all
the
discs
down
when
they're
not
being
accessed.
So
we
have
individual
pools
that
are
matched
to
a
raise
and
the
arrays
are
of
the
order
of
you
know
between
50
and
100
terabytes,
something
like
that.
So
each
each
one
is
it's
its
own
file
system.
B
A
But
now
we
looked
at
all
sorts
of
file
systems
at
carbonite
we
actually
wrote
our
own
file
system.
We
had
unique
problems
there
and
particularly
to
do
with
small
file
sizes,
which
nobody
does
a
great
job
on
to
be
honest,
but
we
had
had
that
experience
and
we
certainly
didn't
want
to
go
and
write
another
file
system,
and
so
we
did
look
for
everything
we
could
find,
but
for
reliability.
You
know
we
couldn't
find
anything
to
match
open,
cfs.