Search results

I did not create the .mgr pool. I suspect that got created during the upgrade. there was something in release notes about mgr ....

# ceph osd pool ls detail pool 48 'nvme-4tb' replicated size 3 min_size 2 crush_rule 4 object_hash rjenkins pg_num 128 pgp_num 128 autoscale_mode on last_change 300736 lfor 0/294914/294912 flags hashpspool,selfmanaged_snaps stripe_width 0 application rbd pool 55 '.mgr' replicated size 3 min_size...

i did not replace the disks, the only thing that changed was to upgrade ceph software. we get emails from zabbix if ceph issues, and only got an email around the time of the upgrade . Also I looked at the ceph section of the pve web page before upgrading and all was OK.

# ceph pg dump_stuck PG_STAT STATE UP UP_PRIMARY ACTING ACTING_PRIMARY 48.7e active+undersized+degraded+remapped+backfilling [1,24,19] 1 [1,24] 1 48.7d active+undersized+degraded+remapped+backfilling...

I have not changed crush rules since 5 years ago.

hello , today I upgraded to the latest ceph. after the first note was upgraded i noticed an inactive pg warning. I continued and finished the upgrade hoping the inactive pg would be fixed with a complete upgrade. But that was not the case. following info from...

have you looked at rsnapshot ? it is good for data snapshots, like hourly, daily , weekly etc . I am not sure if it will do what you want for system.

For some reason on PVE and Nextcloud and other systems log rotation came to a halt in November. /var/log had over 7G . /var/log/journal had 4G i think it has something to do with a conflict with rsyslog and systemd journal stuff. will check later to fix edit /etc/cron.daily/logrotate #...

I'l edit this post sometime.... in the middle of transferring 8T ... I have not tried this.... was researching if resume is possible.. following this https://unix.stackexchange.com/questions/343675/zfs-on-linux-send-receive-resume-on-poor-bad-ssh-connection supposedly as we used the...

thank you Mira, that fixed the warning. rbd -p <pool-name> object-map rebuild vm-160-disk-0 rbd -p <pool-name> object-map rebuild vm-603-disk-0

for some LXC's there have had ' object map is invalid' since about 2020 . the timestamps show these lines are created when a pbs backup occurs. I assume these are harmless. Is there is a simple way to prevent these ? # dmesg|grep rbd | grep inval| grep disk [Fri Nov 4 17:02:54 2022]...

thank you

I am closing this thread and using https://forum.proxmox.com/threads/change-of-proxmox-backup-client-output-makes-cron-annoying.112728/#post-486872

I'm not sure of the syntax. which of these should be used ? export PBS_LOG='error proxmox-backup-client' # or export PBS_LOG='error'

try this: # m5300 auto bond21 iface bond21 alias bond21 on swp21 bond-slaves swp21 clag-id 21 mtu 1500 bond-miimon 100 bond-mode 802.3ad bond-xmit-hash-policy layer3+4 then there are the different macs to use for peerlink.4094 etc.

the config is slightly diff. there are important differences.

here are the /etc/network/interface files for our lagged two switches

I also liked the idea of Debian on a switch - until Nvidia bought Mellonax and dropped software upgrades [ stuck on deban 10 ] for many switches including our two very expensive ones. they are speed 40 and not 100 so just dropped . I could post our working interface files so you have an...

we ended up getting these switches working. what part are you trying to set up?

hello e100. 04:34:46 with bandwidth limit 150G was the fastest backup on the your post today. was that a typo? If not a typo then why not go with 16 workers and bw limit 150? [ yes i should have re read the entire thread .... ]