Re: [CentOS] KVM vs. incremental remote backups
On 3/31/21 12:50 PM, Nicolas Kovacs wrote: The problem with using Rsnapshot on the VM's filesystems rather than backing up the whole VM is the time it takes to restore all the mess. All the same, backing up the VM filesystem from within the VM is the best way to back them up using rsnapshot. rsnapshot's approach of hard links and rsync necessarily means that each time a file changes, the copy in the backup set consumes the entire file size if any byte in the origin file has changed. If you're backing up VM images, you're giving up all of the efficiency that rsnapshot was designed for. I'd note that your original message said that you were transferring the entire VM image. That *shouldn't* be the case. rsync should be transferring only the changed bits over the network, but on disk you'll have an entirely new file. There are a few ways you can work around that with rsnapshot, but I'm not aware of an easy solution. One option would be to use btrfs as your backup volume and write wrapper scripts for cmd_cp and cmd_rm. Rather than the default behavior, you'd want to create a snapshot (for cmd_cp) and remove snapshots (for cmd_rm). The other option that comes to mind would be to use either XFS or btrfs as your backup volume and write a wrapper script for cmd_cp. This would be simpler, the script would just be: #!/bin/sh exec cp --reflink=always "$@" If you pursued either option, you'd want to modify the rsnapshot rsync_long_args setting, and add --inplace. Those two approaches would take advantage of CoW filesystem capabilities to conserve disk space. If you decide to pursue them, bear in mind that "du" will report that each of the resulting VM images are full size, even though that's not really the case. The only way (that I know of) to accurately measure disk use will be to run "df" before a backup and after, and compare the disk use of the filesystem. ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] RHEL/Centos 8 power off issue
So I tried a few things, I have a few docking stations, and they all seem to show that problem. Can't shut it down, remotely, while in a docking station. Also, when in a docking station and using the laptops keyboard and LCD screen, and power down the laptop in RHEL/Centos, just results into a reboot. It does that with RHEL/Centos 7 and 8. When I boot it with Centos 6, the behaviour is as expected, it just shuts down. So I guess this issue was "introduced" after Centos 6 somewhere? thanks, Ron On 3/28/21 9:17 PM, R C wrote: Hello, I have a laptop, in a docking station. When running RHEL/Centos 7 I could shut it down and power it off by using 'shutdown -h now' In did a new install of Centos 8 (and also RHEL 8) and when I do a "shutdown -h now" it just reboots (behaves the same as if I'd do a reboot). Is that a known issue? thanks, Ron ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] older versions of Centos
thanks!, Ron On 4/3/21 4:06 PM, Frank Cox wrote: On Sat, 3 Apr 2021 15:58:08 -0600 R C wrote: is there an archive where ISOs of older versions of Centos are kept? https://vault.centos.org/ ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] older versions of Centos
On Sat, 3 Apr 2021 15:58:08 -0600 R C wrote: > is there an archive where ISOs of older versions of Centos are kept? https://vault.centos.org/ -- MELVILLE THEATRE ~ Real D 3D Digital Cinema ~ www.melvilletheatre.com ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
[CentOS] older versions of Centos
Hello, is there an archive where ISOs of older versions of Centos are kept? thanks, Ron On 4/3/21 9:55 AM, Strahil Nikolov via CentOS wrote: Have you checked with 'semodule -DB' ? Source: Chapter 5. Troubleshooting problems related to SELinux Red Hat Enterprise Linux 8 | Red Hat Customer Portal | | | | || | | | | | Chapter 5. Troubleshooting problems related to SELinux Red Hat Enterprise Linux 8 | Red Hat Customer Portal The Red Hat Customer Portal delivers the knowledge, expertise, and guidance available through your Red Hat subscription. | | | | Best Regards,Strahil Nikolov On Thu, Apr 1, 2021 at 14:43, Radu Radutiu wrote: Hi, I'm upgrading our request tracker from Centos 7 to 8 and found some unexpected SELINUX issues with procmail. Even after I create a policy which allows all denied operations, procmail is still not allowed to run a perl script (in my case rt-mailgate). I get the following error in the procmail log: "Can't open perl script "/opt/rt5/bin/rt-mailgate": Permission denied" but I have no denied audit entry in /var/log/audit/audit.log. If I set selinux to permissive, everything works fine. Any idea how to debug this? Best regards, Radu ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] SELINUX blocks procmail from executing perl script without logging
Have you checked with 'semodule -DB' ? Source: Chapter 5. Troubleshooting problems related to SELinux Red Hat Enterprise Linux 8 | Red Hat Customer Portal | | | | || | | | | | Chapter 5. Troubleshooting problems related to SELinux Red Hat Enterprise Linux 8 | Red Hat Customer Portal The Red Hat Customer Portal delivers the knowledge, expertise, and guidance available through your Red Hat subscription. | | | | Best Regards,Strahil Nikolov On Thu, Apr 1, 2021 at 14:43, Radu Radutiu wrote: Hi, I'm upgrading our request tracker from Centos 7 to 8 and found some unexpected SELINUX issues with procmail. Even after I create a policy which allows all denied operations, procmail is still not allowed to run a perl script (in my case rt-mailgate). I get the following error in the procmail log: "Can't open perl script "/opt/rt5/bin/rt-mailgate": Permission denied" but I have no denied audit entry in /var/log/audit/audit.log. If I set selinux to permissive, everything works fine. Any idea how to debug this? Best regards, Radu ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
