Search results

pool: nvme state: ONLINE scan: scrub repaired 0 in 0h58m with 0 errors on Sun Apr 30 01:23:10 2017 config: NAME STATE READ WRITE CKSUM nvme ONLINE 0 0 0 mirror-0 ONLINE 0 0 0 nvme0n1 ONLINE 0 0...

It isn't rpool. Also, none of this fails until the system is well up (well past initramfs being in play...)

-- Logs begin at Mon 2017-05-01 17:23:05 EDT, end at Wed 2017-05-03 09:12:53 EDT May 01 17:23:06 pve systemd[1]: Starting Import ZFS pools by cache file... May 01 17:23:15 pve zpool[1036]: internal error: Value too large for defined dat May 01 17:23:15 pve systemd[1]: zfs-import-cache.service...

I used /dev/nvme0n1 and /dev/nvme1n1. nvme devices are treated specially, so this was my only option...

Apologies for forgetting that. So... proxmox-ve: 4.4-86 (running kernel: 4.4.49-1-pve) pve-manager: 4.4-13 (running version: 4.4-13/7ea56165) pve-kernel-4.4.35-1-pve: 4.4.35-77 pve-kernel-4.4.44-1-pve: 4.4.44-84 pve-kernel-4.4.49-1-pve: 4.4.49-86 lvm2: 2.02.116-pve3 corosync-pve...

SATA raid1 and NVME raid1. Rebooted. NVME pool not present. Imported manually and all was well. Looked at /var/log/syslog and saw this: May 1 17:23:20 pve zpool[1036]: internal error: Value too large for defined data type May 1 17:23:20 pve systemd[1]: zfs-import-cache.service: main...

Note also that this depends on the cache policy for your VMs. If you use writeback, ARC will be very little used, since the linux page cache will handle things, so in that case, you can leave it at the default. My 128GB server: root@pve:~# free -m total used free...

The installer for 2012 gives you two choices: upgrade or fresh install. From the error screen, it looks like you clicked on upgrade. Do the other option instead.

That depends. In general I agree, but one might have no real choice. Depending on the setup, it might be perfectly safe...

That's very weird. When I played with nfs/pacemaker+corosync last year, it never took more than 15 seconds or so (although that was using vmware, not proxmox, but still...) Don't know what pvestatd is doing here?

I'm confused. Are you trying to create a brand-new windows VM? If so, at the initial CD boot screen, you want to not pick the upgrade, but the other choice (don't remember the name...)

No, you import pools, not disks. e.g. if your pool is called 'tank', then do: zpool export tank zpool import -d /dev/disks/by-id tank

Export the pool, and then re-import it 'the right way'. At that point, it should be in the cachfile and be imported properly on subsequent boots.

No argument there...

Just playing safe. I noticed they run the cache scan service *and* the disk scan service...

I don't know if it is necessary or not, but I also disabled the zfs import by scan service.

That's what I ended up setting. My primary server has 128GB of ram, with plenty free, so it frankly seems silly to have it ever touching swap unless necessary...

This is why I always create the pool manually :)

Bless you, that's the part of the puzzle I was missing :) I just edited the settings for the nvme storage and select 'pve' instead of the default, and now it all works. Yes, it would be nice to have this spelled out a little more clearly. Thanks again!

The NVME pool is a local device, surely you don't suggest I mark it as shared? If so, what's the point of having local storage, if you have to lie about it being shared? I assume this doesn't happen for the default local and local-lvm storage, as any newly installed node has those. I suppose...