Search results

  1. B

    Amazon S3 compatible ZFS cloud with minIO

    Since the unhashed 'AWS Access ID' and 'Region Value' are link included the anonymity is reduced. Maybe its more a bug than a feature, but nice to have here for some rare situations. The possibilities of MinIO are amazing and for public sharing I will still prefer my Seafile Server (different...
  2. B

    Amazon S3 compatible ZFS cloud with minIO

    mmh... what is about the acceptance factor of these kind of links...
  3. B

    Amazon S3 compatible ZFS cloud with minIO

    Yes, @gea described and tested it, think so, above. Duplicati was only a very first -arch linux- client test against MinIO on OmniOS (napp-it managed) from my side ...
  4. B

    Amazon S3 compatible ZFS cloud with minIO

    Thanks, Test connection worked now by these Duplicati settings: (without 'minio' at Bucket name and adding region, Folder have been created by Duplicati on storage) Furthermore I got errors (about encryption) and warnings (regarding user rights) for running backup, but I think this will miss...
  5. B

    Amazon S3 compatible ZFS cloud with minIO

    thanks, but did it before screenshot, no effect...
  6. B

    Amazon S3 compatible ZFS cloud with minIO

    Ok, first setup was successfully: and MinIO Browser works as expected: But Duplicati fails to connect by "All access to this bucket has been disabled." (same for Amazon AWS SDK) Anyone checked in the same way?
  7. B

    Encrypted ZFS child Filesystem not mounted - napp-it

    still open issue: parent encrypted and child file system are disabled for SMB sharing in napp-it, after reboot parent file system is shared by name -off- via SMB, but still disabled for SMB sharing. Clicking on off for tank1/Data shows that's currently off, because it would be set to -Data-...
  8. B

    Encrypted ZFS child Filesystem not mounted - napp-it

    Sometimes Encryption Setting was missing on creating file system, but it's solved on v. 20.dev 02.may.2020 But for now the settings are doubled: and playing with it creates disagreements: Additional question: If the 'Automount on bootup' is on 'no' at creation of file system, is it...
  9. B

    Encrypted ZFS child Filesystem not mounted - napp-it

    @gea I'm testing here different cases but in regard to encryption feature of ZFS probable scenarios for more users, I believe, to migrate unencrypted to encrypted file systems. May be I'm your beta tester for napp-it handling... ;-)
  10. B

    Encrypted ZFS child Filesystem not mounted - napp-it

    Parent file system: casesensitivity insensitive Child file system: casesensitivity mixed Property on child is determined by source file system (remember replication from old storage), so I should recreate encrypted parent file system and run replication once more...
  11. B

    Encrypted ZFS child Filesystem not mounted - napp-it

    Issue still present on doing exactly these on in-replicated child file system (from different host) only. After reboot, napp-it enables parent AND child files system SMB sharing, parent wasn't SMB enabled any time before on run time, only child as the desired behavior. PS: on a second...
  12. B

    Encrypted ZFS child Filesystem not mounted - napp-it

    Locking/unlocking manually encrypted file system means to operate on parent files system for sure and I have described the SMB option in there. No need to share parent enc files system via SMB from my site. The sharing of parent enc file system wasn't wanted but happened...
  13. B

    Encrypted ZFS child Filesystem not mounted - napp-it

    Still same behavior as mentioned in Post Post #10 when I lock/unlock manually and set 'Remember SMB share: last'. When I choose 'Remember SMB share: off' on lock and unlock afterwards and enable SMB share manually on child enc file system, then it works as expected. Rebooting server keeps SMB...
  14. B

    Encrypted ZFS child Filesystem not mounted - napp-it

    Ok, will test it tomorrow by downloading 20.dev again...
  15. B

    Encrypted ZFS child Filesystem not mounted - napp-it

    @gea do you have any implementation schedule? (don't feel time pressured)
  16. B

    Encrypted ZFS child Filesystem not mounted - napp-it

    @gea request any test assistance as you like...
  17. B

    Encrypted ZFS child Filesystem not mounted - napp-it

    Currently I'm playing with different send and recv option on target side... Done as already mentioned, but find a bug on displaying 'ZFS Filesystems' Bug: starting by column 'SOURCE' there is an offset of -1. This behavior seems the reason why the parent encrypted data set would be SMB...