You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Putting diskus in place greatly reduced the amount of time our previous du -sh script took, but I need the path name in the output. So I'm doing this for now, seems though that we lose human readable sizes when manipulating the stdout:
for i in ` find /share/users -mindepth 1 -maxdepth 1 | grep -v "^\.*$"`; do diskus -j 3 $i | awk -v dir=$i '{print $NF "\t\t\t" dir}' & done >> /tmp/diskus-$DATE.log
DANGER for anyone that finds this at random: The above launches a diskus process for everything found 1 layer in, if you have over 100 dirs and say only 96 cores, this will oversubscribe and you'll see a loadavg over 300.
The text was updated successfully, but these errors were encountered:
Great tool!
Would love to see the path in the output a la:
Putting diskus in place greatly reduced the amount of time our previous
du -sh
script took, but I need the path name in the output. So I'm doing this for now, seems though that we lose human readable sizes when manipulating the stdout:Output:
DANGER for anyone that finds this at random: The above launches a
diskus
process for everything found 1 layer in, if you have over 100 dirs and say only 96 cores, this will oversubscribe and you'll see a loadavg over 300.The text was updated successfully, but these errors were encountered: