greyfox

I am not a SAN admin but work closely with them. So take this with a grain of salt.

Best practice is always going to be to split things into as many failure domains as possible. The main argument being how would you test upgrades to the switch firmware without potentially affecting production.

But my personal experience says that assuming you have a typical A/B fabric that is probably enough to handle those sorts of problems, especially if you have director class switches where you have another supervisor to fail back to.

I've personally seen shared dev/prod switches for reasonably large companies (several switches with ~150 ports lit on each switch), and there were never any issues.

If you want to keep a little separation between dev and prod keep those on different VSANs which will force you to keep the zones separated.

Depending on how strict change management is for your org keep in mind that tangling dev+prod might make your life worse in other ways. i.e. you can probably do switch firmware updates/zoning changes/troubleshooting in dev during work hours but as soon as you connect those environments together you may have to do all of that on nights and weekends.

Before I had the helmet units I used to ride with in-ear wired headphones. Those worked pretty well but as you put the helmet on it often pulled at least one side slightly out of your ear making a worse seal. In ear means you also get some hearing protection as well which it is always good to have, especially at highway speeds or if you have loud exhaust. I will say the audio quality/clarity/volume going this route is unbeatable. If all you want is music finding an in-ear solution will be much better than speakers in your helmet. Especially if you have a loud exhaust.

You can get relatively high quality wired headphones for quite cheap that are very low profile.

I would think any wireless headphone like airpods would probably be too big to stay in when you put your helmet on, but you might be able to make it work.

One issue with headphones is that it is probably not legal in most placese, so be cautious about that. You can easily rip them out before the police would notice anyways, but still a risk.

If you go the Sena/Cardo route you should consider hearing protection as well. I usually use the foam inserts. It sounds counterintuitive but having the earplugs in actually makes the speakers easier to hear. They tend to filter the wind noise but the more direct sound from the speakers can get through.

I've run both Cardo (Packtalk Slim, Packtalk Edge), Sena (30k), and some $30 Amazon units and very much prefer Cardo units.

The first thing to do is ask any friends you might ride with what they use. It's been a while since I tried, but getting Sena to pair with anything other than Sena used to be quite a pain.

The Sena units hardware seems a little better, and the phone software may be a little more polished, but the actual comms are terrible. Filtering of background noise is nowhere near as good as Cardo, and general audio clarity is much better on Cardo.

Probably fixed by now but all sorts of problems with mesh pairing and pairing in general on the Senas.

Cardos work well enough, still a bit of a pain to get things paired sometimes, but you can do the whole process from the phone app so you don't need to know button combos.

Cardo's Bluetooth bridge capability is awesome if you have a group of Cardo users and the occasional Amazon user that you want to bring into the mesh. The mesh connects all of your Cardo units together and each Cardo unit can use its Bluetooth bridge to bring in one normal Bluetooth headset. I don't recall if we could get this working to bring Sena units into the group but I have seen release notes saying they improved compatibility so maybe it works now.

I know a couple of people with Shoei helmets with the built in Sena hookups so they get forced into Sena. Seems like the hardware for the integrated units lags behind (took them a few extra years to get a mesh option), and you are certainly locking yourself in. I would personally prefer to not have myself locked in.

If you plan to ride with multiple people getting everyone on the same system especially with mesh units is a must. We just have one big mesh group with everyone we know and as soon as you meet up everything auto connects and is good to go.

The $30 Amazon units actually work well too. Probably not remotely waterproof, and they can usually only connect to one rider at a time, but for the price you might want to start there.

Video is old now but maybe still relevant: https://youtu.be/-AMoXbXHALc

He recommends the Packtalk Slim because it is so low profile, but the new Packtalk Edge is removable, has a lower profile than the old Bolds, uses USB-C, fixes most of his problems with the removable ones and lets you charge without tethering directly to your helmet.

The slims are also little less waterproof because they are more complicated with more wires in and out. The edge being self contained, I would expect to have much better water resistance (haven't had to take my edges apart yet so I can't say that for sure).

I've had a group of us with slims in pouring rain for three hours and they did survive, one or two had some issues with buttons afterwards but they still functioned. Not sure I can even blame it on the units as we had those universal magnetic charger buttons plugged in which kept the little rain cover open at the back.

