<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	
	>
<channel>
	<title>
	Comments on: 10 Tools to Monitor Linux Disk Partitions and Usage in Linux	</title>
	<atom:link href="https://www.tecmint.com/linux-tools-to-monitor-disk-partition-usage/feed/" rel="self" type="application/rss+xml" />
	<link>https://www.tecmint.com/linux-tools-to-monitor-disk-partition-usage/</link>
	<description>Tecmint - Linux Howtos, Tutorials, Guides, News, Tips and Tricks.</description>
	<lastBuildDate>Mon, 09 Oct 2023 06:11:03 +0000</lastBuildDate>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	
	<item>
		<title>
		By: dragonmouth		</title>
		<link>https://www.tecmint.com/linux-tools-to-monitor-disk-partition-usage/comment-page-1/#comment-1506883</link>

		<dc:creator><![CDATA[dragonmouth]]></dc:creator>
		<pubDate>Wed, 26 May 2021 17:46:45 +0000</pubDate>
		<guid isPermaLink="false">http://www.tecmint.com/?p=23768#comment-1506883</guid>

					<description><![CDATA[A minor quibble about terminology.  All the above commands DISPLAY their output information on the terminal.  The output will be PRINTED only if it is piped into some print function.  PRINT usually refers to hard copy output.

&quot;If your root partition is getting full, you can resize root partition using LVM&quot;
Isn&#039;t that a rather drastic procedure, requiring a total re-organization of all the storage devices on your system?  It would take your system offline for an extended period of time.  Wouldn&#039;t using GParted to resize existing partitions be advisable, quicker, and less error-prone?]]></description>
			<content:encoded><![CDATA[<p>A minor quibble about terminology.  All the above commands DISPLAY their output information on the terminal.  The output will be PRINTED only if it is piped into some print function.  PRINT usually refers to hard copy output.</p>
<p>&#8220;If your root partition is getting full, you can resize root partition using LVM&#8221;<br />
Isn&#8217;t that a rather drastic procedure, requiring a total re-organization of all the storage devices on your system?  It would take your system offline for an extended period of time.  Wouldn&#8217;t using GParted to resize existing partitions be advisable, quicker, and less error-prone?</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		By: Martin de Vries		</title>
		<link>https://www.tecmint.com/linux-tools-to-monitor-disk-partition-usage/comment-page-1/#comment-1314372</link>

		<dc:creator><![CDATA[Martin de Vries]]></dc:creator>
		<pubDate>Sat, 01 Feb 2020 06:57:54 +0000</pubDate>
		<guid isPermaLink="false">http://www.tecmint.com/?p=23768#comment-1314372</guid>

					<description><![CDATA[I don&#039;t call these tools real monitoring tools, because you have them run them manually each time, so you have to do the monitoring yourselves. ]]></description>
			<content:encoded><![CDATA[<p>I don&#8217;t call these tools real monitoring tools, because you have them run them manually each time, so you have to do the monitoring yourselves. </p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		By: Aaron Kili		</title>
		<link>https://www.tecmint.com/linux-tools-to-monitor-disk-partition-usage/comment-page-1/#comment-948026</link>

		<dc:creator><![CDATA[Aaron Kili]]></dc:creator>
		<pubDate>Thu, 14 Dec 2017 08:55:13 +0000</pubDate>
		<guid isPermaLink="false">http://www.tecmint.com/?p=23768#comment-948026</guid>

					<description><![CDATA[In reply to &lt;a href=&quot;https://www.tecmint.com/linux-tools-to-monitor-disk-partition-usage/comment-page-1/#comment-947882&quot;&gt;Jim&lt;/a&gt;.

@Jim

To be honest, there is no single straightforward solution to this issue. And from my own experience, no single site will help you solve an Computer/IT problem. You need to carefully peruse through the web and dig through various resources relating to an issue. 

But first, what machine are you using(Dell, HP, Samsung, etc..)? There could possibly be a problem with your hardware causing you not to access the BIOS, for example the keyboard. The key for accessing the BIOS depends on the settings of the machine manufacturer, you could be using a wrong key. 

 You can contact the machine manufacturer or read manuals or documentations to learn how to access the BIOS, that is if it isn&#039;t corrupted. 

In addition, from the information you provided, i can noticed that you are using LILO boot loader, i personally prefer GRUB/2, you can change from LILO to GRUB2 using this guide:  https://wiki.debian.org/FromLiloToGrub

I hope this will give you a starting point towards solving your issue. In case of any thing, you can always write to us.]]></description>
			<content:encoded><![CDATA[<p>In reply to <a target="_blank" href="https://www.tecmint.com/linux-tools-to-monitor-disk-partition-usage/comment-page-1/#comment-947882">Jim</a>.</p>
<p>@Jim</p>
<p>To be honest, there is no single straightforward solution to this issue. And from my own experience, no single site will help you solve an Computer/IT problem. You need to carefully peruse through the web and dig through various resources relating to an issue. </p>
<p>But first, what machine are you using(Dell, HP, Samsung, etc..)? There could possibly be a problem with your hardware causing you not to access the BIOS, for example the keyboard. The key for accessing the BIOS depends on the settings of the machine manufacturer, you could be using a wrong key. </p>
<p> You can contact the machine manufacturer or read manuals or documentations to learn how to access the BIOS, that is if it isn&#8217;t corrupted. </p>
<p>In addition, from the information you provided, i can noticed that you are using LILO boot loader, i personally prefer GRUB/2, you can change from LILO to GRUB2 using this guide:  <a target="_blank" href="https://wiki.debian.org/FromLiloToGrub" rel="nofollow ugc">https://wiki.debian.org/FromLiloToGrub</a></p>
<p>I hope this will give you a starting point towards solving your issue. In case of any thing, you can always write to us.</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		By: Jim		</title>
		<link>https://www.tecmint.com/linux-tools-to-monitor-disk-partition-usage/comment-page-1/#comment-947882</link>

		<dc:creator><![CDATA[Jim]]></dc:creator>
		<pubDate>Wed, 13 Dec 2017 19:07:16 +0000</pubDate>
		<guid isPermaLink="false">http://www.tecmint.com/?p=23768#comment-947882</guid>

					<description><![CDATA[What site would be good to get actual help on a Linux problem instead of being told all the things Im doing wrong posting my questions in the wrong site? My problem is I cant access my bios and have no splash screen to choose which O/S I want to log into.I will post some basic info here in hopes that you can help or guide me to anyone that can help.

http://paste.ubuntu.com/26178393/

thank you for your help and time.
Jim]]></description>
			<content:encoded><![CDATA[<p>What site would be good to get actual help on a Linux problem instead of being told all the things Im doing wrong posting my questions in the wrong site? My problem is I cant access my bios and have no splash screen to choose which O/S I want to log into.I will post some basic info here in hopes that you can help or guide me to anyone that can help.</p>
<p><a target="_blank" href="http://paste.ubuntu.com/26178393/" rel="nofollow ugc">http://paste.ubuntu.com/26178393/</a></p>
<p>thank you for your help and time.<br />
Jim</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		By: Iulian Murgulet		</title>
		<link>https://www.tecmint.com/linux-tools-to-monitor-disk-partition-usage/comment-page-1/#comment-857353</link>

		<dc:creator><![CDATA[Iulian Murgulet]]></dc:creator>
		<pubDate>Tue, 03 Jan 2017 17:13:07 +0000</pubDate>
		<guid isPermaLink="false">http://www.tecmint.com/?p=23768#comment-857353</guid>

					<description><![CDATA[Your commands example is OK, but sometime, you have some bad luck. And something is wrong with your system. Block-id, uuid are very hard to identify, if I have several hdd/ssd/whatever. 

It could be very difficult to see that /dev/sdX or uuid, is located on xxx device, if I have 2 or more identical hdd/ssd. More simple is to use anywhere (fstab, as a example) /dev/disk/by-id/*.

In this case you will get even the serial-number that is printed to the (any) hdd/ssd label. Try for example this:
&lt;pre&gt;
ls -l /dev/disk/by-id
&lt;/pre&gt;
and you will understand what I am try to say! And you can use fdisk(whatever) /dev/disk/by-id/yyyyy

Less errors and less mistakes (I make a new gpt table on the wrong disk ...)

  Have a nice day, with BY-ID :)]]></description>
			<content:encoded><![CDATA[<p>Your commands example is OK, but sometime, you have some bad luck. And something is wrong with your system. Block-id, uuid are very hard to identify, if I have several hdd/ssd/whatever. </p>
<p>It could be very difficult to see that /dev/sdX or uuid, is located on xxx device, if I have 2 or more identical hdd/ssd. More simple is to use anywhere (fstab, as a example) /dev/disk/by-id/*.</p>
<p>In this case you will get even the serial-number that is printed to the (any) hdd/ssd label. Try for example this:</p>
<pre>
ls -l /dev/disk/by-id
</pre>
<p>and you will understand what I am try to say! And you can use fdisk(whatever) /dev/disk/by-id/yyyyy</p>
<p>Less errors and less mistakes (I make a new gpt table on the wrong disk &#8230;)</p>
<p>  Have a nice day, with BY-ID :)</p>
]]></content:encoded>
		
			</item>
	</channel>
</rss>
