mistermanko
Guru
- Joined
- Jan 27, 2020
- Messages
- 577
Something's happend after a replication task ran and somehow deleted 2 absolutely unaffiliated datasets including the snapshots(logically) on the target pool.
I just don't really know why and how the gui did not warn me about it.
So this was the initial situation, my mainpool got into unhealthy state because there were some write errors (like 3 across 3 disks). Smartctl -A on all disks looked fine, minutes before I ran the troubled replication, which is why I ignored the unhealthy state. Layout looks like that:
I setup the task to execute in /mnt/mainpool and not how I intended in /mnt/mainpool/backups.
After starting the task, I was warned about how "encrypted datasets can only be replicated to another encrypted datasets" if I recall correctly. Because I did a similar replication setup before, I was familiar with that warning, though it did not state any data loss was imminent.
So the task started and while stuck at 0% I immediately noticed two datasets missing from mainpool. The GUI showed it to look like this:
I have trouble to understand how that could have happend. I read somewhere that replication into the root of the pool could lead to data loss, but I really don't understand why. I was under the impression, that replication always creates the datasets it replicates if not present at the destination, because it's really only snapshots that are transferred.
I somewhat hope that a scrub right after I noticed the missing datasets will eventually bring the lost ones back... let's see
I just don't really know why and how the gui did not warn me about it.
So this was the initial situation, my mainpool got into unhealthy state because there were some write errors (like 3 across 3 disks). Smartctl -A on all disks looked fine, minutes before I ran the troubled replication, which is why I ignored the unhealthy state. Layout looks like that:
- mainpool (unhealthy)
- media
- backups
- dump
- nextcloud
- jailpool (encrypted)
- data1
- data2
- data3
- mainpool (unhealthy)
- media
- backups
- jailpool (encrypted)
- data1
- data2
- data3
- jailpool (encrypted)
- dump
- nextcloud
- jailpool (encrypted)
- data1
- data2
- data3
I setup the task to execute in /mnt/mainpool and not how I intended in /mnt/mainpool/backups.
After starting the task, I was warned about how "encrypted datasets can only be replicated to another encrypted datasets" if I recall correctly. Because I did a similar replication setup before, I was familiar with that warning, though it did not state any data loss was imminent.
So the task started and while stuck at 0% I immediately noticed two datasets missing from mainpool. The GUI showed it to look like this:
- mainpool (unhealthy)
- backups
- nextcloud
I have trouble to understand how that could have happend. I read somewhere that replication into the root of the pool could lead to data loss, but I really don't understand why. I was under the impression, that replication always creates the datasets it replicates if not present at the destination, because it's really only snapshots that are transferred.
I somewhat hope that a scrub right after I noticed the missing datasets will eventually bring the lost ones back... let's see