Quote:
Originally Posted by vermaden
It does not cover 4k drives (gnop devices), so its not the best, but thanks  |
Right! and there's lots of madness lying there. So here's what I did, and please correct me if I'm wrong, on my nas pool, my logic was to tackle the Advanced Format bs by partitioning the disk so that it stays in the boundaries of 4096 bytes at a time for whatever operation, then well Geli was set to feed ZFS 4K chunks and ZFS would just align (ashift 12), I didn't bother using gnop since I'm already at 3 software layers for disk access without counting ZFS. Is there any issue apparent in here?
Here's the implementation detail
Code:
# gpart destroy -F ada1
...
# gpart destroy -F ada4
# gpart create -s GPT ada1
...
# gpart create -s GPT ada4
# gpart add -t freebsd-zfs -l zdisk1 -b 2048 -a 4k ada1
...
# gpart add -t freebsd-zfs -l zdisk4 -b 2048 -a 4k ada4
# glabel label -v znas1 /dev/ada1p1
...
# glabel label -v znas4 /dev/ada4p1
# geli init -e aes -l 128 -K /media/boot/keys/znas1.key -b -s 4096 -B /media/backups/znas1.eli.meta /dev/label/znas1
...
# geli init -e aes -l 128 -K /media/boot/keys/znas4.key -b -s 4096 -B /media/backups/znas4.eli.meta /dev/label/znas4
# geli attach -k /media/boot/keys/znas1.key /dev/label/znas1
...
# geli attach -k /media/boot/keys/znas4.key /dev/label/znas4
# zpool create nas raidz /dev/label/znas1.eli /dev/label/znas2.eli /dev/label/znas3.eli /dev/label/znas4.eli
# zdb nas | grep ashift
# zpool export nas
# zpool import nas
# zpool status
Quote:
Originally Posted by vermaden
Encryption is not the problem.
The MAIN problem, is that FreeBSD Bootloader is not able to boot FreeBSD from ZFS which is on encrypted GELI drive, so we have to do it other way.
|
Got it. Personally I found this ZFS setup way too complex already, I'm may be accustomed to KISS stuff from OpenBSD but I really needed ZFS for this server, it took me about 10days to get everything sorted out with not much trial and errors so for now i think i'd better pass on Beadm although I can see how useful it is.