All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Caleb O'Connell" <caleb@privacyassociation.org>
To: linux-btrfs@vger.kernel.org
Subject: advice for testing fileserver
Date: Tue, 11 Sep 2012 13:19:47 -0400	[thread overview]
Message-ID: <k2nrrj$voq$1@ger.gmane.org> (raw)

I'm building a test file server using samba 3.6 to see if BTRFS is a good 
fit.  I want to stress that this is a test setup for now.

I'm trying to get an idea of the sub-volume concept and how it relates to 
the LVM concept.  Trying to see what might be the best practice.

I was going to create one of two configs.
-----------------------------------------------------------------------------
##
option 1
sda1 -> /boot using ext4
sda2 is LV sysvg, this will include:
  lvroot -> / using ext4
  lvvar -> /var using ext4
  lvopt -> /opt using ext4
  lvhome -> /home using btrfs
  lvsrv -> /srv using btrfs

I could create sub-volumes in srv for each samba share.

##
option 2
sda1 -> /boot using ext4
sda2 is LV sysvg, this will include:
  lvroot -> / using ext4
  lvvar -> /var using ext4
  lvopt -> /opt using ext4
sda3 -> /home using btrfs
sda4 -> /srv using btrfs

both /home and /srv can create their own sub-volumes for each homedir and 
each share.
____________________________________________________________________________
Does BTRFS work fine within a LV?  Is there an advantage to keep BTRDS out 
or in a LV?  Does all this make no sense? and I really should just create 
one big BTRFS partition and only use sub-volumes?




                 reply	other threads:[~2012-09-11 17:25 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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='k2nrrj$voq$1@ger.gmane.org' \
    --to=caleb@privacyassociation.org \
    --cc=linux-btrfs@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.