Search results

Generally you need more than 3 and odd amount of MONs to provide a reliable majority quorum all the time; other daemons are not picky, and usually one spare will do fine. In all cases I advise you to read the documentation of ceph about the redundancy suggestions of the specific daemons, but...

Ok, that was what I was wondering. Tomas vs. regex 0:1 :) I have patched mine so I'm okay, thank you. Well I see only the web interface and it gave no hint nor history; I try not to touch git if possible since I dislike it pretty much, but no offense, just mentioning that it seems the code...

Indeed, there is no real good answer, apart from the generic "copy your whole storage to another node by your preferred means and connect it to the cluster and migrate your nodes over". As for the ceph part: adding new OSDs to a ceph cluster shall be relatively painless. You can create new OSDs...

I was fighting to create an already tested state of: "a group [member] who can only manage users within the group foo" and kept failing, and I was thinking it's me: # pveum acl modify /access/realm/pve -groups vmadmin -roles PVEUserAdmin 400 Parameter verification failed. path: invalid ACL path...

There are numerous times when PVE chokes, the UI become gray, all tasks stuck, system gets in iowait, unresponsive, gets on fire and explode. Most of the time it requires some services to be restarted, usually after the culprit is found and eredicated, be that some STOP tasks never stopping but...

Then it's just a suggestion to mention this in the documetation, since, as we all know CT online migration is impossible, so such a restart requires a reboot of all the CTs.

How to restart lxcfs, or, rather, how to resurrect /proc on running containers? If lxcfs gets restarted by some or other reason all the CT's get choked: # ps awuxf Error: /proc must be mounted To mount /proc at boot you need an /etc/fstab line like: proc /proc proc defaults In...

The latest GC seems to handle this properly, and the root of the problem (missing chunks) seems to be fixed as well.

You're right, "large" is subjective. The one in question is 2.6 TB with about 18 million files. There may be some relevant factors here: full filesystem traversal time (have to be done in all cases) stat()'ing the file (also had to be done to see incrementality based on update time) reading...

On my Large container the pbs takes 25 hours now. The same contaner with backuppc (incremental, rsync) takes about 90 minutes. Backing up a VM image is fast. (Non-incremental backuppc take 12 - 40 hours.) It seems pbs could use a feature where files with old atime/mtime would be skipped.

@t.lamprecht since it's persisting, see also https://bugzilla.proxmox.com/show_bug.cgi?id=3035

It is not clear to me how lxcfs error related to container config but anyway, I have only unprivileged CTs, and have this spamming error for quite a while now. Tracking it back there was a reboot (due to various network problems and, eventually, getting fenced) and after reboot and start and...

Yes, and and it fails first usually: 2020-09-07T00:00:32+02:00: TASK ERROR: Unable to open dynamic index "/mnt/datastore/pub/ct/106/2020-08-20T22:22:02Z/root.pxar.didx" - No such file or directory (os error 2) Then comes again in 1 minute and report a lot of missing chunks. Probably killing...

So, I have pruned all the backup for the specific container, and a whole [new] backup was created. Started verification. It ran for a few hours then started to find errors, again, though much less in numbers. I really wonder what and when deletes these chunks, since it seems to consistently...

It seems that the problem is not in the container but the method itself; I suspec that somewhere in the snapshotting the FS gets an inconsistent snapshotted state and the backup complains. Visibly the inconsistent files are recent ones and there is no reason to have any problem there, and a...

Exactly same happened to me. PVE openvz created a tgz while pct cannot handle it, only tar.gz.

Apologies if I should have detailed what I meant. Let me: There is two side of pbs+pve backup process: the pve sender and the pbs receiver side. On the sender side the total volume may be known, especially if vzdump made a snapshot, so percentages ("progress") can be calculated. I don't...

Would it be good to have some progress bar for running backups? Right now I've got a CT showing "created new dynamic index 2" for 20+ hours....

Sure, and I'm pretty sure it will be fixed then. That's the only way right now to fix it anyway.... Hmm, I am not sure this GC looks very promising though: 2020-09-01T21:32:46+02:00: Removed bytes: 8824296342 2020-09-01T21:32:46+02:00: Removed chunks: 4177 2020-09-01T21:32:46+02:00: Pending...

Interesting to read it: lot have changed, something not at all. My personal opinion: I still try to avoid ZFS since it still has that weird aura that some bugs are unfixed for years now, and it's still an external kernel sidecar which still occasionally became uncompilable and have to wait for...