You are not logged in.
Pages: 1
So I was building android and got a out of space error. Looked at my hard drive and it said I still had about 70gb of space left.
I've ran balance and defraged. Ran resize max also. So i'm not sure what's wrong.
I used to have about 175gb of space in data. This was after I ran balance. I ran balance again and it started going to down so I stopped it.
This was on the stable branch's on 3.12. I switched to testing on 3.13 and still have the same problem.
This is my output of: df -h
Filesystem Size Used Avail Use% Mounted on
/dev/sda1 239G 121G 117G 52% /
dev 7.9G 0 7.9G 0% /dev
run 7.9G 5.4M 7.9G 1% /run
tmpfs 7.9G 77M 7.8G 1% /dev/shm
tmpfs 7.9G 0 7.9G 0% /sys/fs/cgroup
tmpfs 7.9G 443M 7.4G 6% /tmp
tmpfs 7.9G 896K 7.9G 1% /etc/pacman.d/gnupg
This is the output of: sudo btrfs fi df /
Data, single: total=155.00GiB, used=117.83GiB
System, single: total=32.00MiB, used=28.00KiB
Metadata, single: total=5.00GiB, used=3.55GiB
This is the output of: sudo btrfs fi show
Label: none uuid: a258fcee-0dbd-4ea5-9b1e-5c8483e058f7
Total devices 1 FS bytes used 121.58GiB
devid 1 size 238.47GiB used 160.03GiB path /dev/sda1Btrfs v3.12
Last edited by winner00 (2014-01-30 05:34:48)
Offline
It is not your root file system that is full. It is your temporary file system. Probably the one on /tmp. You might try a reboot and then try again. Check that /tmp is cleared after boot.
Nothing is too wonderful to be true, if it be consistent with the laws of nature -- Michael Faraday
Sometimes it is the people no one can imagine anything of who do the things no one can imagine. -- Alan Turing
---
How to Ask Questions the Smart Way
Offline
I've tried rebooting a few times and watching /tmp while building. It's not that. Btrfs is making my data disappear for some reason. It says I have 155gb max while the other commands say I have about 239gb.
Offline
Btrfs is making my data disappear for some reason. It says I have 155gb max
No it doesn't. It's saying that you have 155GB currently allocated to the data pool. You should still have ~78GB in the "free" pool. It should be allocated to the data/metadata/system pools as and when it is needed. If this isn't happening, then you might have encountered a filesystem bug (possibly this one: http://www.mail-archive.com/linux-btrfs … 30519.html)
Last edited by WorMzy (2014-01-31 02:28:45)
Sakura:-
Mobo: MSI MAG X570S TORPEDO MAX // Processor: AMD Ryzen 9 5950X @4.9GHz // GFX: AMD Radeon RX 5700 XT // RAM: 32GB (4x 8GB) Corsair DDR4 (@ 3000MHz) // Storage: 1x 3TB HDD, 6x 1TB SSD, 2x 120GB SSD, 1x 275GB M2 SSD
Making lemonade from lemons since 2015.
Offline
Yea it's probably a bug like that. Which sucks because I could use that data.
Offline
So email the mailing list and see if you can help squash the bug.
Sakura:-
Mobo: MSI MAG X570S TORPEDO MAX // Processor: AMD Ryzen 9 5950X @4.9GHz // GFX: AMD Radeon RX 5700 XT // RAM: 32GB (4x 8GB) Corsair DDR4 (@ 3000MHz) // Storage: 1x 3TB HDD, 6x 1TB SSD, 2x 120GB SSD, 1x 275GB M2 SSD
Making lemonade from lemons since 2015.
Offline
Also I noticed you seem to have metadata set to "single". Are you sure that is wise? EVerything I read suggests to set it to the default "raid1" at least since if you lose that metadata you lose everything.
You said you ran a balance operation but stopped it. Could that be related to this? Maybe it would be a good idea to run balance and let it continue [after ensuring you have backups just in case]?
Offline
On SSDs the default option is single for metadata.
Offline
On SSDs the default option is single for metadata.
This is because quite a few controllers have internal deduplication. So if you do dup, it is likely that it is going to ultimately be single anyway. But a mkfs.btrfs over >1 disk will default to data as raid0 and metadata/system as raid1 the last I checked.
When I first started using btrfs I was interested because of the snapshot functionality. But over time I began to learn about the overall design of btrfs and realized that the biggest strong point of the filesystem lies with its ability to self-heal. The violation of the traditional layering approach to disks, partitions, and filesystems is precisely due to this benefit. So if one has the opportunity to use btrfs to span more than one disk, using raid1 for at least metadata is highly recommended.
Offline
Pages: 1