| 1 |
Am 04.05.2014 20:40, schrieb J. Roeleveld: |
| 2 |
> On Sunday, May 04, 2014 03:07:28 PM Stefan G. Weichinger wrote: |
| 3 |
|
| 4 |
>> Oh, yes, I like ZFS and its features and used it in some cases already. |
| 5 |
>> But I didn't yet take the step to set up ZFS-root on my work machines. |
| 6 |
> |
| 7 |
> I haven't yet, but it's on the list of items to look into at some point. |
| 8 |
> I'd like to know if, with ZFS, it is possible to create block-devices like LVs |
| 9 |
> which I can then attach to VMs. Or if I have to use files instead. |
| 10 |
|
| 11 |
I think you would have to use files on top of ZFS ... but I am not |
| 12 |
up-to-date in that area. |
| 13 |
|
| 14 |
People run KVM-hosts with storage on ZFS ... nice with the snapshots etc ... |
| 15 |
|
| 16 |
> I think it does as I get the following on my server: |
| 17 |
> *** |
| 18 |
> # gdisk -l /dev/sda |
| 19 |
> GPT fdisk (gdisk) version 0.8.8 |
| 20 |
> |
| 21 |
> Partition table scan: |
| 22 |
> MBR: protective |
| 23 |
> BSD: not present |
| 24 |
> APM: not present |
| 25 |
> GPT: present |
| 26 |
> |
| 27 |
> Found valid GPT with protective MBR; using GPT. |
| 28 |
> Disk /dev/sda: 11718749184 sectors, 5.5 TiB |
| 29 |
> Logical sector size: 512 bytes |
| 30 |
> Disk identifier (GUID): 936FDBE4-A736-41CF-B9A5-51069940D3DB |
| 31 |
> Partition table holds up to 128 entries |
| 32 |
> First usable sector is 34, last usable sector is 11718749150 |
| 33 |
> Partitions will be aligned on 2048-sector boundaries |
| 34 |
> Total free space is 2014 sectors (1007.0 KiB) |
| 35 |
> |
| 36 |
> Number Start (sector) End (sector) Size Code Name |
| 37 |
> 1 2048 411647 200.0 MiB EF00 EFI System |
| 38 |
> 2 411648 2101247 825.0 MiB 8300 Linux filesystem |
| 39 |
> 3 2101248 11718749150 5.5 TiB 8E00 Linux LVM |
| 40 |
> |
| 41 |
> *** |
| 42 |
> |
| 43 |
> That's a hardware raid device with 4 * 3TB disks with raid-6. |
| 44 |
> I don't like the fact that a 2nd disk-failure can kill a raid-10 when both |
| 45 |
> disks are in the same mirror-set. |
| 46 |
> |
| 47 |
> gdisk automatically aligns on 2048 sector boundaries, that is more then enough |
| 48 |
> for the 4k-sectors and the block/stripe sizes employed by the raid-controller. |
| 49 |
|
| 50 |
Yes, this is for UEFI booting, thanks. |
| 51 |
|
| 52 |
I tried to migrate to GPT/BIOS-booting today but failed. It seems my |
| 53 |
mainboard/BIOS has problems detecting that ... I vaguely remember this |
| 54 |
from trying it back then. |
| 55 |
|
| 56 |
So I am back on a freshly partitioned and formatted SSD with plain old |
| 57 |
MBR now. |
| 58 |
|
| 59 |
I also wanted to partition the SSD according to the Erase Block Size of |
| 60 |
6144 kB by this way ... dunno if this is still needed or has any real |
| 61 |
speed benefits. |
| 62 |
|
| 63 |
Maybe I take another approach to migrate to UEFI/GPT in the next days, |
| 64 |
now that I have my rsynced filesystems at hand (I got rid of more LVs |
| 65 |
and stuff so it gets pretty slim now). |
| 66 |
|
| 67 |
|
| 68 |
> UUIDs, I believe, do work natively. And those are stored inside the partition |
| 69 |
> itself. Which means they should also work. But are not as easy to locate. (eg. |
| 70 |
> you don't specify them yourself) |
| 71 |
|
| 72 |
Yep. LABELs are human readable ... big advantage. |
| 73 |
|
| 74 |
> See the partitioning on my server above. |
| 75 |
> It boots using BIOS as I haven't been able to boot Xen using UEFI yet. |
| 76 |
|
| 77 |
So then the EFI partition is useless ... |
| 78 |
|
| 79 |
> Support should be there now, but not been able to test that yet. |
| 80 |
> GPT is supported by grub-1 (and grub2) and with the MBR-support inside GPT, |
| 81 |
> booting works from BIOS/MBR. |
| 82 |
|
| 83 |
... if your BIOS isn't crappy ;-) |
| 84 |
|
| 85 |
S |
Archives