Wiped Freespace, now drive is full and I can't delete

Dyzaster · 2019-03-17 05:28:04

Okay, so I did the dumb thing and ran wipe free disk space on bleachbit, thought it wouldn't be a big deal since it'd have 8h while I slept to finish. When I woke up, it said 3m left. 5m went by, it said 2m left, my dumb self stopped it and rebooted to erase the tmp file, when it rebooted it got stuck on "loading ramdisk" and I let it go for 10m, and eventually gave up.

Well I booted up arch livedisk on a usb, and as I thought, / was 100% full. I chrooted into my hdd, and so far have tried bleachbit -c system.trash system.tmp system.cache, if tried rm -rf .local/share/Trash* in my home acc, rm -rf on Trash worked, but didn't clear any space, and bleachbit fails, giving me a permission error due to the drive being full. Running as root works, but it doesn't fix anything because it isn't clearing my account.

I have no idea what to do at this point. I've ran ls -a in my home and haven't found the normal bleachbit files I used to years ago. I updated my system just earlier today so everythings 100% up to date.

Any idea on what I should do next? Where to look for the temp files manually aside from /home?

EDIT: when running bleachbit I didn't get a permission error, it was error 28 no space left on device. I tried rebooting, booting the live disk up once more, mounted my root folder, deleted debian.iso (just a 2-4gb filei don't need) without being chrooted, and it did nothing. Space is still 100% full when iI chrooted in and ran df.

Last edited by Dyzaster (2019-03-17 08:12:34)

seth · 2019-03-17 09:13:37

You'll have to fix the system offline, ie. do NOT chroot into it.
From the code, there should be hidden files in all wiped paths like ".j9ruvrozt8wzuozco32749u3974p08oczp3fdsdxlf#h9q3c32pu9ureuscue90403ucmu3qcmur38q" - the paths are the ones you chose in the GUI.

find /mnt -xdev -type f -size +1G

would find all files >=1GB in /mnt …

The next and very important step you must not miss:

pacman -Rs bleachbit

graysky · 2019-03-17 09:35:44

seth wrote:

The next and very important step you must not miss:
pacman -Rs bleachbit

Actually BB is a good tool. I never used the free space wipe, but I routinely:

# bleachbit --clean system.cache system.localizations system.trash

Dyzaster · 2019-03-17 09:48:19

seth wrote:

You'll have to fix the system offline, ie. do NOT chroot into it.
From the code, there should be hidden files in all wiped paths like ".j9ruvrozt8wzuozco32749u3974p08oczp3fdsdxlf#h9q3c32pu9ureuscue90403ucmu3qcmur38q" - the paths are the ones you chose in the GUI.
find /mnt -xdev -type f -size +1G
would find all files >=1GB in /mnt …
The next and very important step you must not miss:
pacman -Rs bleachbit

EDIT: typo, my bad.

I'm running the command, searching for the files, so far nothing has came up but I will be back in a bit to post if iI found anything yet, I've looked in multiple folders in my user directory manually and can't seem to find it in any of the places it used to show up (I've had this eeorro many times in the past lol) but hopefully this will find it

Last edited by Dyzaster (2019-03-17 09:50:54)

graysky · 2019-03-17 09:52:32

What is the partition format (ext4, btrfs, etc)? Did you run fsck on it from the live environment?

seth · 2019-03-17 09:53:02

Is there a "/mnt" path? (The assumption was to run this from the iso or grml or whatever and your system root mounted at "/mnt")
In case that's really weird, is maybe "type find" some alias?

Jaja, "exactly" ;-)

---

@graysky and in full risk of a flamewar ;-)

It uses wihte- and blacklists for "deleteworthy paths" and does not maintain the integrity of mapped files, see eg. https://blog.martin-graesslin.com/blog/ … bleachbit/
I don't know how the OP "stopped" bleachbit, but while there's a comment in the code to delete tempFiles on termination, according to a brief google and this thread that doesn't happen either.

Deleting caches is a thing of its own - more often than never you'll end up deleting caches in order to re-create them w/ the next session.

If I feel like I need to free some space, I search for bigger files with old access dates. There's a good chance this is cruft.
Automated deletion of "stuff" by code written by some python kiddies is like russian roulette w/ 5 bullets.

Last edited by seth (2019-03-17 09:54:19)

Dyzaster · 2019-03-17 09:54:30

Okay so done, I added > test at the end so it would send everything to a file that I could scroll through, but all it has are my movies, TV shows, some .isos and games, no random files or anything that I cannot identify as being mine.

ran it on all of /mnt so nothing was excluded.

Edit: I set to 500mb and same result, more files, just more tv shows though.

Is there a way for me to check the size of a specific directory recursively through terminal? I know what size all of my directories should be, this would help me narrow it down a lot.

Last edited by Dyzaster (2019-03-17 09:58:11)

seth · 2019-03-17 09:58:21

Mount trap? Do you mount any other partitions into /mnt eg. /mnt/home for your /home partition?

df -h

Otherwise

graysky wrote:

Did you run fsck on it from the live environment?

Dyzaster · 2019-03-17 10:05:58

