Search results

mkdir Documents. Correct command? You make me wondering that I might not loaded the key of this dataset before creating the folder. I will test by removing them and create them again after making sure the key is loaded.

How is it possible that the content (I created some directories in it for testing) of my encrypted dataset 'zpool/edata' is immediately vieweable after reboot (also after shutdown) with reloading the key? As you said I checked the encryption status with 'zfs get all zpool/edata | more' and the...

Okay, but doesn't it work then also when i create a dataset 'data' for all my data incl. virtual machines, where I put the virtual machines in a separate folder in the 'data' dataset. Why is it necessary for making a dedicated dataset for virtual machines?

Anybody can help further?

Sorry but I don't understand where the difference lays between a 'zvol blockdevice' and an 'emulated block device' when creating data sets/ file systems. Also I don't understand at which point the zfs storage is ready for actually storing data on it. Please help whether below steps are...

zvol blockdevices as well as emulated blockdevices can both be encrypted files systems?

Thanks, I think I am getting closer to understand. So also for unencrypted data I need to create datasets. The hierarch is as follow: - Disks - Pool - Dataset - Files and folders Correct? Additionally, how does it come I don’t have to enter password when rebooting system? The files in...

I can read the text file in the encrypted_data data set. But let me ask the question differently. 1) Do I have to create data sets on the pool? Or is the pool ‘zroot’ in my case directly suitable for storage of files? 2) Can I encrypt the pool entirely?

A few questions on ZFS pool creation and encryption. I read the instructions on encryption but I am not sure about the tank/encrypted_data part in the wiki. So better ask. 1) To create the pool I issued 'zpool create -f -o ashift=12 zroot mirror sda sdb -m /mnt/zroot'. I added -m /mnt/zroot...

I have build a new mini server for running Proxmox, i.e.: - ASRock Z390M-ITX/ac motherboard - 32 gb of ram - Intel I7 octa core processor I am migrating from an old hardware configuration and want to place my old dm-crypt encrypted Samsung 1.5 TB harddisks to the new hardware configuration...

Currently I have a fresh install with Proxmox running with OpenMediaVault in a container. Option 1: The idea is to have the Proxmox host take care of the ZFS file system and than share directories via 'bind' with the OpenMediaVault container. Is this possible? Other options I am considering...

I read somewhere that 8 GB of RAM is recommended, that's basically the guidance I intended to follow.

After long hesitating: Mini-pc and Synology NAS vs. custom build pc with Proxmox and Virtual NAS (probably OpenMediaVault). I will go for the latter option. Just wanted to check whether the setup I am heading for is feasible: 1) I want to install the Proxmox (operating) system to a SSD. 2) 2 or...

Thanks for the responses providing me knowledge about ZFS :-). But my basic question in the initial post whether you would recommended option 1 or option 2, i.e. option 1 self-build mini-ITX system as virtualization and NAS solution combined or option 2 mini-PC for virtualization purpose and...

My intention is to use ZFS for user data. Or is ZFS not suitable for that purpose?

So if I understand correctly with ZFS if one disk of the two disk fails I still have my data? And adding a new disk will rebuild the "RAID-1 mirror"? Sounds great! Than of course I will go for option 1 without Synology. So in my setup ZFS runs on top of LUKS? Or does not ZFS provides some native...

Currently I have a custom build system on which I run Proxmox, providing two functionalities: - The virtualization environment for personal LAB purposes - Proxmox host operating system also for 'NAS'/ file server services, i.e. based on SAMBA and LUKS encryption. Now the system is up for...

Yes, they are both from the same network class. Solving this issue I ran into another problem. After issuing apt-get update && dist-upgrade Proxmox it hang forever on the following line: - update-initramfs: Generating /boot/initrd.img-2.6.32-34-pve I had to interrupt the process and issue dpkg...

See output below. I notice that I not upgraded to 3.3 yet. I issued apt-get update && upgrade, instead of apt-get update && dist-upgrade. Running apt-get dist-upgrade right now. proxmox-ve-2.6.32: 3.1-114 (running kernel: 2.6.32-26-pve) pve-manager: 3.1-24 (running version: 3.1-24/060bd5a6)...

I use vnet for OpenVZ containers but it seems that during updating to later Proxmox host versions (currenlty on latest 3.1-24 ) the containers have no internet connectivity anymore. KVM machines on the same host still have internet connectivity with no problems. Suggestions?