public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Volker Armin Hemmann <volkerarmin@googlemail.com>
To: gentoo-user@lists.gentoo.org
Cc: Michael Hampicke <gentoo-user@hadt.biz>
Subject: Re: [gentoo-user] experiences with zfsonlinux?
Date: Mon, 31 Dec 2012 04:42:45 +0100	[thread overview]
Message-ID: <4217336.sd8MtAsg5n@localhost> (raw)
In-Reply-To: <50E04E42.3030005@hadt.biz>

Am Sonntag, 30. Dezember 2012, 15:22:58 schrieb Michael Hampicke:
> Am 30.12.2012 15:07, schrieb Volker Armin Hemmann:
> > Set both mountpoints as legacy and put them into fstab - I know I could
> > zfs
> > deal with that, but I feel more comfortable that way.
> 
> Howdy Volker,
> 
> that's a good idea. For some reason - with the latest sys-fs/zfs upgrade
> (0.6.0_rc13) - I found that both of my zfs file systems (single pool) do
> not get mounted at boot time automatically. This worked fine up until
> now. I'll look into that in the new year, right now, I'm on vacation :)

one thing that baffled me was when I set the mountpoint for zfstank/var - and 
it was gone.  ;) 

But seriously, setting up zfs was way easier than my first steps with mdraid + 
fitting a filesystem on it. It is different (just like office 2010 is easiert than 
2003 but people complain because it is different) but a lot easier. I hope it 
stays that way.

One thing that scares me: it is way too easy to throw away everything..

zpool history               
zsh: correct 'history' to '.history' [nyae]? n
History for 'zfstank':
2012-12-29.23:47:49 zpool create -f -o ashift=12 zfstank raidz ata-
Hitachi_HDS5C3020ALA632_ML4230FA17X6EK ata-
Hitachi_HDS5C3020ALA632_ML4230FA17X6HK ata-
Hitachi_HDS5C3020ALA632_ML4230FA17X7YK
2012-12-29.23:48:05 zfs create zfstank/var
2012-12-29.23:48:10 zfs create zfstank/data
2012-12-29.23:50:10 zfs set compression=on zfstank/var
2012-12-29.23:50:48 zfs set compression=on zfstank/data
2012-12-29.23:51:04 zfs set atime=off zfstank
2012-12-29.23:54:00 zfs set quota=100G zfstank/var
2012-12-30.00:04:16 zfs set mountpoint=/var zfstank/var
2012-12-30.00:08:00 zfs destroy zfstank/var
2012-12-30.00:08:35 zfs create -o quota=100G zfstank/var
2012-12-30.00:14:38 zfs set compression=on zfstank/var
2012-12-30.00:19:09 zfs set mountpoint=legacy zfstank/data
2012-12-30.05:55:17 zfs set mountpoint=legacy zfstank/var

compared with the hours of fiddling when I started using raid this was pretty 
much straight forward - and yes, I know, destroying var was not necessary, but 
at that point I just wanted to try it... as I said, way too easy to throw away 
everything. 

-- 
#163933


  reply	other threads:[~2012-12-31  3:44 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-12-28 17:52 [gentoo-user] experiences with zfsonlinux? Volker Armin Hemmann
2012-12-28 20:29 ` Stefan G. Weichinger
2012-12-28 23:21   ` Scott Ellis
2012-12-28 23:54     ` Volker Armin Hemmann
2012-12-30 14:07     ` Volker Armin Hemmann
2012-12-30 14:22       ` Michael Hampicke
2012-12-31  3:42         ` Volker Armin Hemmann [this message]
2012-12-31  7:07           ` Alan McKinnon
2012-12-31 13:27             ` Volker Armin Hemmann
2012-12-31 16:02           ` Scott Ellis

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=4217336.sd8MtAsg5n@localhost \
    --to=volkerarmin@googlemail.com \
    --cc=gentoo-user@hadt.biz \
    --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