Starfish4711

I have re-created the pool, again using btrfs with encryption. According to syslog this time it should be encrypted indeed:

Dec 2 21:00:34 nas-langner24 emhttpd: shcmd (506): udevadm settle
Dec 2 21:00:34 nas-langner24 kernel: md1p1: running, size: 5860522532 blocks
Dec 2 21:00:34 nas-langner24 emhttpd: shcmd (510): /usr/sbin/cryptsetup luksOpen /dev/sdb1 sdb1 --allow-discards --key-file=/root/keyfile
Dec 2 21:00:34 nas-langner24 kernel: device-mapper: ioctl: 4.48.0-ioctl (2023-03-01) initialised: [email protected]
Dec 2 21:00:36 nas-langner24 kernel: BTRFS: device fsid 2560928a-5aad-4693-b1f5-6dc76d97f289 devid 1 transid 11 /dev/dm-0 (251:0) scanned by udevd (11432)
Dec 2 21:00:36 nas-langner24 emhttpd: cache: Encrypted volume present
Dec 2 21:00:36 nas-langner24 emhttpd: shcmd (512): /usr/sbin/cryptsetup luksOpen /dev/sdc1 sdc1 --allow-discards --key-file=/root/keyfile
Dec 2 21:00:38 nas-langner24 kernel: BTRFS: device fsid 2560928a-5aad-4693-b1f5-6dc76d97f289 devid 2 transid 11 /dev/dm-1 (251:1) scanned by udevd (11433)
Dec 2 21:00:38 nas-langner24 emhttpd: cache2: Encrypted volume present
Dec 2 21:00:38 nas-langner24 emhttpd: import 30 pool device: (sdb) Samsung_SSD_870_EVO_500GB_S7EWNL0X331366M
Dec 2 21:00:38 nas-langner24 emhttpd: import 31 pool device: (sdc) Samsung_SSD_870_EVO_500GB_S7EWNL0X331385N
Dec 2 21:00:38 nas-langner24 emhttpd: update_pool_cfg: 30 cache 0
...
...
Dec 2 21:00:39 nas-langner24 emhttpd: mounting /mnt/cache
Dec 2 21:00:39 nas-langner24 emhttpd: shcmd (520): mkdir -m 0666 -p /mnt/cache
Dec 2 21:00:39 nas-langner24 emhttpd: cache: btrfs verify devices
Dec 2 21:00:39 nas-langner24 emhttpd: /sbin/btrfs filesystem show 2560928a-5aad-4693-b1f5-6dc76d97f289 2>&1
Dec 2 21:00:39 nas-langner24 emhttpd: Label: none uuid: 2560928a-5aad-4693-b1f5-6dc76d97f289
Dec 2 21:00:39 nas-langner24 emhttpd: Total devices 2 FS bytes used 144.00KiB
Dec 2 21:00:39 nas-langner24 emhttpd: devid 1 size 465.75GiB used 2.01GiB path /dev/mapper/sdb1
Dec 2 21:00:39 nas-langner24 emhttpd: devid 2 size 465.75GiB used 2.01GiB path /dev/mapper/sdc1
Dec 2 21:00:39 nas-langner24 emhttpd: mounting: cache devices: 2 slots: 2 missing: 0
Dec 2 21:00:39 nas-langner24 emhttpd: shcmd (521): mount -t btrfs -o noatime,nodiscard,space_cache=v2 -U 2560928a-5aad-4693-b1f5-6dc76d97f289 /mnt/cache
Dec 2 21:00:39 nas-langner24 kernel: BTRFS info (device dm-0): first mount of filesystem 2560928a-5aad-4693-b1f5-6dc76d97f289
Dec 2 21:00:39 nas-langner24 kernel: BTRFS info (device dm-0): using crc32c (crc32c-intel) checksum algorithm
Dec 2 21:00:39 nas-langner24 kernel: BTRFS info (device dm-0): enabling ssd optimizations
Dec 2 21:00:39 nas-langner24 kernel: BTRFS info (device dm-0): enabling free space tree
Dec 2 21:00:39 nas-langner24 emhttpd: shcmd (522): mount -o remount,discard=async /mnt/cache
Dec 2 21:00:39 nas-langner24 emhttpd: update_pool_cfg: 30 cache 0


But, what I really don't like: the keyfile used for unlocking the cache pool still exists on the local drive:

root@nas-langner24:~# ls -la /root/keyfile
-rw-r--r-- 1 root root 799760 Dec 2 21:16 /root/keyfile

In my opinion the keyfile should be removed immediately after unlocking drives! Can I delete the keyfile after the array has been started or is it needed for some reason?