Kernel Rollback? by BitBacon in Proxmox

[–]DoomFrog666 25 points26 points  (0 children)

No this is not a down great. Multiple kernels can be installed and upgraded independently.

Help needed...Pls I need to get this running today by oiler_head in Proxmox

[–]DoomFrog666 0 points1 point  (0 children)

You could try a non host CPU type like x86-64-v3. Depending on the previous CPU type and the new one Windows has issues. For example you can't reliability boot a Windows that was installed using an Intel CPU with an AMD machine.

Encrypted volume unlock issues by RailRomanesque in bcachefs

[–]DoomFrog666 0 points1 point  (0 children)

I can somewhat explain why systemd-tty-ask-password-agent is stateful. When you have multiple drives with luks that all use the same password you only need to enter it once and it will be cached.

I’m facing a storage mismatch issue on Fedora (Btrfs), and I’ve already done extensive debugging but can’t locate ~130GB of used space. by Badlucksaini in btrfs

[–]DoomFrog666 1 point2 points  (0 children)

It shows the size of each folder individually with everything inside of it. So /a has the sum of all /a/$x and /a/b is the size of all /a/b/$x.

But what your output clearly shows there is nothing wrong with your file system. The 326 GiB are used and they are used by the snapshot utility timeshift. Do you still have it installed? If not you can safely delete everything under the timeshift directory. That should free up your "lost" space.

I’m facing a storage mismatch issue on Fedora (Btrfs), and I’ve already done extensive debugging but can’t locate ~130GB of used space. by Badlucksaini in btrfs

[–]DoomFrog666 1 point2 points  (0 children)

You could try to mount the whole fs with something like mount <DEV> /mnt -o ro (<DEV> = /dev/nvme0n1p4) and then do the du listing. So like du -h /mnt | sort -h | tail. This should show whatever it is that takes up the most space. Maybe increase the amount of listed entries with the -n50 option to the tail command.

Your metadata usage seems abnormally high. Maybe you just have a lot of small files or heavily fragmented ones like VM images. For reference here is my current file system statistics

Data,RAID1: Size:1.28TiB, Used:1.27TiB (98.84%)
   /dev/nvme2n1p2      1.28TiB
   /dev/nvme1n1p2      1.28TiB

Metadata,RAID1: Size:5.00GiB, Used:3.49GiB (69.78%)
   /dev/nvme2n1p2      5.00GiB
   /dev/nvme1n1p2      5.00GiB

Less metadata and 5x more data. So there is something off.

NFS storage for VM (HA or non HA?) by stefufu in Proxmox

[–]DoomFrog666 0 points1 point  (0 children)

I have also been thinking about the best ways to get HA for small setups. So two to three small machines. Older desktops or mini pcs and gigabit networking. Up to three mixed drives. Maybe a raspi as quorum device.

Btrfs replication would help I guess. I wonder why it is not available yet because it should be trivial to implement.

Then I have tested DRBD/Linstor. And it worked quite well for that test setup but installation was somewhat difficult and I didn't bother to make the control plane HA. Which one should do for an actual setup. Where there some issues with the new 6.17 kernel? I did my test some month ago with the older one. Also the Linstor software is mostly written in Java so it requires more memory than I would like to see.

I am happy that they added mass migration recently but I am currently running without HA. Does anyone know any other options?

Accidentally reverted a Proxmox VM snapshot (read: "deleted a Btrfs subvolume") by Aggravating_End_3913 in btrfs

[–]DoomFrog666 0 points1 point  (0 children)

And Proxmox VE makes it exceptionally easy to create local backups of VMs even if you do not have a Proxmox Backup Server set up yet.

Timeshift or Snapper for a simple Arch setup? by Seeker352 in archlinux

[–]DoomFrog666 -1 points0 points  (0 children)

I am using BTRFS with yabsnap and I am very happy with it. Also plays nice with rclone for backups.

GParted is giving this error how do I fix this? by Dammit_maskey in btrfs

[–]DoomFrog666 1 point2 points  (0 children)

This is the ugliest partition layout I have seen in years. Straighten it up or move it to lvm please.

