linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jim <jim@webstarts.com>
To: linux-btrfs <linux-btrfs@vger.kernel.org>
Subject: delete disk proceedure
Date: Tue, 05 Jun 2012 10:38:11 -0400	[thread overview]
Message-ID: <4FCE19D3.4090908@webstarts.com> (raw)

Good morning btrfs list,
I had written about 2 weeks ago about using extra btrfs space in an nfs 
file system setup.  Nfs seems to export the files but the mounts don't 
work on older machines without btrfs kernels.  So I am down to deleting 
several drives from btrfs to setup a standard raid 1 array for storage 
and export via nfs.  My system stats are:
[root@advanced ~]# df -h
Filesystem            Size  Used Avail Use% Mounted on
/dev/sdm2             196G   50G  137G  27% /
tmpfs                  16G     0   16G   0% /dev/shm
/dev/sdm1             2.0G  141M  1.8G   8% /boot
/dev/sdm5             1.2T   20G  1.1T   2% /var
10.2.0.40:/data/sites
                       2.6T  2.4T  155G  94% /nfs1/data/sites
10.2.0.42:/data/sites
                       2.6T  2.2T  328G  87% /nfs2/data/sites
/dev/sda               11T  4.9T  6.0T  46% /btrfs
[root@advanced ~]# btrfs fi show
failed to read /dev/sr0
Label: none  uuid: c21f1221-a224-4ba4-92e5-cdea0fa6d0f9
         Total devices 12 FS bytes used 4.76TB
         devid    6 size 930.99GB used 429.32GB path /dev/sdf
         devid    5 size 930.99GB used 429.32GB path /dev/sde
         devid    8 size 930.99GB used 429.32GB path /dev/sdh
         devid    9 size 930.99GB used 429.32GB path /dev/sdi
         devid    4 size 930.99GB used 429.32GB path /dev/sdd
         devid    3 size 930.99GB used 429.32GB path /dev/sdc
         devid   11 size 930.99GB used 429.08GB path /dev/sdk
         devid    2 size 930.99GB used 429.32GB path /dev/sdb
         devid   10 size 930.99GB used 429.32GB path /dev/sdj
         devid   12 size 930.99GB used 429.33GB path /dev/sdl
         devid    7 size 930.99GB used 429.32GB path /dev/sdg
         devid    1 size 930.99GB used 429.09GB path /dev/sda

Btrfs v0.19-35-g1b444cd

df -h and btrfs fi show seem to be in good size agreement.  Btrfs was 
created as raid1 metadata and raid0 data.  I would like to delete the 
last 4 drives leaving 7T of space to hold 4.9T of data.  My plan would 
be to remove /dev/sdi, j, k, l one at a time.  After all are deleted run 
"btrfs fi balance /btrfs".  The data is not critical and can be lost but 
I am really trying to avoid the hassle of having to completely redo the 
filesystem.  Does my deletion plan seem reasonable.  Please, I'm really 
swimming alone here and would value some advice.
Jim Maloney
-- 


             reply	other threads:[~2012-06-05 14:38 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-05 14:38 Jim [this message]
2012-06-05 15:47 ` delete disk proceedure Hugo Mills
     [not found]   ` <4FCE2B70.9020107@webstarts.com>
2012-06-05 16:00     ` Hugo Mills
2012-06-05 16:05       ` Jim
2012-06-05 16:19 ` Helmut Hullen
2012-06-05 17:04   ` Hugo Mills
2012-06-05 17:12     ` Jim
2012-06-05 17:18       ` Hugo Mills
2012-06-05 17:23     ` Helmut Hullen

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=4FCE19D3.4090908@webstarts.com \
    --to=jim@webstarts.com \
    --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 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).