Search results

As embarrassed as I am to admit it, I actually had this same problem last year and solved it by freeing up inodes due to excessive .vg file creations: https://forum.proxmox.com/threads/excessive-inode-consumption-and-etc-lvm-archive.91868/ What happened is that when I upgraded to Proxmox 7, it...

I have an issue where I cannot create new VM's following what appears to be an otherwise successful upgrade to VE7.2-7. Looking at another thread on what seems to be a related issue, I ran the pvesm status command, which succeeded with the following output: I am able to select an ISO from...

I would also like to point out that I am no longer experiencing the issue now that I have done what I wrote up here (cleared out the excessive inode usage): https://forum.proxmox.com/threads/excessive-inode-consumption-and-etc-lvm-archive.91868/ Is it possible that the lack of inodes available...

pvesm status root@prxmox:~# pvesm status Name Type Status Total Used Available % Store1 nfs active 38193152 49152 36173824 0.13% Data1 nfs active 959853568 509200384...

I had to start another thread about inode issues (https://forum.proxmox.com/threads/excessive-inode-consumption-and-etc-lvm-archive.91868/), so I defer to people who are dealing with Samba inode consumption directly. My research said deleting my .vg files in /etc/lvm/archive was safe; I cannot...

Some of you have probably seen these threads below: https://forum.proxmox.com/threads/apt-get-update-autoremove-failed-no-space-left.91867/ https://forum.proxmox.com/threads/an-help-to-free-inode-usage-on-my-servers.69730/ I am experiencing a similar problem - but not due to Samba. I have...

You are afflicted like many others: https://forum.proxmox.com/threads/an-help-to-free-inode-usage-on-my-servers.69730/ You need to clean out those inodes from Samba.

I believe I am running into the same problem, and I believe you may be out of inodes. Do this: cd / du --inodes -xS | sort -n At the bottom of that list, do you have a large number?

Running into a similar issue. I'm seeing that no one responded to this, but I ran 'pvesm status' to try to keep this going: Only error was that some .vg files were not found. All other storage was listed correctly. Just highlighting that this behavior is being observed by others too...

Just successfully tested on 6.4-8. Please note: - Updated from FreeNAS 11.3 to TrueNAS Core 12.0-U4 - GrandWazoo seems to have made recent updates, so I deleted the freenas-proxmox repo I had cloned and re-cloned it - Appears to be working A-OK

I was able to figure it out. See below if you run into similar issues: The ISCSI service on my FreeNAS-11.2-U8 was initially having trouble restarting after reconfiguring the network. This was due to ISCSI and associated pools still being associated with the prior network configuration...

All, I re-did a lot of the networking on my cluster and appear to have successfully changed everything over to ZFS-over-ISCSI using LACP and Linux bonded interfaces for some throughput improvement and redundancy. I am connecting to a FreeNAS cluster using GrandWazoo's ZFS-over-ISCSI patch...

Thank you sir - I am now tracking. Actually create a share (NFS, for example), and go from there.

Thanks for the reply - why am I not seeing the same content across all the nodes then since they are marked shared? I only the drives listed under the nodes.

Hello all, So I have a 3-node cluster which each server loaded with local hard drives. I want to share the local hard drives across all the systems in the cluster, so I did the following: Used parted to initialize with GPT and create a partition Used mkfs.ext4 to create a filesystem on each...

Again, for the weary, FreeNAS-seeking-but-very-frustrated-because-no-one-actually-wrote-everything-up Proxmox user: I believe I have solved the problem of the "iSCSI: Failed to connect to LUN : Failed to log in to target. Status: Authorization failure(514) " listed above. As a comprehensive...

Updates for the weary Proxmox/FreeNAS Internet traveler: Do not set a password on the SSH key you generate unless you have a way to supply the password every time you need to use the key On this line "Target: IQN on the FreeNAS box and target ID", that means the syntax needs to be of the...

Well, I already solved one problem. I added the target name using the following syntax in the Edit:ZFS over iSCSI dialog box and it created the VM with no errors: iqn.custom-name.net.freenas.ctl:targetname However, I now have these problems when I attempt to start the VM: iscsiadm: No...

I am trying to use a FreeNAS server for shared storage in a 3-node Proxmox cluster to enable HA and live migration. The iSCSI target is set up on a ZFS pool of 4 identical enterprise-grade SSD's and is reporting "healthy" in FreeNAS. I followed the helpful instructions here...