1 |
covici@××××××××××.com wrote: |
2 |
|
3 |
> Rich Freeman <rich0@g.o> wrote: |
4 |
> |
5 |
> > On Sat, Dec 19, 2015 at 2:56 AM, <covici@××××××××××.com> wrote: |
6 |
> > > |
7 |
> > > I was never able to get either zfs or btrfs to work correctly, zfs was |
8 |
> > > very vulnerable -- I forgot to export a zfs on a usb drive and got an |
9 |
> > > enless loop of processes untill I rebooted. Btrfs never did work for |
10 |
> > > me, I created a pool, copied my root file system, usr and var into |
11 |
> > > ssubvolumes, and copied my files, but when I would boot into it, |
12 |
> > > everything was messed up, processes thought files were missing, very |
13 |
> > > strange. So, how did you set up either one of those -- I would love to |
14 |
> > > use it because I have ssds and I don't want to rely on their firmware |
15 |
> > > either. |
16 |
> > |
17 |
> > Well, I don't have much personal experience with zfs, but the ZFS on |
18 |
> > Linux lead is a Gentoo dev, so you're in good company there all the |
19 |
> > same. I personally use btrfs. |
20 |
> > |
21 |
> > The obvious caveat is that it is still relatively experimental, and |
22 |
> > raid5/6 is VERY experimental. I plan to convert to raid5/6 at a |
23 |
> > future date but am staying away from it for now (and a selling point |
24 |
> > of btrfs is that reshaping in-place is easy). |
25 |
> > |
26 |
> > I can't really vouch for what went wrong with your migration. It |
27 |
> > could be anything from a failure to preserve all your file attributes |
28 |
> > to something with btrfs itself or your bootloader config/etc. It |
29 |
> > isn't hard to do a new install in btrfs though, and you can always |
30 |
> > mess with it in a VM, or even mess with doing migrations in a VM. |
31 |
> > |
32 |
> > My btrfs install notes are at: |
33 |
> > https://docs.google.com/document/d/1VJlJyYLTZScta9a81xgKOIBjYsG3_VfxxmUSxG23Uxg/edit?usp=sharing |
34 |
> > (I still plan to merge this stuff into the handbook. Maybe a good |
35 |
> > holiday project... Oh, and if it isn't already obvious anybody can |
36 |
> > add comments and half this list seems to have already done so.) |
37 |
> > |
38 |
> > Oh, for a boot image I tend to use system rescue CD since it has all |
39 |
> > the necessary userspace and is gentoo-based (and you can always emerge |
40 |
> > --sync and install whatever you need inside it). I tend to use the |
41 |
> > alternate kernel since it is newer, and with btrfs newer tends to be |
42 |
> > better. In production I'm currently on 3.18 eyeing an upgrade to 4.1. |
43 |
> > I tend to stay on the latest longterm, but not when they are first |
44 |
> > declared as longterm. That seems to be the sweet spot for getting |
45 |
> > btrfs features and bugfixes, but not getting as many of the |
46 |
> > regressions. I use grub2/dracut to boot, and that is in my guide. |
47 |
> > |
48 |
> > If you follow those notes for a stage3 install it should "just work." |
49 |
> > If you want to mess around I suggest just doing a vanilla install on a |
50 |
> > VM once to validate that it works for you and then tweak from a |
51 |
> > position of strength. |
52 |
> |
53 |
> Thanks. I will check out your notes and figure out something -- it was |
54 |
> definitely strange. I have a vm I can play with -- its older, but I can |
55 |
> bring it up to date and see what happens. |
56 |
> |
57 |
> Thanks again. |
58 |
|
59 |
One thing I was thinking of -- since I like separate file systems for |
60 |
each major directory i.e. separate /usr, /var, /home, /tmp and even |
61 |
/var/tmp/portage, I thought I would make btrfs file systems using lvm. |
62 |
The advantage is that I use lvm already, so this would be easy for me to |
63 |
do and safer in case one of them goes south and easier to control space |
64 |
allocation. The only disadvantage I can see is if its a performance |
65 |
hit, does anyone have any knowledge of that is true? |
66 |
|
67 |
-- |
68 |
Your life is like a penny. You're going to lose it. The question is: |
69 |
How do |
70 |
you spend it? |
71 |
|
72 |
John Covici |
73 |
covici@××××××××××.com |