Anton Starikov
Anton Starikov
assuming I am going to send datasets from read-only mounted pool or via `zdb -B`, then what should be my strategy to properly backup datasets with snapshots? for example: ```...
or, maybe, after all, there is a way to manually alter metaslab(s) and make pool good enough, to mount RW, make recursive snapshots and generate replication stream?
hm. I am working on the script which managed backing up of such read-only pool. But have a problem. Assuming I have multiple snapshots on the dataset, for example ```...
After all, looks like I managed to backup it all in more or less consistent way. Wasted whole day though )
yep, but when you have 16 of them, this is a bit annoying :) at this point I have no idea anymore, which version of firmware they run :)
By coincidence, I was debugging this issue just minutes ago, as I see it also for some time, and it is very annoying. So, story here is simple. If HA...
as a short term solution, I suggest to change this one from logger.error to logger.warn
I can do better, I can give repro :) just publish anything to the topic `homeassistant/sensor/bla-bla-bla` when z2m config has: ``` homeassistant: legacy_entity_attributes: false legacy_triggers: true ``` the only requirement...
Oh, missed that. Look, effectively we have 2 Tset values. One which is calculated by thermostat, and one which is used by boiler. Once we override Tset, then, effectively, we...
Same problem. godaddy definitely changed their login mechanism. Does somebody maintain this code nowadays?