<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
	<channel>
		<atom:link href="https://dev1galaxy.org/extern.php?action=feed&amp;tid=7894&amp;type=rss" rel="self" type="application/rss+xml" />
		<title><![CDATA[Dev1 Galaxy Forum / home directory 100% but acutall there should be 11Gb left of free spac]]></title>
		<link>https://dev1galaxy.org/viewtopic.php?id=7894</link>
		<description><![CDATA[The most recent posts in home directory 100% but acutall there should be 11Gb left of free spac.]]></description>
		<lastBuildDate>Thu, 09 Apr 2026 18:34:51 +0000</lastBuildDate>
		<generator>FluxBB</generator>
		<item>
			<title><![CDATA[Re: home directory 100% but acutall there should be 11Gb left of free spac]]></title>
			<link>https://dev1galaxy.org/viewtopic.php?pid=63130#p63130</link>
			<description><![CDATA[<p>BTRFS interests me a lot, but I have hesitated to use it for years now. If I decide to give it a try, I will probably put <span class="bbc">/home</span> on a separate partition (or disk) and format it as ext4. That way, if BTRFS causes me any serious problems, my data won&#039;t be directly involved.</p>]]></description>
			<author><![CDATA[dummy@example.com (pcalvert)]]></author>
			<pubDate>Thu, 09 Apr 2026 18:34:51 +0000</pubDate>
			<guid>https://dev1galaxy.org/viewtopic.php?pid=63130#p63130</guid>
		</item>
		<item>
			<title><![CDATA[Re: home directory 100% but acutall there should be 11Gb left of free spac]]></title>
			<link>https://dev1galaxy.org/viewtopic.php?pid=63129#p63129</link>
			<description><![CDATA[<p>Hello:</p><div class="quotebox"><cite>matze72 wrote:</cite><blockquote><div><p>Thank you ...</p></div></blockquote></div><p>You&#039;re welcome.<br />It was more a recommendation than anything else.</p><div class="quotebox"><cite>matze72 wrote:</cite><blockquote><div><p>... a german page that seems to fit to my problem ...<br />... something went wrong.<br />... time ti format /dev/sda6.</p></div></blockquote></div><p>I cannot opine on all that.</p><p>All I can say is that every time I have come across the string <span class="bbc">btrfs</span> it is usually associated with a problem.<br />Not all solvable, many fatal.</p><p>As an example, see this thread from a couple of years ago: <a href="https://dev1galaxy.org/viewtopic.php?id=5631" rel="nofollow">https://dev1galaxy.org/viewtopic.php?id=5631</a></p><div class="quotebox"><cite>matze72 wrote:</cite><blockquote><div><p>... is there another option?<br />... wiser to change to ext4 fs instead of btrfs?</p></div></blockquote></div><p>I&#039;ll answer your questions by expressing my point of view* with respect to using filesystems other than the one Devuan uses by default.<br />* which <span class="bbu">does not</span> imply or pretend any wisdom on my behalf. 8^°</p><p>To wit:</p><p>Choosing anything other than the default Devuan <span class="bbc">ext4</span> filesystem implies that you are <span class="bbu">absolutely sure</span> that you have a use case that really <span class="bbu">justifies your doing so</span>, a second implication being that you are sufficiently versed in the options being considered.<br />This (quite obviously) <span class="bbu">also</span> applies to choosing any init package other than the default Devuan <span class="bbc">sysvinit</span>, something of a trend in the last few years.</p><p>From where <em>I</em> see it, keeping the default options is a basic part of the KISS principle.<br />ie: if it works as advertised / needed, is adequately supported and has not given you any grief, use the default.</p><p>In my case as a 100% Linux user for the last 14 years (the last 8 or so with Devuan), I have never (ever) had any isssues with <span class="bbc">sysvinit</span> or <span class="bbc">ext4</span>.</p><p>As always, just my $0.02.<br />YMMV.</p><p>That said and assuming that you have all your data and configurations properly backed up, I&#039;d say that you may want to consider getting rid of <span class="bbc">btrfs</span> and proceed to format whatever disk arrangement you have to <span class="bbc">ext4</span>.<br />ie: <span class="bbu">all</span> the drives, no mixing filesystems.</p><p>Best,</p><p>A.</p>]]></description>
			<author><![CDATA[dummy@example.com (Altoid)]]></author>
			<pubDate>Thu, 09 Apr 2026 17:13:27 +0000</pubDate>
			<guid>https://dev1galaxy.org/viewtopic.php?pid=63129#p63129</guid>
		</item>
		<item>
			<title><![CDATA[Re: home directory 100% but acutall there should be 11Gb left of free spac]]></title>
			<link>https://dev1galaxy.org/viewtopic.php?pid=63127#p63127</link>
			<description><![CDATA[<p>Hello Altoid,</p><p>Thank you for your hint.</p><p>With the expression &quot;ENOSPC&quot; (Error: No space left on device) on the the 2nd link, I found a german page that seems to fit to my problem:</p><p><a href="https://www.slicewise.net/debian/balancierung-eines-vollen-btrfs-dateisystems/" rel="nofollow">https://www.slicewise.net/debian/balanc … eisystems/</a></p><p>According to that it couldbe that btrfs &quot;thinks&quot; the partition is full, bit it isn&#039;t. <br />Caused by btrfs not realesing space that is not needed any more. (it is actually more complicated than that)<br />To solve the problem the size of the blocked partition could be temporary increased, that there is enough space for btrfs and then&#160; balance the fs again:</p><div class="codebox"><pre><code>cd /mnt
mkdir fulldisk
#the &quot;full&quot; btrfs-partition is /dev/sda2
mount /dev/sda2 fulldisk
#add a USB-stick to the &#039;full&#039; btrfs partition
btrfs device add /dev/sdb fulldisk
#balancing
btrfs balance start fulldisk
#remove USB-Stick from btrfs-partition 
btrfs device delete /dev/sdb fulldisk</code></pre></div><p>Well I tried this with the stick that was plugged in wit an antic Live systemand forced the add as I need not the data on the stick any more.</p><p>But something went wrong. Wether I could run the balancing nor could I remove the stick from the btrfs-partition.</p><p>I did a reboot and now the &quot;full&quot; btrfs-partition could not be mounted any more. Also when I try to start a btrfs repair action it aborts with the error message:</p><div class="codebox"><pre><code> root@blechdepp:~# btrfs check --repair /dev/sda6</code></pre></div><p>Error:</p><div class="codebox"><pre><code>Chunk[256, 228, 37606129664]: length(1073741824), offset(37606129664), type(1) is not found in block group
well this shouldn&#039;t happen, extent record overlaps but is metadata? [37339414528, 16384]
aborted</code></pre></div><p>It seems it is time ti format /dev/sda6.</p><p>Or is there another option?</p><p>Would it be wiser to change to ext4 fs instead of btrfs?</p>]]></description>
			<author><![CDATA[dummy@example.com (matze72)]]></author>
			<pubDate>Thu, 09 Apr 2026 15:21:56 +0000</pubDate>
			<guid>https://dev1galaxy.org/viewtopic.php?pid=63127#p63127</guid>
		</item>
		<item>
			<title><![CDATA[Re: home directory 100% but acutall there should be 11Gb left of free spac]]></title>
			<link>https://dev1galaxy.org/viewtopic.php?pid=63126#p63126</link>
			<description><![CDATA[<p>Hello:</p><div class="quotebox"><cite>matze72 wrote:</cite><blockquote><div><p>I have the following problem:</p><p>according to df my home directory has free space and is fully occupied the same time:</p><div class="codebox"><pre><code>/dev/sda6        40G     29G     0  100% /home</code></pre></div></div></blockquote></div><p>I&#039;d have a look here <a href="https://btrfs.readthedocs.io/en/stable/trouble-index.html" rel="nofollow">https://btrfs.readthedocs.io/en/stable/ … index.html</a> and here <a href="https://wiki.debian.org/Btrfs" rel="nofollow">https://wiki.debian.org/Btrfs</a></p><p>Best,</p><p>A.</p>]]></description>
			<author><![CDATA[dummy@example.com (Altoid)]]></author>
			<pubDate>Thu, 09 Apr 2026 10:25:04 +0000</pubDate>
			<guid>https://dev1galaxy.org/viewtopic.php?pid=63126#p63126</guid>
		</item>
		<item>
			<title><![CDATA[home directory 100% but acutall there should be 11Gb left of free spac]]></title>
			<link>https://dev1galaxy.org/viewtopic.php?pid=63124#p63124</link>
			<description><![CDATA[<p>I have the following problem:</p><p>according to df my home directory has free space and is fully occupied the same time:</p><div class="codebox"><pre><code>/dev/sda6        40G     29G     0  100% /home</code></pre></div><p>This is permanent and does not disappear after a reeboot.</p><p>Withe the help of ddg-ai I made a few checks and also tried a repair but was not successful.</p><p>Here the results of the checks:</p><div class="codebox"><pre><code>btrfs filesystem show
Label: &#039;devuanroot&#039;  uuid: 2b6fb193-4c1a-4c76-a9a6-8dd1fc5b85b2
	Total devices 1 FS bytes used 44.83GiB
	devid    1 size 58.59GiB used 57.59GiB path /dev/sda3

Label: &#039;devuanhome&#039;  uuid: 5207a0ce-102b-475a-ba38-64d62eecd38b
	Total devices 1 FS bytes used 28.37GiB
	devid    1 size 39.06GiB used 39.06GiB path /dev/sda6

Label: &#039;sammelordner&#039;  uuid: ac2097f4-8bb0-4fa3-b282-fac690400a1d
	Total devices 1 FS bytes used 205.13GiB
	devid    1 size 255.31GiB used 206.02GiB path /dev/sda7

Label: &#039;antixroot&#039;  uuid: f98c69d7-4500-4706-8381-b1d22c94364d
	Total devices 1 FS bytes used 384.00KiB
	devid    1 size 58.59GiB used 1.02GiB path /dev/sda2

Label: &#039;antixhome&#039;  uuid: 07ecdfdf-12b8-4f6b-9607-79d5d9723d62
	Total devices 1 FS bytes used 112.00KiB
	devid    1 size 9.77GiB used 20.00MiB path /dev/sda5

Label: &#039;antixhome&#039;  uuid: 726cbd5c-87dd-4126-90e0-70e7fafae460
	Total devices 1 FS bytes used 112.00KiB
	devid    1 size 39.06GiB used 20.00MiB path /dev/sda8</code></pre></div><div class="codebox"><pre><code>findmnt -t btrfs
TARGET                          SOURCE    FSTYPE OPTIONS
/                               /dev/sda3 btrfs  rw,noatime,ssd,space_cache,subvolid=5,subvol=/
└─/home                         /dev/sda6 btrfs  rw,noatime,ssd,space_cache,subvolid=5,subvol=/
  └─/home/matthias/Sammelordner /dev/sda7 btrfs  rw,noatime,ssd,space_cache,subvolid=5,subvol=/</code></pre></div><p>btrfs scrum after repair:</p><div class="codebox"><pre><code>root@blechdepp:/home# btrfs scrub start -B -R /home
scrub done for 5207a0ce-102b-475a-ba38-64d62eecd38b
Scrub started:    Thu Apr  9 11:01:06 2026
Status:           finished
Duration:         0:00:54
	data_extents_scrubbed: 586281
	tree_extents_scrubbed: 32016
	data_bytes_scrubbed: 29936181248
	tree_bytes_scrubbed: 524550144
	read_errors: 0
	csum_errors: 0
	verify_errors: 1
	no_csum: 32170
	csum_discards: 7276468
	super_errors: 0
	malloc_errors: 0
	uncorrectable_errors: 1
	unverified_errors: 0
	corrected_errors: 0
	last_physical: 41892708352
ERROR: there are uncorrectable errors</code></pre></div><p>btrfs scrum before repair:</p><div class="codebox"><pre><code>root@blechdepp:~# btrfs scrub start -B -R /home
    
scrub done for 5207a0ce-102b-475a-ba38-64d62eecd38b
Scrub started:    Thu Apr  9 10:30:39 2026
Status:           finished
Duration:         0:00:56
	data_extents_scrubbed: 587056
	tree_extents_scrubbed: 32050
	data_bytes_scrubbed: 29985071104
	tree_bytes_scrubbed: 525107200
	read_errors: 0
	csum_errors: 0
	verify_errors: 0
	no_csum: 32170
	csum_discards: 7288404
	super_errors: 0
	malloc_errors: 0
	uncorrectable_errors: 0
	unverified_errors: 0
	corrected_errors: 0
	last_physical: 41892708352</code></pre></div><p>repair:</p><div class="codebox"><pre><code>root@blechdepp:~# btrfs check --force --repair /dev/sda6
enabling repair mode
Opening filesystem to check...
WARNING: filesystem mounted, continuing because of --force
Checking filesystem on /dev/sda6
UUID: 5207a0ce-102b-475a-ba38-64d62eecd38b
[1/7] checking root items
Fixed 0 roots.
[2/7] checking extents
No device size related problem found
[3/7] checking free space cache
cache and super generation don&#039;t match, space cache will be invalidated
[4/7] checking fs roots
reset nbytes for ino 19094119 root 5
[5/7] checking only csums items (without verifying data)
[6/7] checking root refs
[7/7] checking quota groups skipped (not enabled on this FS)
found 30510194688 bytes used, no error found
total csum bytes: 29153616
total tree bytes: 525123584
total fs tree bytes: 454262784
total extent tree bytes: 30703616
btree space waste bytes: 87900281
file data blocks allocated: 206212526080
 referenced 70746300416</code></pre></div><p>I had to use --force since I cannot umount /home</p><p>A hardware check:</p><div class="codebox"><pre class="vscroll"><code>root@blechdepp:~# smartctl -a /dev/sda6
smartctl 7.3 2022-02-28 r5338 [x86_64-linux-6.1.0-44-amd64] (local build)
Copyright (C) 2002-22, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF INFORMATION SECTION ===
Model Family:     Samsung based SSDs
Device Model:     Samsung SSD 860 EVO 500GB
Serial Number:    S3Z2NB1K309289F
LU WWN Device Id: 5 002538 e402803d9
Firmware Version: RVT01B6Q
User Capacity:    500.107.862.016 bytes [500 GB]
Sector Size:      512 bytes logical/physical
Rotation Rate:    Solid State Device
Form Factor:      2.5 inches
TRIM Command:     Available, deterministic, zeroed
Device is:        In smartctl database 7.3/5319
ATA Version is:   ACS-4 T13/BSR INCITS 529 revision 5
SATA Version is:  SATA 3.1, 6.0 Gb/s (current: 6.0 Gb/s)
Local Time is:    Thu Apr  9 10:34:27 2026 CEST
SMART support is: Available - device has SMART capability.
SMART support is: Enabled

=== START OF READ SMART DATA SECTION ===
SMART overall-health self-assessment test result: PASSED

General SMART Values:
Offline data collection status:  (0x00)	Offline data collection activity
					was never started.
					Auto Offline Data Collection: Disabled.
Self-test execution status:      (   0)	The previous self-test routine completed
					without error or no self-test has ever 
					been run.
Total time to complete Offline 
data collection: 		(    0) seconds.
Offline data collection
capabilities: 			 (0x53) SMART execute Offline immediate.
					Auto Offline data collection on/off support.
					Suspend Offline collection upon new
					command.
					No Offline surface scan supported.
					Self-test supported.
					No Conveyance Self-test supported.
					Selective Self-test supported.
SMART capabilities:            (0x0003)	Saves SMART data before entering
					power-saving mode.
					Supports SMART auto save timer.
Error logging capability:        (0x01)	Error logging supported.
					General Purpose Logging supported.
Short self-test routine 
recommended polling time: 	 (   2) minutes.
Extended self-test routine
recommended polling time: 	 (  85) minutes.
SCT capabilities: 	       (0x003d)	SCT Status supported.
					SCT Error Recovery Control supported.
					SCT Feature Control supported.
					SCT Data Table supported.

SMART Attributes Data Structure revision number: 1
Vendor Specific SMART Attributes with Thresholds:
ID# ATTRIBUTE_NAME          FLAG     VALUE WORST THRESH TYPE      UPDATED  WHEN_FAILED RAW_VALUE
  5 Reallocated_Sector_Ct   0x0033   100   100   010    Pre-fail  Always       -       0
  9 Power_On_Hours          0x0032   094   094   000    Old_age   Always       -       26176
 12 Power_Cycle_Count       0x0032   097   097   000    Old_age   Always       -       2985
177 Wear_Leveling_Count     0x0013   094   094   000    Pre-fail  Always       -       87
179 Used_Rsvd_Blk_Cnt_Tot   0x0013   100   100   010    Pre-fail  Always       -       0
181 Program_Fail_Cnt_Total  0x0032   100   100   010    Old_age   Always       -       0
182 Erase_Fail_Count_Total  0x0032   100   100   010    Old_age   Always       -       0
183 Runtime_Bad_Block       0x0013   100   100   010    Pre-fail  Always       -       0
187 Uncorrectable_Error_Cnt 0x0032   100   100   000    Old_age   Always       -       0
190 Airflow_Temperature_Cel 0x0032   060   044   000    Old_age   Always       -       40
195 ECC_Error_Rate          0x001a   200   200   000    Old_age   Always       -       0
199 CRC_Error_Count         0x003e   100   100   000    Old_age   Always       -       0
235 POR_Recovery_Count      0x0012   099   099   000    Old_age   Always       -       128
241 Total_LBAs_Written      0x0032   099   099   000    Old_age   Always       -       107438634846

SMART Error Log Version: 1
No Errors Logged

SMART Self-test log structure revision number 1
No self-tests have been logged.  [To run self-tests, use: smartctl -t]

SMART Selective self-test log data structure revision number 1
 SPAN  MIN_LBA  MAX_LBA  CURRENT_TEST_STATUS
    1        0        0  Not_testing
    2        0        0  Not_testing
    3        0        0  Not_testing
    4        0        0  Not_testing
    5        0        0  Not_testing
Selective self-test flags (0x0):
  After scanning selected spans, do NOT read-scan remainder of disk.
If Selective self-test is pending on power-up, resume after 0 minute delay.</code></pre></div>]]></description>
			<author><![CDATA[dummy@example.com (matze72)]]></author>
			<pubDate>Thu, 09 Apr 2026 09:09:55 +0000</pubDate>
			<guid>https://dev1galaxy.org/viewtopic.php?pid=63124#p63124</guid>
		</item>
	</channel>
</rss>
