1 |
On 12/30/2015 10:14 PM, lee wrote: |
2 |
> Hi, |
3 |
> |
4 |
> soon I'll be replacing the system disks and will copy over the existing |
5 |
> system to the new disks. I'm wondering how much merit there would be in |
6 |
> being able to make snapshots to be able to revert back to a previous |
7 |
> state when updating software or when installing packages to just try |
8 |
> them out. |
9 |
> |
10 |
> To be able to make snapshots, I could use btrfs on the new disks. When |
11 |
> using btrfs, I could use the hardware RAID-1 as I do now, or I could use |
12 |
> the raid features of btrfs instead to create a RAID-1. |
13 |
> |
14 |
> |
15 |
> Is it worthwhile to use btrfs? |
16 |
|
17 |
Yes. |
18 |
|
19 |
;-) |
20 |
|
21 |
> Am I going to run into problems when trying to boot from the new disks |
22 |
> when I use btrfs? |
23 |
|
24 |
Yes. |
25 |
|
26 |
;-) |
27 |
|
28 |
well ... maybe. |
29 |
|
30 |
prepare for some learning curve. but it is worth it! |
31 |
|
32 |
> Am I better off using the hardware raid or software raid if I use btrfs? |
33 |
|
34 |
I would be picky here and separate "software raid" from "btrfs raid": |
35 |
|
36 |
software raid .. you think of mdadm-based software RAID as we know it in |
37 |
the linux world? |
38 |
|
39 |
btrfs offers RAID-like redundancy as well, no mdadm involved here. |
40 |
|
41 |
The general recommendation now is to stay at level-1 for now. That fits |
42 |
your 2-disk-situation. |
43 |
|
44 |
> The installation/setup is simple: 2x3.5" are to be replaced by 2x2.5", |
45 |
> each 15krpm, 72GB SAS disks, so no fancy partioning is involved. |
46 |
> |
47 |
> (I need the physical space to plug in more 3.5" disks for storage. Sure |
48 |
> I have considered SSDs, but they would cost 20 times as much and provide |
49 |
> no significant advantage in this case.) |
50 |
> |
51 |
> |
52 |
> I could just replace one disk after the other and let the hardware raid |
53 |
> do it all for me. A rebuilt takes only 10 minutes or so. Then I could |
54 |
> convert the file system to btrfs, or leave it as is. That might even be |
55 |
> the safest bet because I can't miss anything when copying. (What the |
56 |
> heck do I have it for? :) ) |
57 |
> |
58 |
> |
59 |
> Suggestions? |
60 |
|
61 |
I would avoid converting and stuff. |
62 |
|
63 |
Why not try a fresh install on the new disks with btrfs? |
64 |
You can always step back and plug in the old disks. |
65 |
You could even add your new disks *beside the existing system and set up |
66 |
a new rootfs alongside (did that several times here). |
67 |
|
68 |
- |
69 |
|
70 |
There is nearly no partitioning needed with btrfs (one of the great |
71 |
benefits). |
72 |
|
73 |
I never had /boot on btrfs so far, maybe others can guide you with this. |
74 |
|
75 |
My /boot is plain extX on maybe RAID1 (differs on |
76 |
laptops/desktop/servers), I size it 500 MB to have space for multiple |
77 |
kernels (especially on dualboot-systems). |
78 |
|
79 |
Then some swap-partitions, and the rest for btrfs. |
80 |
|
81 |
So you will have something like /dev/sd[ab]3 for btrfs then. |
82 |
|
83 |
Create your btrfs-"pool" with: |
84 |
|
85 |
# mkfs.btrfs -m raid1 -d raid1 /dev/sda3 /dev/sdb3 |
86 |
|
87 |
Then check for your btrfs-fs with: |
88 |
|
89 |
# btrfs fi show |
90 |
|
91 |
Oh: I realize that I start writing a howto here ;-) |
92 |
|
93 |
In short: |
94 |
|
95 |
In my opinion it is worth learning to use btrfs. |
96 |
checksums, snapshots, subvolumes, compression ... bla ... |
97 |
|
98 |
It has some learning curve, especially with a distro like gentoo. |
99 |
But it is manageable. |
100 |
|
101 |
As mentioned here several times I am using btrfs on >6 of my systems for |
102 |
years now. And I don't look back so far. |
103 |
|
104 |
- |
105 |
|
106 |
look up: |
107 |
|
108 |
https://btrfs.wiki.kernel.org/index.php/Using_Btrfs_with_Multiple_Devices |