Not emby related but debian related

[tdiguy 99]

I screwed something up trying to tar my drive and back it up. 

I ran sudo tar -czvf /media/emby/* disk-temp/Movies-archive.tar.gzMovies-archive.tar.gz

and about 3/4 of the way through my son hit the keyboard a few times and likely managed to hit ctrl c because it stopped the process.

 

So now i have /media/emby with 90% utilization and i have no idea what is using all the room. Before trying to back it up /media/emby was at about 46% utilization.

 

Would love some idea's on this. Thank you.

[Luke 42078]

Have you tried just using a file browser to see what folders are consuming the most amount of space?

[tdiguy 99]

Have you tried just using a file browser to see what folders are consuming the most amount of space?

I have not tried that, i have the box set up for cli access only right now, maybe later today when i actually wake up before the rest of the house i will try that. I need to reboot the box to get gui access via rdp.

[tdiguy 99]

Actually found out about a really good command line program ncdu shows the disk usage per directory / file.

Seems i screwed up my tar command and it made a tat of my source drive on my source drive as the first file in the source drive. 

[dcrdev 255]

Or you could have used "du" which is a standard utility - usage "du /directory".

[mastrmind11 722]

Actually found out about a really good command line program ncdu shows the disk usage per directory / file.

Seems i screwed up my tar command and it made a tat of my source drive on my source drive as the first file in the source drive. 

LOL did this myself once.  All it takes is once

[tdiguy 99]

Just glad it was of my emby drive and not root. Debian has a fit when root reaches 100%.

 

Sent from my SM-G900P using Tapatalk

[dcrdev 255]

Nevermind

Edited November 15, 2017 by dcrdev

[mastrmind11 722]

Just glad it was of my emby drive and not root. Debian has a fit when root reaches 100%.

 

Sent from my SM-G900P using Tapatalk

which is especially painful if your server is headless and gets rebooted in that state.

[tdiguy 99]

which is especially painful if your server is headless and gets rebooted in that state.

ya looking back at it i dont get why debin suggests home and / being on one partition for inexperienced users.

[Waldonnis 148]

ya looking back at it i dont get why debin suggests home and / being on one partition for inexperienced users.

 

Don't get me started.  That topic has been debated heatedly since I was a Debian maintainer many years ago.  I'm in agreement with you, and think that keeping important directories on their own partitions makes better sense.  On the other hand, it does mirror how other OS vendors handle things and is at least a more familiar concept to most.  Partition management can be intimidating for novices anyway and, let's be honest, most people just prefer the "one big drive" thing rather than worry about partitioning.  Thankfully, I wasn't part of the group that dealt with the installer outside of the ports I was in charge of, so I never got dragged into the arguments.

 

Personally, I always include "v" (verbose output) when running tar simply because I've made so many typos over the years.  It has had the side benefit of making me look much busier than I am when people walk by and see text streaming by    For the truly paranoid, you can monitor the size of the tarball as well in another vt or shell to make sure it isn't getting larger than you expected (using watch or any number of other methods).

[tdiguy 99]

Well I guess I see the point, but it's not like gparted is hard to use. My next build I am making sure root is its own partition. When emby had a runaway temp file it put a big kink in doing anything on the system. Putting the temp drive as my external drive kills performance for streaming live TV.

 

Sent from my SM-G900P using Tapatalk