> What do *you* mean by flexible in this context ?
> ZFS Crypto is by design extensible to new crypto algorithms and modes.
> It is also designed to allow for multiple different key management
> strategies and implementations, and in fact is explicitly a multiple
> phase project for this reason
Thanks for your answers so far.
> Yes the pools are properly dealt with on a reboot.
> What makes you think
> this wouldn't be the case ? Do you have a specific
> case where you
> believe it has failed ?
Well, I have to admit I only played around a little bit with zfs-fuse so far.
And I don'
not available wrote:
> But there are some points I have problems with:
> - What happens to the pools if the machine is shut down and rebooted? Are the
> pools automatically exported and imported again on boot up? Where is the
> information about the pools kept? What component is responsible for a
not available wrote:
> - What about data wiping? Simply overriding does not work because of the COW
> policy. So how can it be achieved? I think it should be considered to
> integrate some mechanism to intentionally override data.
See the archives of this list, there was a very long discussion a
Hello,
I have read much about ZFS and I find it great, especially the checksums
against silent data corruption and the COW writing policy and the snapshots and
of course the storage pooling.
But there are some points I have problems with:
- What happens to the pools if the machine is shut down an