Also had one Slim unit where the microphone cable went out, not perfect, but warranty is usually pretty good. Again a win for the Edge/Bold removable units because those cables are separate from the unit itself so you could buy a helmet kit if it fails out of warranty.

Like most have said it is best to stay away from ZFS deduplication. Especially if your data set is media the chances of an entire ZFS block being the same as any other is small unless you somehow have multiple copies of the same content.

Imagine two mp3s with the exact same music content but with slightly different artist metadata. A single bit longer or shorter at the beginning of the file and even if the file spans multiple blocks ZFS won't be able to duplicate a single byte. A single bit offsetting the rest of the file just a little is enough to throw off the block checksums across every block in the file.

To contrast with ZFS, enterprise backup/NAS appliances with deduplication usually do a lot more than block level checks. They usually check for data with sliding window sizes/offsets to find more duplicate data.

There are still some use cases where ZFS can help. Like if you were doing multiple full backups of VMs. A VM image has a fixed size so the offset issue above isn't an issue, but if beware that enabling deduplication for even a single ZFS filesystem affects the entire pool, even ZFS filesystems that have deduplication disabed. The deduplication table is global for the pool and once you have turned it on you really can't get rid of it. If you get into a situation where you don't have enough memory to keep the deduplication table in memory ZFS will grind to a halt and the only way to completely remove deduplication is to copy all of your data to a new ZFS pool.

