How to delete a (seemingly) infinite folder structure?

  • Thread starter Thread starter SomeGamer
  • Start date Start date
  • Views Views 1,806
  • Replies Replies 7

SomeGamer

Well-Known Member
Member
Joined
Dec 19, 2014
Messages
6,827
Reaction score
3,432
Trophies
2
XP
5,133
Country
Antarctica
Somehow com.sonymobile.dlna has created a folder structure like this on my SD card:
/Android/com.sonymobile.dlna/cache/cache/cache... and it goes on.
Currently running sudo rm -rf on a live Lubuntu on my tablet, and while it's certainly doing something (fans at full speed) I'm beyond uncertain if it'll ever finish. :P
 
Somehow com.sonymobile.dlna has created a folder structure like this on my SD card:
/Android/com.sonymobile.dlna/cache/cache/cache... and it goes on.
Currently running sudo rm -rf on a live Lubuntu on my tablet, and while it's certainly doing something (fans at full speed) I'm beyond uncertain if it'll ever finish. :P
I don't know how it is on Linux for can you check it's properties? On windows it shows how many folders a folder has.
 
I don't know how it is on Linux for can you check it's properties? On windows it shows how many folders a folder has.
It shows an obviously smaller number than the actual count of folders. (Can't remember the exact number, but the structure is much deeper.)
 
SOLVED! Simply closed the Terminal window, then deleted using the GUI file manager as a last attempt. To my great surprise, it worked, despite it previously saying that the file name was too long. But I really want to know why it worked the second time. (The rm -rf was closed in the process of deletion so it obviously hasn't finished yet.)
 
  • Like
Reactions: Jacklack3
SOLVED! Simply closed the Terminal window, then deleted using the GUI file manager as a last attempt. To my great surprise, it worked, despite it previously saying that the file name was too long. But I really want to know why it worked the second time. (The rm -rf was closed in the process of deletion so it obviously hasn't finished yet.)

Sounds like rm -f had deleted enough of the deepest folders in the path to enable the GUI to handle the rest... Example When you originally tried deleting from the GUI there may have been 500 folders, making the string value containing the complete path to the deepest file too long for the gui to handle. rm -f may have removed the deepest 300 entries before being interrupted, leaving only another 200 left, therefore allowing the GUI to now handle the path of the deepest file.
 
  • Like
Reactions: SomeGamer

Site & Scene News

Popular threads in this forum