Search results

It looks like there are different defaults for configuring zfs pools in different versions of ProxMox. I just set up a new v5.3 server from scratch, and when I go to Datacenter->Storage->local-zfs and click Edit, I see that "Thin Provision" is checked, and the Block Size is 8k. Based on what...

So, I think I've stumbled upon something. After reading https://www.delphix.com/blog/delphix-engineering/zfs-raidz-stripe-width-or-how-i-learned-stop-worrying-and-love-raidz and seeing over and over that 6 drives in a RAID-Z2 seems to be a sweet spot, which is exactly what I have, I noticed at...

I'm curious... your zvol shows a referenced value of 6.58GB when your filesystem is 5GB. Where is the extra ~1.5GB being consumed? On my system, the discrepancy is ~2x. Can I really expect a 2TB partition to take up over 4TB of disk space? Here are the "ref" parameters for my partition...

The refreservation property is "none", which seems to me to indicate that the zvol can expand to the maximum size of the pool. The problem arose because the amount of space on the server doesn't match what is expected. I have 6 2TB drives in a RAID-Z2 configuration, so I expect to have 4x2TB or...

I'm having a similar issue and still don't understand the difference between usedbydataset and localused. I have a VM that has TRIM configured, and I've verified that the ZFS subvol actually reports less data being used after issuing a fstrim command in the VM, but the volume is still taking up...

Since I don't have any available SATA ports, putting in the new drive before removing the old drive isn't an option. I've double-checked with "ls" at the boot prompt, and all the disks are there. I've also checked my bios settings to make sure that all of the drives in the array are marked as a...

I'm really not comfortable with this solution. I have to return the existing drive under warranty to get the replacement, and if the system goes down before the new drive is resilvered, I'm back to square one. I feel I really need to get this machine booting with sdb removed.

root@goat:~# pveversion -v proxmox-ve: 4.4-84 (running kernel: 4.4.44-1-pve) pve-manager: 4.4-13 (running version: 4.4-13/7ea56165) pve-kernel-4.4.6-1-pve: 4.4.6-48 pve-kernel-4.4.44-1-pve: 4.4.44-84 lvm2: 2.02.116-pve3 corosync-pve: 2.4.2-2~pve4+1 libqb0: 1.0-1 pve-cluster: 4.0-48 qemu-server...

Also, another data point that may be pertinent: when I set up Proxmox, I found that zfs was referring to my volumes by name (sdb2, sdc2, etc.) and not by vdevs. I posted on the forum and was basically told "if it works, don't worry about it." Is this biting me in the butt now?

I have a 5 drive raidz1 array (sdb,sdc,sdd,sde,sdf) and the smart status on sdb indicates that it's about to fail. My server does not have hot-swap bays so I need to shut down the server to pull out the failing disk. I thought I had installed grub on sdc correctly to assist in this situation...

The setting just says "Default for display" which is 2880x1800 at 2x scaling so it behaves like 1440x900. The symptoms don't change when I change the resolution of the built-in or external non-retina display.

I'm on a MacBook Pro with a 15" retina display at default resolution. Also tried on an external non-retina display at 1920x1080 with the same results.

I'm in the process of migrating from Proxmox 3.3 to 4.2 and I've noticed some minor graphical issues using Safari with 4.2. Virtually all buttons are too small for the text inside them as shown here: Everything seems to work fine with Firefox or Chrome. But in Safari, even if I zoom in or...

I've set up a new instance of Proxmox VE 3.4 using a RAID 1 ZFS volume for the root partition. When I use "zpool status" to look at the status of rpool, it shows that the two member volumes are sda3 and sdb3. I was under the impression that one shouldn't refer to volumes directly, since the...