3 ms·

> For the hobbyist I don;'t see any reason why you'd really want to have an mdadm array The "don't even dare to use ZFS without dedicating 8-16 GB of memory to

> For the hobbyist I don;'t see any reason why you'd really want to have an mdadm array The "don't even dare to use ZFS without dedicating 8-16 GB of memory to it" warnings all over the ZFS documentation online has served as a very, very good reason for me to not use ZFS for anything at all. I'll stick with tooling that lets my homelab actually have enough RAM to run the applications I want to run.

Sebb767 6y ago
> don't even dare to use ZFS without dedicating 8-16 GB of ECC [!] memory to it Fixed that for you. Now, I've since build a storage server for my homelab using ZFS, but mdadm is far more accessible. It also feels easier - I know what's on the drives and how it is stored. In case of something strange happening with ZFS, I don't have any hope except backups. Also, ZFS lacks support in most distributions and somewhat obscure encryption capability. I don't mean to bash ZFS here - it's great. But the GP feels like it's saying "I don't see why would anyone not want to run a dedicated kubernetes cluster with HA for running a program on Linux".
- KaiserPro 6y ago
  > GP feels like it's saying "I don't see why would anyone not want to run a dedicated kubernetes cluster with HA for running a program on Linux". Thats not quite right Its more that the documentation, command line interface and general user setup is far more friendly than mdadm. I've been a sysadmin for many years, and looked after innumerable file servers, from clustered XFS (!) through many years of lustre, plain old XFS/ext2/3/5 on HWraid to netapps&isilons, and all sorts of flash in the pan appliances. Barring GPFS, the only file system that has documentation and tooling that is simple to understand and doesn't immediately bite you in the arse is ZFS. Kubernetes is neither simple, easy or quick to setup, or run.
KaiserPro 6y ago
that warning is the same for any File server. if you want performance, then you need ram. otherwise you don't have enough space to keep hot blocks. ZFS works as well as any FS in places with 8 gigs of ram. Hell I even run a KVM node with just 16 gigs of ram. Its working just fine.
- McGlockenshire 6y ago
  > if you want performance, then you need ram This is not what the documentation or the thousands of posts from ZFS experts out there imply. The direct implication is that ZFS REQUIRES that much memory for day to day mundane operation.
tha0x5 6y ago
>The "don't even dare to use ZFS without dedicating 8-16 GB of memory to it" This is WRONG and FUD. Unless you're talking about turning dedup on. >warnings all over the ZFS documentation online has served as a very, very good reason for me to not use ZFS for anything at all. Links or it didn't happen. >I'll stick with tooling that lets my homelab actually have enough RAM to run the applications I want to run. Then stick with ZFS.
- McGlockenshire 6y ago
  > Links or it didn't happen. Google "zfs memory requirements" and pick one. Go argue with them, not with me. The top result is a Stack Overflow answer, perhaps you can start there.
  - tha0x5 6y ago
    >Google "zfs memory requirements" and pick one. That's not documentation, and the posts agree with me, counter to your original claim. > Go argue with them, not with me. The top result is a Stack Overflow answer, perhaps you can start there. The top result literally agrees with me. It links to a page talking about dedup. So, Google actually proved you wrong. You're spreading FUD.

Sebb767 6y ago

> don't even dare to use ZFS without dedicating 8-16 GB of ECC [!] memory to it Fixed that for you. Now, I've since build a storage server for my homelab using ZFS, but mdadm is far more accessible. It also feels easier - I know what's on the drives and how it is stored. In case of something strange happening with ZFS, I don't have any hope except backups. Also, ZFS lacks support in most distributions and somewhat obscure encryption capability. I don't mean to bash ZFS here - it's great. But the GP feels like it's saying "I don't see why would anyone not want to run a dedicated kubernetes cluster with HA for running a program on Linux".

KaiserPro 6y ago
> GP feels like it's saying "I don't see why would anyone not want to run a dedicated kubernetes cluster with HA for running a program on Linux". Thats not quite right Its more that the documentation, command line interface and general user setup is far more friendly than mdadm. I've been a sysadmin for many years, and looked after innumerable file servers, from clustered XFS (!) through many years of lustre, plain old XFS/ext2/3/5 on HWraid to netapps&isilons, and all sorts of flash in the pan appliances. Barring GPFS, the only file system that has documentation and tooling that is simple to understand and doesn't immediately bite you in the arse is ZFS. Kubernetes is neither simple, easy or quick to setup, or run.

KaiserPro 6y ago

that warning is the same for any File server. if you want performance, then you need ram. otherwise you don't have enough space to keep hot blocks. ZFS works as well as any FS in places with 8 gigs of ram. Hell I even run a KVM node with just 16 gigs of ram. Its working just fine.

McGlockenshire 6y ago
> if you want performance, then you need ram This is not what the documentation or the thousands of posts from ZFS experts out there imply. The direct implication is that ZFS REQUIRES that much memory for day to day mundane operation.

tha0x5 6y ago

>The "don't even dare to use ZFS without dedicating 8-16 GB of memory to it" This is WRONG and FUD. Unless you're talking about turning dedup on. >warnings all over the ZFS documentation online has served as a very, very good reason for me to not use ZFS for anything at all. Links or it didn't happen. >I'll stick with tooling that lets my homelab actually have enough RAM to run the applications I want to run. Then stick with ZFS.

McGlockenshire 6y ago
> Links or it didn't happen. Google "zfs memory requirements" and pick one. Go argue with them, not with me. The top result is a Stack Overflow answer, perhaps you can start there.
- tha0x5 6y ago
  >Google "zfs memory requirements" and pick one. That's not documentation, and the posts agree with me, counter to your original claim. > Go argue with them, not with me. The top result is a Stack Overflow answer, perhaps you can start there. The top result literally agrees with me. It links to a page talking about dedup. So, Google actually proved you wrong. You're spreading FUD.