From: Tamas Papp <tompos@martos.bme.hu>
To: Andrew Flerchinger <lorax3@gmail.com>, linux-btrfs@vger.kernel.org
Subject: Re: File server structure suggestion
Date: Thu, 10 Jul 2014 16:52:44 +0200 [thread overview]
Message-ID: <53BEA8BC.2000309@martos.bme.hu> (raw)
In-Reply-To: <CAGTBuzTWV2jVqy4uScevHbMi-kp4_TRdeR21ZoA3-yOtCXPA=g@mail.gmail.com>
On 07/10/2014 04:41 PM, Andrew Flerchinger wrote:
> what was going on. That sold me on the idea of data checksums, but I'd
> rather stay in linux than BSD, and I previously made use of online
> capacity expansion as needed, which ZFS doesn't support.
What do you mean by that?
What zfs doesn't support is reducing a pool.
tamas
next prev parent reply other threads:[~2014-07-10 14:52 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-10 14:41 File server structure suggestion Andrew Flerchinger
2014-07-10 14:52 ` Tamas Papp [this message]
2014-07-10 15:25 ` Andrew Flerchinger
2014-07-10 21:20 ` Duncan
2014-07-16 16:49 ` Kyle Gates
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=53BEA8BC.2000309@martos.bme.hu \
--to=tompos@martos.bme.hu \
--cc=linux-btrfs@vger.kernel.org \
--cc=lorax3@gmail.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).