<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Insufficient storage in Firewall and Security Management</title>
    <link>https://community.checkpoint.com/t5/Firewall-and-Security-Management/Insufficient-storage/m-p/174162#M31699</link>
    <description>&lt;P&gt;I have a customer running R80.40 VSX clusters on 7k appliances (about 25 VS).&lt;/P&gt;&lt;P&gt;lv_current on one of the members was exhausted and they couldn't push a change. They found some old files they could delete, enough to claw back about 2GB so the changes could be applied.&lt;/P&gt;&lt;P&gt;The root partition has been gradually filling since install and TAC advise there are no other files that can be deleted to recover space - they recommend extending lv_current by 15-20GB which will also increase the upgrade volume and eat into available snapshot space.&lt;/P&gt;&lt;P&gt;While LVM is familiar to engineers, I'm trying to understand why this level of maintenance should be necessary on a device sold as an appliance. Wouldn't it make more sense to size the physical disk and volumes sufficient for normal operations for the life of the appliance, or automate disk optimisation like my TiVo did in 1999?&lt;/P&gt;&lt;P&gt;Disk space (or lack of it) appears to be a common source of frustration here.&lt;/P&gt;</description>
    <pubDate>Thu, 09 Mar 2023 06:06:30 GMT</pubDate>
    <dc:creator>cosmos</dc:creator>
    <dc:date>2023-03-09T06:06:30Z</dc:date>
    <item>
      <title>Insufficient storage</title>
      <link>https://community.checkpoint.com/t5/Firewall-and-Security-Management/Insufficient-storage/m-p/174162#M31699</link>
      <description>&lt;P&gt;I have a customer running R80.40 VSX clusters on 7k appliances (about 25 VS).&lt;/P&gt;&lt;P&gt;lv_current on one of the members was exhausted and they couldn't push a change. They found some old files they could delete, enough to claw back about 2GB so the changes could be applied.&lt;/P&gt;&lt;P&gt;The root partition has been gradually filling since install and TAC advise there are no other files that can be deleted to recover space - they recommend extending lv_current by 15-20GB which will also increase the upgrade volume and eat into available snapshot space.&lt;/P&gt;&lt;P&gt;While LVM is familiar to engineers, I'm trying to understand why this level of maintenance should be necessary on a device sold as an appliance. Wouldn't it make more sense to size the physical disk and volumes sufficient for normal operations for the life of the appliance, or automate disk optimisation like my TiVo did in 1999?&lt;/P&gt;&lt;P&gt;Disk space (or lack of it) appears to be a common source of frustration here.&lt;/P&gt;</description>
      <pubDate>Thu, 09 Mar 2023 06:06:30 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/Firewall-and-Security-Management/Insufficient-storage/m-p/174162#M31699</guid>
      <dc:creator>cosmos</dc:creator>
      <dc:date>2023-03-09T06:06:30Z</dc:date>
    </item>
    <item>
      <title>Re: Insufficient storage</title>
      <link>https://community.checkpoint.com/t5/Firewall-and-Security-Management/Insufficient-storage/m-p/174205#M31704</link>
      <description>&lt;P&gt;Disk space (or lack of it) appears to be a common source of frustration in every imaginable scenario: No matter how big, any HD will have insufficient storage sooner than expected 8)&lt;/img&gt;.&lt;/P&gt;
&lt;P&gt;CP appliances supported life time is from 6 up to 11 years for HIgh End DC.&lt;/P&gt;</description>
      <pubDate>Thu, 09 Mar 2023 10:48:21 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/Firewall-and-Security-Management/Insufficient-storage/m-p/174205#M31704</guid>
      <dc:creator>G_W_Albrecht</dc:creator>
      <dc:date>2023-03-09T10:48:21Z</dc:date>
    </item>
  </channel>
</rss>

