When you don't want ZFS: HAST - High Availability Storage (block-level replication and failover) for UFS reddit / BSD ---------------------------------------------------------------------- [deleted] · 2012-01-28 20:15 [deleted] ---------------------------------------------------------------------- gimpbully · 2012-01-28 20:44 "Note: HAST is currently limited to two cluster nodes in total." Well that's not very impressing, this is just drdb.. I always want to be impressed by fbsd but they're always so far behind. Didn't they *just* get active/active multipathing? ---------------------------------------------------------------------- [deleted] · 2012-01-28 21:27 > Didn't they just get active/active multipathing? Yeah, it's late coming considering the age of geom_multipath but it's basically a total rewrite. As far as I can tell both geom_fox and geom_multipath were very early proof of concepts and nobody touched multipath in a long time. Fox isn't even supposed to be used at all. On the other hand, have you seen the power of the GEOM framework? Slow and steady wins the race :) What we're missing in features we make up for in stability and well thought out code/frameworks. We won't be rewriting it anytime soon. (upower, udisks, hal, etc etc etc) Also, DRBD hit 2.6.23 in October 2007. HAST has been in -CURRENT since Feb 2010. So it's not THAT far behind, but HAST is still behind feature-wise. ---------------------------------------------------------------------- edogawaconan · 2012-01-29 04:02 HAST and ZFS provide different thing. IIUC, they can be used in combination. ---------------------------------------------------------------------- X-Istence · 2012-01-29 04:19 I've used HAST with ZFS, without issues... ---------------------------------------------------------------------- [deleted] · 2012-01-29 04:49 [deleted] ---------------------------------------------------------------------- X-Istence · 2012-01-29 06:07 Because ZFS "replication" is using zfs send/receive. There is no real replication. Whereas with HAST there is. When a write returns to the app it is written on both sides. No need to take a snapshot, and zfs send/recv it before it is on the other side. This means if one node goes down the other can immediately pick up where the other left off, hopefully with a small interruption waiting for the services to start. I am not sure whether you understand what HAST is ... this is not for local disks (which if you didn't want ZFS there are several GEOM providers that can do mirroring and raid without issues) but rather for having two servers that are fail-over writing the data to both. So with node-1 and node-2 if node-1 dies node-2 takes over. Even if there is a fire and its hard drives melt down, all your data is also on node-2. ---------------------------------------------------------------------- jonforthewin · 2012-01-29 11:04 ZFS and HAST are for completely different things. ---------------------------------------------------------------------- 1esproc · 2012-01-29 15:19 DRBD, friend. ---------------------------------------------------------------------- gimpbully · 2012-01-29 17:39 Oh, understood. If i'm going for a system I need up 24x7 sitting in a corner, i'm going FBSD. I'd love to extend that to the storage realm, but Linux keeps eating FBSD's cake there. Sure, it's not rock solid but when you have every parallel filesystem out there and every multipathing style, every controller, etc supported on linux, you never get the FBSD foot in the door. It's just a shame. Give me support for lustre, full active/active multipathing for my preferred vendor over RDMA IB (both SRP and connections to clients) and heartbeat-style failover. If you do that, I'll throw 3 large storage clusters at FBSD tomorrow. ---------------------------------------------------------------------- [deleted] · 2012-01-29 22:20 There IS active-active multipathing now, but you have to patch 9.0-RELEASE yourself or run 9-CURRENT I'm not sure what RDMA IB is :-P and yes, it's annoying we don't have lustre ---------------------------------------------------------------------- [deleted] · 2012-01-30 00:35 [deleted] ---------------------------------------------------------------------- [deleted] · 2012-01-30 00:41 [deleted] ---------------------------------------------------------------------- [deleted] · 2012-01-30 00:42 [deleted] ---------------------------------------------------------------------- [deleted] · 2012-01-30 00:46 [deleted] ---------------------------------------------------------------------- jonforthewin · 2012-01-30 00:47 ZFS' replication and HAST's replication are different and intended for completely different applications. Massive amounts of RAM are needed for ZFS' advanced features, not to use ZFS. ZFS is fine with 1gb of RAM. You have to adjust your parameters for that, but it's still fine. For everything else, there's rsync and incremental on-the-fly rsync. > maybe you don't have a box with 32GB of RAM This leads me to believe you have never used ZFS in production for any large environment where these things actually matter. ---------------------------------------------------------------------- [deleted] · 2012-01-30 00:49 [deleted] ---------------------------------------------------------------------- [deleted] · 2012-01-30 00:55 [deleted] ---------------------------------------------------------------------- jonforthewin · 2012-01-30 00:59 > the need to spoon-feed basics to me Because ZFS' replication and HAST are for completely different purposes with completely different goals. In any situation where one would be used instead of the other, the other would not have been a viable option in the first place. > there are many situations when rsync's file-level algorithm is a horrible option Yes, there are. > wouldn't say "everything else." Okay, "just about everything else". Unison is probably better. ---------------------------------------------------------------------- X-Istence · 2012-01-30 01:15 I went with ZFS over UFS because there is no fsck when I re-import the pool. My data is checksummed and dedupped. ZFS's tools for managing "file systems" is fantastic. Creating new mountpoints with quotas, setting restrictions, turning on dedup per mountpoint and various other features. I just feel much safer trusting my data to ZFS than I do trusting my data on UFS. ---------------------------------------------------------------------- [deleted] · 2012-01-30 02:47 [deleted] ---------------------------------------------------------------------- jonforthewin · 2012-01-30 09:46 > You do realize that we agree, right? LoL Yeah > I don't understand what you're 'arguing' about. Ah yeah man I'm not arguing it's just that fucking . . Reddit-or thread shit that just like . . happens. > thinking that HAST didn't work with ZFS The problem with HAST is that it replicates block devices. What makes ZFS strong is that it leverages multiple block devices. Are you gonna clone 16 disks and hope to reassemble a zpool on the target remote / "clone" host?? srsly?! lawl uhh . . hypothetically that may work but is any one seriously gonna do that? Damn, maybe when HAST uses that "memsync" mode those of us who have real-world real-value systems to use will take a look at it. -_- HAST will be something worth considering once the memsync mode is available. > 'm not going to continue this any further. Naw dude it's chill it's chill it's chill #FreeBSD on irc.freenode.net I will see you there fellow citizen of our Free / Open world.