Will boot rollback work just as well/poorly regardless of where the system dataset is?

[depasseg]

With all the issues with the latest 9.10-U1 update, I started thinking about the impacts of having the system dataset somewhere other than on the boot device. I thought I saw something about the config db getting updated and didn't get rolled back, which could be understandable if the config db is in the system dataset, and the system dataset doesn't also get rolled back when the boot environment does.

1. Will a boot rollback work just as well/poorly regardless of where the system dataset is?
2. What's actually in the system dataset?

 

[danb35]

What's actually in the system dataset?

Logs, config backups, and rrd data, at least. I don't think the current config is there, though.

Edit: zfs list | grep system should give a pretty good idea, though.

 

[Ericloewe]

I don't think the current config is there, though.

Just backups, I think.

Logs, config backups, and rrd data, at least.

Samba persistent stuff. I have no idea what kind of stuff, exactly, but that was the main impetus for creating the .system dataset.

1. Will a boot rollback work just as well/poorly regardless of where the system dataset is?

I think rollbacks in newer versions (since late 9.3) act properly and ignore the .system dataset.