I was like "nothing wrong here" until I saw that T that my brain just refused to parse the first time.
post
Your username absolutely does not check out. Or your shredder is broken haha
Pfft, the only "hoarding problem" is that storage is expensive these days!
I know, I just paid $500 for a 24TB SAS drive that was $250 just over a year ago.
That's a good deal. Microcenter was selling a WD 20TB external HDD for $600. Didn't end up pulling the trigger 'cause I'm going for a 2 drive Raid1 config on my janky setup and $1350 w/ taxes is way too steep.
I'm reading the command to the tune of Du Hast
Meanwhile here I am trying to upgrade my 512gb NVME drive to 2Tb while also still trying to afford car payments, rent and food. Rookie numbers on my part.
The most well-timed thing I ever did was buy 6 2tb NVMe drives in August last year
God help me if one fails
Pardon my stupidity BUT why include stdout to Devnull? Why not omit and simply 'du -sh /home'
There’s probably a bunch of permissions errors, filesystems warnings for cross-filesystem mounts or links, etc. all going to stderr. Linux output streams are a bit odd, 1 is stdout and 2 is stderr. So the command is redirecting the “noise” to null and just printing the actual command output. That would be my assessment, but OP could probably give a more correct answer..!
Noob, just use sudo, less chars!
Oddly enough, still generates errors. (There are stuff in user directories that are set to 600.... so even root can't browse/open.)
Well now I have to try this. Missing that executable bit would make sense. But last time I did this on / I didn't get errors 🤔
Are you sure? Root can see everything.
2> means stderr.... Keeps the "can't access ...." Out of the display.
One think I miss from reddit… /r/datahoarder
These were my people. I probably have 100TB but it certainly isn't in my home directory. I'm not sure if I should be immpressed or freightened.
There's !datahoarder@lemmy.world, !datahoarder@lemmy.ml, and !datahoarder@selfhosted.forum...
EDIT: spelling
never saw the s argument and was curious what's the difference to d. man pages are way ahead of me ^^
--max-depth=0is the same as--summarize
So just did a couple of experiments...
sudo su -sh /home - returns permission denied errors on certain NAS subdirectories, but not a lot.
du -sh /home --summarize -returns the same errors.
du -sh --max-depth=0 - returns the same errors plus an error saying that using --max-depth=0 is the same as --summarize.
;-) for the purposes of what I was doing (creating a clip for posting) redirecting stderr to null was the best option.
But I learned a few things today, which is cool. ;-)
Why do you pipe stderr of du into /dev/null?
I create videos, and back up all of my raw footage. I make weekly videos, and the size ranges from 50GB up to 500GB or more. I have 105TB available, 90TB used at the moment. I also have a fully redundant set of another 105TB. My employer has unfortunately made it very easy to justify hoarding, as they'll sell me reputable used commercial drives for $10/TB.
The video archives are 53TB
TubeArchivist is 19TB
Legally acquired movies and TV is 10TB
Immich is 2TB
Those are the main users of data. A bunch of other folders are using anywhere from a gig to 500GB, but those are basically rounding errors.
Bob Saget would roll in his grave if he heard about your addiction.
top 50 comments