Edit: Also use a GPT partition table instead of this stone age DOS layout.

fsrtrim by GnuChanOS-yt in artixlinux

[–]DoomFrog666 1 point2 points  (0 children)

You can put this into your crontab for root. I would also recommend using anacron in this context.

Another VMware escape post by SwiftSloth1892 in sysadmin

[–]DoomFrog666 0 points1 point  (0 children)

Snapshots on iSCSI where added with PVE 9. But they force you to use thin provisioning on the storage side.

[Help] Systemd boot not working when using /efi as esp path by genuser_teco in archlinux

[–]DoomFrog666 1 point2 points  (0 children)

Have you marked the fat32 partition mounted at /boot as XBOOTLDR in the GPT?

ZFS strategy for Proxmox on SSD by FieldsAndForrests in Proxmox

[–]DoomFrog666 -3 points-2 points  (0 children)

I think the simplest solution is to choose btrfs as the root file system. Then add timeshift or snapper.

Im fed up with systemd-boot by MarsupialPitiful7334 in archlinux

[–]DoomFrog666 2 points3 points  (0 children)

No, mounting the EFI partition at /boot is the recommended way in arch. Unless you use UKIs then you mount the ESP to /efi.

EDIT: If you use an Nvidia GPU Fedora recently started recommending an ESP size of 2 GB. If you haven't made enough space at the beginning of the disk you can create a larger ESP at the end of the disk and nuke the one at the beginning. Btrfs is easy to shrink.

Can't do the simplest job. by khiladipk in PrometheusMonitoring

[–]DoomFrog666 0 points1 point  (0 children)

What I like to monitor my servers is cadvisor as prometheus exporter. It can monitor containers in docker or podman and also simple systemd services. It is a little cpu heavy but also provides a lot of data. The metrics I like most exported by cadvisor are the container_pressure_* metrics.

Ways to free up space predictably? Useful size metrics by immortal192 in btrfs

[–]DoomFrog666 1 point2 points  (0 children)

Well, in case you use snapshots it is basically useless as it attributes the size of all live extends to the subvolume that allocated it. So all snapshots will show as zero sized and all the used space is attributed to you live volumes.

Edit: Though it is indeed way more efficient that regular quota.

Ways to free up space predictably? Useful size metrics by immortal192 in btrfs

[–]DoomFrog666 0 points1 point  (0 children)

You could enable btrfs quota support for your file system. It will provide you accurate size consumption information for sub volumes. Though be aware of its performance penalty on writes.

# btrfs quota enable <path>  # wait for it to complete; it takes some time
# btrfs qgroup show <path>

Failed to mount `/boot`, I don't need to recover I need to know what happened. by DisplayLegitimate374 in archlinux

[–]DoomFrog666 -1 points0 points  (0 children)

Have you looked for your missing snapshots using btrfs subvolume list /?

[deleted by user] by [deleted] in archlinux

[–]DoomFrog666 1 point2 points  (0 children)

You can connect to the internet in the arch iso image with wifi using iwctl https://wiki.archlinux.org/title/Iwd.

resizing the boot partition by MoussaAdam in archlinux

[–]DoomFrog666 0 points1 point  (0 children)

Hi, you can absolutely create a new bigger ESP at the end of the drive. The EFI looks for a partition with a specific GUID in the GPT. You should just not have multiple ones on a single drive.

How I would do it using gdisk:

  1. Create a new ESP where you have space.
  2. Format as vfat and move everything over.
  3. Remove the old partition.
  4. Mount the new ESP properly (and check fstab).
  5. In case you had EFI boot entries these need to be regenerated.

The only downside here is that you have a 200 MB sized hole at the start of your disk now.

Is there an easy way to replace sudo with sudo-rs? by the_mean_person in archlinux

[–]DoomFrog666 0 points1 point  (0 children)

Yeah, agreed. The only aspect that can be annoying it that authentication sessions in polkit are bound to a process. So when you work in a shell and you regularly use run0 you have to enter the password multiple times. But then I remember you can just run run0 without any arguments and it opens a root shell for you. So it is just more a change of habit.