public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Pandu Poluan <pandu@poluan.info>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Safeguarding strategies against SSD data loss
Date: Tue, 28 Oct 2014 07:41:42 +0700	[thread overview]
Message-ID: <CAA2qdGXMSwZB75dpA-J5owJeP4hKJNK9szbDrN-5-_baH2vGPg@mail.gmail.com> (raw)
In-Reply-To: <CAGfcS_nFX0N7OmX0=oi4m_rFpJQ=AkJjeNz5RXLXT9eB8ofqEQ@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1441 bytes --]

On Oct 28, 2014 12:31 AM, "Rich Freeman" <rich0@gentoo.org> wrote:
>
> On Mon, Oct 27, 2014 at 12:52 PM, Pandu Poluan <pandu@poluan.info> wrote:
> >
> > ZoL (ZFS on Linux) nowadays is implemented using DKMS instead of FUSE,
thus
> > running in kernelspace, and (relatively) easier to put into an
initramfs.
>
> Sorry about that.  I should have known that, but for some reason I got
> that memory crossed in my brain...  :)
>
> > vdevs can grow, but they can't (yet) shrink.
>
> Can you point to any docs on that, including any limitations/etc?  The
> inability to expand raid-z the way you can do so with mdadm was one of
> the big things that has been keeping me away from zfs.  I understand
> that it isn't so important when you're dealing with large numbers of
> disks (backblaze's storage pods come to mind), but when you have only
> a few disks being able to manipulate them one at a time is very
> useful.  Growing is the more likely use case than shrinking.  Then
> again, at some point if you want to replace smaller drives with larger
> ones you might want a way to remove drives from a vdev.
>

First, you need to set your pool to "autoexpand=on".

Then, one by one, you offline a disk within the vdev and replace it with a
larger one. After all disks have been replaced, do a scrub, and ZFS will
automagically enlarge the vdev.

If you're not using whole disks as ZFS, then s/replace with larger/enlarge
the partition/.

Rgds,
--

[-- Attachment #2: Type: text/html, Size: 1859 bytes --]

  reply	other threads:[~2014-10-28  0:41 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-27  9:24 [gentoo-user] Safeguarding strategies against SSD data loss Mick
2014-10-27 10:30 ` Alec Ten Harmsel
2014-10-27 11:11 ` Alan McKinnon
2014-10-27 13:13   ` Rich Freeman
2014-10-27 15:15     ` [gentoo-user] " James
2014-10-27 15:23       ` Mick
2014-10-27 15:22     ` [gentoo-user] " Mick
2014-10-27 15:36       ` Rich Freeman
2014-10-27 16:52         ` Pandu Poluan
2014-10-27 17:26           ` Volker Armin Hemmann
2014-10-27 17:30           ` Rich Freeman
2014-10-28  0:41             ` Pandu Poluan [this message]
2014-10-28  1:13               ` Rich Freeman
2014-10-28  3:45           ` Tom H
2014-10-27 17:23         ` Volker Armin Hemmann
2014-10-27 17:37           ` Rich Freeman
2014-10-28  0:56             ` Pandu Poluan
2014-10-28  3:49             ` Tom H
2014-10-27 17:20       ` Volker Armin Hemmann
2014-10-27 17:17     ` Volker Armin Hemmann
2014-10-27 12:27 ` Philip Webb
2014-10-27 14:12   ` [gentoo-user] Safeguarding strategies against SSD data loss : PS Philip Webb
2014-10-27 15:16   ` [gentoo-user] Safeguarding strategies against SSD data loss Mick

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=CAA2qdGXMSwZB75dpA-J5owJeP4hKJNK9szbDrN-5-_baH2vGPg@mail.gmail.com \
    --to=pandu@poluan.info \
    --cc=gentoo-user@lists.gentoo.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