<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>sysadmin on daphnia</title>
    <link>https://blog.daphnia.pw/tags/sysadmin/</link>
    <description>Recent content in sysadmin on daphnia</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en</language>
    <lastBuildDate>Tue, 08 Jul 2025 02:19:00 +0300</lastBuildDate><atom:link href="https://blog.daphnia.pw/tags/sysadmin/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Proxmox</title>
      <link>https://blog.daphnia.pw/posts/2025-proxmox_increase_the_size_of_backup_partition/</link>
      <pubDate>Tue, 08 Jul 2025 02:19:00 +0300</pubDate>
      
      <guid>https://blog.daphnia.pw/posts/2025-proxmox_increase_the_size_of_backup_partition/</guid>
      <description>Problem encountered I had a proxmox server locally running with a disk space of roughly 4TBs. The time came to analyze an unsually large disk image (~1TB). However, by default, when you install a proxmox server, two partitions are created: local and *local-lvm&amp;quot;:
local is usually automatically assigned ~90-100GB, and this partition is where the root (&amp;quot;/&amp;quot;) is mounted. local-lvm gets all the remaining space left on your server.
local is a regular directory, and thus you can store any files or folders you want there (containers&amp;rsquo; and VM&amp;rsquo;s backup, IS files, etc.</description>
    </item>
    
  </channel>
</rss>