If you think this feature would still be useful for you, you might want to wait for 2.3 to release (which isn't too far off) for the new fast dedup feature which fixes or at least prevents a lot of the major issues with ZFS dedup

More info on the fast dedup feature here https://github.com/openzfs/zfs/discussions/15896

If they are on the same vlan and the same proxmox server the packets likely never leave your proxmox server. The bridge interface on your virtual host acts like its own switch so packets between those VMs would never hit the Ubiquiti ACLs.

If you have another nic on the host you could attach each VM to a different NIC which would force that traffic through the switch.

I assume these are Ubiquiti's Unifi switches not the Edgeswitches? The Edgeswitches can't be managed through Unifi but have a lot more capabilities like community vlans which would be another potential solution for intra-vlan isolation.

Proxmox might have its own options to solve this but I am not familiar with their capabilities.

Third party solutions can at least partially fix this. I have this site: https://spotifyshuffler.com/ create a shuffled copy of my playlists occasionally. Then you just play the pre-shuffled playlist with shuffle disabled.

In my case I have a large (several thousand track) playlist, and I turn on Spotify's shuffle just to pick the first track at a somewhat random spot in the large list and then shut their shuffle off toward continue the pre-shuffled list without their manipulation. Whenever I add content to the playlist I have it reshuffled.

I assume you are powering the dock? Many docks require external power before they will pass video.

Does the screen on the deck shut off or stay active?

If the screen stays active that means that it isn't detecting an HDMI signal through the dock at all.

If the screen shuts off but you get no video through the receiver, you should try hitting the power button one to shut it off wait a few seconds then turn it back on (while plugged in). Even the official dock has issues getting the deck to switch to the external output but putting the deck to sleep and back on gets it sorted out.

If that still doesn't do it plug in directly to your TV to narrow down the problem (removes the receiver as a variable). Next try a different HDMI cable, and as a last resort try a different dock. If you know someone else with their own deck you can try theirs to eliminate a hardware failure on your deck.

Slows down then freezes sure sounds like an out of memory situation, so to add to yours here they might actually want less swap. Sometimes you would rather hit the oom killer sooner instead of waiting on swap to fill.

Ideally login via SSH from another machine to figure out what is using the memory (hopefully the system is responsive enough for SSH), and if it is your critical programs causing the problem then you should consider a memory upgrade.

Contrary to a lot of posts that I have seen, I would say ZFS isn't pointless with a single drive. Even if you can't repair corruption with a single drive knowing something is corrupt in the first place is even more important (you have backups to restore it from right?).

And a ZFS still has a lot of features that are useful regardless. Like snapshots, compression, reflinks, send/receive, and COW means no concerns about data loss during a crash.

BTRFS can do all of this too and I believe it is better about low memory systems but since you have ZFS on your NAS you unlock a lot of possibilities keeping them the same.

I.e. say you keep your T110ii running with ZFS you can use tools like syncoid to periodically push snapshots from the Optiplex to your T110.

That way your Optiplex can be a workhorse, and your NAS can keep the backup+periodic snapshots of the important data.

I don't have any experience with TrueNAS in particular but it looks like syncoid works with it. You might need to make sure that pool versions/flags are the same for sending/receive to work.

Alternatively keep that data on an NFS mount. The SSD in the Optiplex would just be for the base OS and wouldn't have any data that can't be thrown away. The disadvantage here being your Optiplex now relies on a lot more to keep running (networking + nas must be online all the time).

If you need HA for the VMs you likely need distributed storage for the VMs to run on. No point in building an HA VM solution if it just moves the single point of failure to your NAS.

Personally I like Harvester, but the minimum requirements are probably beyond what your hardware can handle.

Since you are already on TrueNAS Scale have you looked at using TrueNAS Scale on the Optiplex with replication tasks for backups?

Credit unions use the NCUA instead of FDIC. So if they don't go after that as well there are still some options.

https://spotifyshuffler.com/

You can use sites like these to randomize your playlist. You can have it randomize the playlist or create a randomized copy if you want to keep the original.

I usually start the playlist, turn on their crappy shuffle to get me to a random position in the randomized playlist, then disable their ~~profitability maximizer~~ shuffle.

Very much agree. BoTW is a good game and definitely worth playing but it isn't a great game. My biggest gripe with it is that there is clearly a RPG leveling/XP system that they desperately try to hide. They don't want to be an RPG but it is difficult for an open world game to not use those mechanics.

So once you realize this you ask yourself why am I breaking all of these weapons just to get more weapons when the only outcome is that the enemies get harder. Blood moons are probably just world resets when you go up a level, which also makes higher level enemies appear.

They also very apparently apply this to the rain patterns as well. Right away I went all in on exploring and getting shrines to increase stamina because it sure is handy to be able to climb large cliffs to explore the map. But I didn't actually do much fighting during that time. Once I had stamina maxed and started just playing and clearly as I leveled up the chances of rain as soon as you approached a cliff side went up considerably making all of that work feel worthless.

The end result was that playing more just meant things got worse, instead of a normal RPG where leveling up meant you gained abilities/stats instead the world just got harder. Sure the weapons got better but once you have the master sword you are always using that first and the harder the enemies get the less effective it is since its stats don't change.

The game also has some serious balancing issues with those levels. Until you get protective clothing it see a like nearly every enemy does exactly your health minus one heart in damage. Have 8 hearts? Ehh 7 of those don't matter if you weren't at 100% health you are dead anyways. Go through shrines to increase those hearts? Doesn't matter enemies still nearly one shot you every time. Easily rectified if you buy/upgrade armor but if you are a cheap bastard like me and don't want to spend money on items that might not be useful you end up playing quite a while before you understand that the deck is stacked against you.

Also in general the map is very lifeless, and there is so little variation in enemies. They certainly are limited by the WiiU/Switch so can't fault them too much on that front.

ToTK fixes a lot of problems compared to BoTW but using the same map feels like it should have been DLC. Everything above/below the map feels like they just told an intern here is your spot go make a change in this area without having to make a change to the old map. And the story line feels very copy+paste from BoTW (go fight the four things in the four corners then go kill the big bad).

Obviously the devices you can make and the increased variation in enemies fixes a lot of the complaints with BoTW, and helps keep you engaged with the game.

ZD has a top tier storyline, but you need to be the type that cares about that to get the most out of it. I suspect most of the folks that don't like Horizon are the type that don't bother to listen to the audio files/read the text messages which really fills out the story. Gameplay is good but gets a little repetitive towards the end (once you are grinding thunderjaws for fun on very hard everything else is just too easy). Some enemies are just variations but the variations change how you approach fighting them.

HFW the story isn't nearly as good (still good but HZ is a high bar), but the variations in enemies and how you have to fight them is much better. If you are trying to get end game weapons the grind is a bit too much. Do yourself a favor and just change to story mode difficulty so you don't have to waste hours of your time fighting the same enemies. If you just want to explore/fight across a huge beautiful map HFW is great for that.