Jump to content

wurmfood

Members
  • Posts

    36
  • Joined

  • Last visited

Everything posted by wurmfood

  1. Definitely don't use dedupe. Compression seems to work fine for me, but most of my data so far isn't very compressible. When I've done tests using things that are mostly text it works out well. For most things that are binary or encrypted, it doesn't seem to do much. I'm getting a compressratio of only 1.01 using either zstd or lz4 on most of my datasets. If you know you're going to have places that are going to benefit from compression, use it there, but I'm tempted to turn it off for a lot of my stuff (media, encrypted backups).
  2. Any normal backup solution should work. In general, it sounds like you want to just make an image of the live system. The dd utility will work for this. dd if=/dev/disk/by-id/[your disk] of=/path/to/zfs/pool/root.img bs=1M status=progress You can adjust the block size based on what you find works well for your system. You can later restore it using exactly the same process, just switching your in-file (if) and out-file (of). Note that file here can include block devices.
  3. I suggest checking out this post and the solution a little below it, as it sounds like your same problem.
  4. Damn. I actually have spare money right now, but I'm too slow.
  5. I was able to get it working and played with it. I didn't realize I had to create a ZVOL to make it work, and it introduced some interesting problems. I'm not sure I'll stick with it, but I like the idea as a backup solution for the local Windows machines.
  6. wurmfood

    ZFS on Helios64

    The only ones really needed to make it work are the libs, either zfs-dkms or kmod-zfs, zfs, zfs-initramfs, and python3-pyzfs. The others are optional.
  7. wurmfood

    ZFS on Helios64

    The services you have to enable are zfs-import-cache, zsf-import.target, zfs-mount, zfs.target, and zfs-zed. You don't have to unmask anything. Just enable those and it'll work. Yup. If you build using deb-kmod instead of deb-dkms, it'll build the kmod. That's what I did.
  8. wurmfood

    ZFS on Helios64

    Yes, once you have everything installed, you need to enable zfs-import-cache, zsf-import.target, zfs-mount, zfs.target, zfs-zed.
  9. wurmfood

    ZFS on Helios64

    I've gotten ZFS working pretty well following the compile instructions on their website. I just put everything in a chroot to make it cleaner. # Fist, install a few things we're going to need: sudo apt install debootstrap # Now, create our chroot mkdir -p chroot-zfs # This will take a while sudo debootstrap --variant=buildd focal chroot-zfs # mount proc, sys, and dev sudo mount -t proc /proc chroot-zfs/proc sudo mount --rbind /sys chroot-zfs/sys sudo mount --rbind /dev chroot-zfs/dev # Copy the files we need for apt. The sources.list is missing many things we'll need. cp /etc/apt/sources.list . cat /etc/apt/sources.list.d/armbian >> sources.list sudo cp sources.list chroot-zfs/etc/sources.list # Chroot in chroot chroot-zfs /bin/bash # Install wget and gnupg apt install -y wget gnupg # Add the repository key wget -qO - http://apt.armbian.com/armbian.key | apt-key add - # Update apt update apt upgrade -y # From here, follow the instruction from ZFS The only problem I ran into is the linux-headers-current-rockchip64 were for 5.9.10 and not 5.9.11. I did a cross build in a VM for Armbian to get updated headers. Once I installed those in the chroot I was able to build kmods. I'm sure there's a way to include building ZFS 2.0 with the Armbian cross-compile setup, I just haven't figured out how yet.
  10. Do you know of a good guide for getting iSCSI working with ZFS? Or just a guide for iSCSI? I took a brief look around but everything so far is over my head.
  11. I'm having a problem where ata5 on my device isn't responding. From dmesg I get the following: [ 3.499599] ata1: SATA link down (SStatus 0 SControl 300) [ 3.811439] ata2: SATA link down (SStatus 0 SControl 300) [ 4.123422] ata3: SATA link down (SStatus 0 SControl 300) [ 4.435415] ata4: SATA link down (SStatus 0 SControl 300) [ 4.747416] ata5: SATA link down (SStatus 0 SControl 300) [ 5.461077] ata5: SATA link down (SStatus 0 SControl 300) [ 6.185068] ata5: SATA link down (SStatus 0 SControl 300) [ 6.913043] ata5: SATA link down (SStatus 0 SControl 300) [ 7.637054] ata5: SATA link down (SStatus 0 SControl 300) [ 8.361129] ata5: SATA link down (SStatus 0 SControl 300) [ 9.081132] ata5: SATA link down (SStatus 0 SControl 300) [ 9.805046] ata5: SATA link down (SStatus 0 SControl 300) [ 10.517028] ata5: SATA link down (SStatus 0 SControl 300) [ 11.237033] ata5: SATA link down (SStatus 0 SControl 300) [ 11.952977] ata5: SATA link down (SStatus 0 SControl 300) [ 12.677074] ata5: SATA link down (SStatus 0 SControl 300) That will keep going as long as I have a drive plugged into ata5. However, the same drive plugged into any other spot works just fine. To help narrow down the problem, I disconnected the SATA cables from spots 4 and 5 and switched them. Now spot 5 (plugged into 4) works. It looks like it's not a problem with the connection or the drive, but rather with the ata5 connection on the board. Any ideas on what I should do?
×
×
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines