1 |
Rich Freeman <rich0@g.o> writes: |
2 |
|
3 |
> On Fri, Jan 9, 2015 at 4:02 PM, lee <lee@××××××××.de> wrote: |
4 |
>> Rich Freeman <rich0@g.o> writes: |
5 |
>> |
6 |
>>> On Mon, Dec 29, 2014 at 8:55 AM, lee <lee@××××××××.de> wrote: |
7 |
>>>> |
8 |
>>>> Just why can't you? ZFS apparently can do such things --- yet what's |
9 |
>>>> the difference in performance of ZFS compared to hardware raid? |
10 |
>>>> Software raid with MD makes for quite a slowdown. |
11 |
>>>> |
12 |
>>> |
13 |
>>> Well, there is certainly no reason that you couldn't serialize a |
14 |
>>> logical volume as far as design goes. It just isn't implemented (as |
15 |
>>> far as I'm aware), though you certainly can just dd the contents of a |
16 |
>>> logical volume. |
17 |
>> |
18 |
>> You can use dd to make a copy. Then what do you do with this copy? I |
19 |
>> suppose you can't just use dd to write the copy into another volume |
20 |
>> group and have it show up as desired. You might destroy the volume |
21 |
>> group instead ... |
22 |
> |
23 |
> You can dd from a logical volume into a file, and from a file into a |
24 |
> logical volume. You won't destroy the volume group unless you do |
25 |
> something dumb like trying to copy it directly onto a physical volume. |
26 |
> Logical volumes are just block devices as far as the kernel is |
27 |
> concerned. |
28 |
|
29 |
You mean I need to create a LV (of the same size) and then use dd to |
30 |
write the backup into it? That doesn't seem like a safe method. |
31 |
|
32 |
>> How about ZFS as root file system? I'd rather create a pool over all |
33 |
>> the disks and create file systems within the pool than use something |
34 |
>> like ext4 to get the system to boot. |
35 |
> |
36 |
> I doubt zfs is supported by grub and such, so you'd have to do the |
37 |
> usual in-betweens as you're eluding to. However, I suspect it would |
38 |
> generally work. I haven't really used zfs personally other than |
39 |
> tinkering around a bit in a VM. |
40 |
|
41 |
That would be a very big disadvantage. When you use zfs, it doesn't |
42 |
really make sense to have extra partitions or drives; you just want to |
43 |
create a pool from all drives and use that. Even if you accept a boot |
44 |
partition, that partition must be on a raid volume, so you either have |
45 |
to dedicate at least two disks to it, or you're employing software raid |
46 |
for a very small partition and cannot use the whole device for ZFS as |
47 |
recommended. That just sucks. |
48 |
|
49 |
>> And how do I convert a system installed on an ext4 FS (on a hardware |
50 |
>> raid-1) to ZFS? I can plug in another two disks, create a ZFS pool from |
51 |
>> them, make file systems (like for /tmp, /var, /usr ...) and copy |
52 |
>> everything over. But how do I make it bootable? |
53 |
>> |
54 |
> |
55 |
> I'm pretty sure you'd need an initramfs and a boot partition that is |
56 |
> readable by the bootloader. You can skip that with btrfs, but not |
57 |
> with zfs. GRUB is FSF so I doubt they'll be doing anything about zfs |
58 |
> anytime soon. Otherwise, you'll have to copy everything over - btrfs |
59 |
> can do in-place ext4 conversion, but not zfs. |
60 |
|
61 |
Well, I don't want to use btrfs (yet). The raid capabilities of brtfs |
62 |
are probably one of its most unstable features. They are derived from |
63 |
mdraid: Can they compete with ZFS both in performance and, more |
64 |
important, reliability? |
65 |
|
66 |
With ZFS at hand, btrfs seems pretty obsolete. |
67 |
|
68 |
|
69 |
-- |
70 |
Again we must be afraid of speaking of daemons for fear that daemons |
71 |
might swallow us. Finally, this fear has become reasonable. |