Naw basically i have 2 drives, a ssd with /boot on it, and a 2tb hdd with swap and /, I like a nice simple setup lol. / is where the files are. / is 100% full when it actually has 700gb free, when I exited bleachbit I just hit the X, I didn't alt f4 or pkill.

I know the partition that is full, I just don't know what folders inside of that partition hold the data. After searching around for hours tonight, everybody was talking about bleachbit updating and this no longer being an issue, will I definitely have the issue and bleachbit definitely is updated. My only assumption is that bleachbit possibly creates its own folder, and then creates all these files inside of that one specific folder instead of doing it in an already existing folder. I've checked /var/tmp and /tmp just incase, nothing in /var/tmp was suspecious, and /tmp was empty like iit should be.

P.s. I probably will be uninstalling bleachbit after this, I I think the Russian Roulette metaphor is about perfect lol.

Also I have not ran fsck, that isn't going to change partitions at all will it?

Last edited by Dyzaster (2019-03-17 10:13:47)

seth · 2019-03-17 10:13:18

"man fstrim"?
What's "du -hs /mnt"?

Dyzaster · 2019-03-17 10:17:35

Result:
993G /mnt

df -h says 1.8t is used, 0bytes free

P.s. there's a chance, and from what this is showing is most likely the case, that within the past week I ran clean disk space for a few minutes, closed out, and those files are still on my system also

Last edited by Dyzaster (2019-03-17 10:24:16)

seth · 2019-03-17 10:21:48

And that's the 2TB HDD?
Compared to "df -h"?

Edit: and did you run an fsck on the partition?

Last edited by seth (2019-03-17 10:23:52)

Dyzaster · 2019-03-17 10:25:20

I have not ran fsck yet, do I just run fsck /dev/sda2? Or is there more to it?

seth · 2019-03-17 10:30:29

I'd suggest to umount it first, but yes.

Dyzaster · 2019-03-17 10:35:08

Okay yeah so I've definitely been here before and seen this before, and have resolved errors on here before, but this one is something I have not seen before:
/dev/sda2 contains a filesystem with errors, check forced
Inode 11796944 extent tree (at level 2) could be narrower.

It is asking me to optimize, I'm assuming that I should click yes, but I do want to make sure first so I don't mess anything up, I have stuff that I cannot recover if I mess my partition up lol

EDIT: So I cliked Yes, more errors started to come up on other blocks, I guess ill just go through this lol

Last edited by Dyzaster (2019-03-17 10:43:34)

seth · 2019-03-17 10:52:21

Is that the only and complete message?
This happens and is usually a minor thing - no idea whether it could stash 1TB from your bleachbit wipe.

I'd argue to never tamper w/ a known broken FS w/ having a backup of exclusive data (and actually you should back that up anyway)
"fsck -p" will auto-fix the "safe" issues and I don't expect trouble under these circumstances, but ex falso quodlibet …

Dyzaster · 2019-03-17 10:53:55

So I have already went through a couple of the errors myself, and I'm not completely done, I'm at#7017 of the "Free blocks count wrong for group***" part. Can I exit out of this and be safe? That way I can start at the automatic run? Lol

Dyzaster · 2019-03-17 11:01:07

Seth, thank you very much!!!! I'm back in my system and everything llooks good

I'm still a little confused as to what exactly happened though lol

Arch Linux

#1 2019-03-17 05:28:04

Wiped Freespace, now drive is full and I can't delete

#2 2019-03-17 09:13:37

Re: Wiped Freespace, now drive is full and I can't delete

#3 2019-03-17 09:35:44

Re: Wiped Freespace, now drive is full and I can't delete

#4 2019-03-17 09:48:19

Re: Wiped Freespace, now drive is full and I can't delete

#5 2019-03-17 09:52:32

Re: Wiped Freespace, now drive is full and I can't delete

#6 2019-03-17 09:53:02

Re: Wiped Freespace, now drive is full and I can't delete

#7 2019-03-17 09:54:30

Re: Wiped Freespace, now drive is full and I can't delete

#8 2019-03-17 09:58:21

Re: Wiped Freespace, now drive is full and I can't delete

#9 2019-03-17 10:05:58

Re: Wiped Freespace, now drive is full and I can't delete

#10 2019-03-17 10:13:18

Re: Wiped Freespace, now drive is full and I can't delete

#11 2019-03-17 10:17:35

Re: Wiped Freespace, now drive is full and I can't delete

#12 2019-03-17 10:21:48

Re: Wiped Freespace, now drive is full and I can't delete

#13 2019-03-17 10:25:20

Re: Wiped Freespace, now drive is full and I can't delete

#14 2019-03-17 10:30:29

Re: Wiped Freespace, now drive is full and I can't delete

#15 2019-03-17 10:35:08

Re: Wiped Freespace, now drive is full and I can't delete

#16 2019-03-17 10:52:21

Re: Wiped Freespace, now drive is full and I can't delete

#17 2019-03-17 10:53:55

Re: Wiped Freespace, now drive is full and I can't delete

#18 2019-03-17 11:01:07

Re: Wiped Freespace, now drive is full and I can't delete

Board footer