This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revisionNext revisionBoth sides next revision | ||
computing:zfsreminders [2022/08/28 01:17] – oemb1905 | computing:zfsreminders [2024/04/21 23:07] – oemb1905 | ||
---|---|---|---|
Line 46: | Line 46: | ||
zfs load-key pool/ | zfs load-key pool/ | ||
zfs mount pool/ | zfs mount pool/ | ||
+ | | ||
+ | If you need to delete a dataset, do the following: | ||
+ | |||
+ | zfs destroy -r pool/ | ||
| | ||
To create snapshots, here is a reasonable template: | To create snapshots, here is a reasonable template: | ||
Line 79: | Line 83: | ||
zpool status -v | zpool status -v | ||
zpool iostat -v | zpool iostat -v | ||
- | zpool list | + | zpool list -v |
| | ||
Also, to see whether cache volume is necessary, run and look at cache hit/miss ratio: | Also, to see whether cache volume is necessary, run and look at cache hit/miss ratio: | ||
Line 85: | Line 89: | ||
arc_summary | arc_summary | ||
- | --- //[[jonathan@haacksnetworking.org|oemb1905]] | + | Change location of the keys for your encrypted datasets: |
+ | |||
+ | sudo zfs set keylocation=file:/// | ||
+ | |||
+ | Send and receive entire pool to new pool | ||
+ | |||
+ | zfs snapshot -r pool1@latestsnap | ||
+ | zfs send -R pool1@latestsnap | zfs receive -F pool2 | ||
+ | |||
+ | Arc information | ||
+ | |||
+ | arcstat | ||
+ | arc_summary -d | less | ||
+ | nano / | ||
+ | <# 8GB example - 8*(2^30) = below> | ||
+ | <# | ||
+ | <# Set Max ARC size => 2GB == 2147483648 Bytes> | ||
+ | <options zfs zfs_arc_max=2147483648> | ||
+ | <# Set Min ARC size => 1GB == 1073741824> | ||
+ | <options zfs zfs_arc_min=1073741824> | ||
+ | |||
+ | More examples ... | ||
+ | |||
+ | --- //[[webmaster@haacksnetworking.org|oemb1905]] |