You have about 30G of data space available but the available metadata is close 
to being full.  That could be your problem, but I am new to btrfs.

I reformatted your output to make it more readable:

# btrfs filesystem df /
Data, single: total=50.02GiB, used=20.89GiB System,
RAID1: total=32.00MiB, used=16.00KiB
Metadata, RAID1: total=79.06MiB, used=73.30MiB
Metadata, DUP: total=725.50MiB, used=638.70MiB
GlobalReserve, single: total=69.91MiB, used=64.00KiB


You can try to balance the metadata area using ' btrfs balance start -m /'.

My filesystem was low on data space but when I ran the command to balance the 
metadata area, over 700MB was freed up (according to the 'df' command).  I 
ended up balancing the metadata and data areas, then ran the command to defrag 
the data blocks.  I ran ' btrfs balance start -dusage=5 /' and increased the 
'dusage' value by 5 until it said that it did anything.  It was up to 
'dusage=50' when this happened.



Harley Linker Jr.
Sr. Systems Programmer
Ensono
e: [email protected]
o: 630.944.5111

www.ensono.com

-----Original Message-----
From: Linux on 390 Port <[email protected]> On Behalf Of Neale Ferguson
Sent: Monday, October 22, 2018 7:11 AM
To: [email protected]
Subject: Re: Problem running zypper upgrade

Thanks, it doesn’t look like I have much:

# snapper list
Type   | # | Pre # | Date                     | User | Cleanup | Description    
       | Userdata
-------+---+-------+--------------------------+------+---------+-----------------------+---------
single | 0 |       |                          | root |         | current        
       |
single | 1 |       | Tue Feb  2 12:01:30 2016 | root |         | first root 
filesystem |


# btrfs filesystem df /
Data, single: total=50.02GiB, used=20.89GiB System, RAID1: total=32.00MiB, 
used=16.00KiB Metadata, RAID1: total=79.06MiB, used=73.30MiB Metadata, DUP: 
total=725.50MiB, used=638.70MiB GlobalReserve, single: total=69.91MiB, 
used=64.00KiB

# btrfs filesystem usage /
Overall:
    Device size:         51.66GiB
    Device allocated:          51.65GiB
    Device unallocated:              3.08MiB
    Device missing:              0.00B
    Used:                 22.28GiB
    Free (estimated):          29.13GiB  (min: 29.13GiB)
    Data ratio:                    1.00
    Metadata ratio:                2.00
    Global reserve:            69.91MiB  (used: 64.00KiB)

Data,single: Size:50.02GiB, Used:20.89GiB
   /dev/dasdb2     5.64GiB
   /dev/dasdd      21.99GiB
   /dev/dasde1     22.38GiB

Metadata,RAID1: Size:79.06MiB, Used:73.30MiB
   /dev/dasdb2     79.06MiB
   /dev/dasde1     79.06MiB

Metadata,DUP: Size:725.50MiB, Used:638.70MiB
   /dev/dasdb2   939.00MiB
   /dev/dasdd    512.00MiB

System,RAID1: Size:32.00MiB, Used:16.00KiB
   /dev/dasdb2     32.00MiB
   /dev/dasde1     32.00MiB

Unallocated:
   /dev/dasdb2     1.00MiB
   /dev/dasdd      1.05MiB
   /dev/dasde1     1.03MiB

# btrfs fi show
Label: none  uuid: d80841ed-2839-4dfc-b3be-4539adce5eb5
Total devices 3 FS bytes used 21.58GiB
devid    1 size 6.67GiB used 6.67GiB path /dev/dasdb2
devid    2 size 22.49GiB used 22.49GiB path /dev/dasdd
devid    3 size 22.49GiB used 22.49GiB path /dev/dasde1

I’m not sure why it used /dev/dasdd rather than ./dev/dasdd1


On 10/22/18, 07:23, "Linux on 390 Port on behalf of Harley Linker" 
<[email protected] on behalf of [email protected]> wrote:

    If the root is under btrfs, then the output of 'df' is misleading as the 
space could be tied up by snapshots.  Below are commands that I used last week 
to find and free space in a root filesystem.



----------------------------------------------------------------------
For LINUX-390 subscribe / signoff / archive access instructions, send email to 
[email protected] with the message: INFO LINUX-390 or visit
https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.marist.edu%2Fhtbin%2Fwlvindex%3FLINUX-390&amp;data=02%7C01%7Charley.linker%40ENSONO.COM%7C7cac7be10a564d95a08608d638184059%7Cd483ed84f7bf4078a58ffb250feccf8f%7C0%7C0%7C636758074153999796&amp;sdata=9jNlwkLZmsoZ13KuzL90%2Be0UeJJEQH0tmZe9qKqYqOs%3D&amp;reserved=0
----------------------------------------------------------------------
For more information on Linux on System z, visit
https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwiki.linuxvm.org%2F&amp;data=02%7C01%7Charley.linker%40ENSONO.COM%7C7cac7be10a564d95a08608d638184059%7Cd483ed84f7bf4078a58ffb250feccf8f%7C0%7C0%7C636758074154009804&amp;sdata=%2BAP%2FquU9GhbfTUFZQ8UVOkkoj8C4JB3a%2BjA0fDOco7Q%3D&amp;reserved=0
© 2018 Ensono, LP. All rights reserved. Ensono is a trademark of Ensono, LP. 
The information contained in this communication is confidential, is intended 
only for the use of the recipient named above, and may be legally privileged. 
If the reader of this message is not the intended recipient, you are hereby 
notified that any dissemination, distribution or copying of this communication 
is strictly prohibited. If you have received this communication in error, 
please resend this communication to the sender and delete the original message 
or any copy of it from your computer system.

----------------------------------------------------------------------
For LINUX-390 subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
----------------------------------------------------------------------
For more information on Linux on System z, visit
http://wiki.linuxvm.org/

Reply via email to