Louis I. answered 05/14/19
Computer Science Instructor/Tutor: Real World and Academia Experienced
That's a sad-ending story, but yes - I'm assuming I know what really happened here.
You didn't own the symlink - someone else did - perhaps root, but not necessarily.
You applied the sudo to the wrong command.
You should have applied it to your 1st "rm" attempt
sudo rm symLink
rather than
sudo rm -rf dirThatSymLinkPointsTo
That's when you "threw the baby out" ... that's when the file system blocks got purged.
In the future, you just need to be mindful of exactly what you're doing with sudo
You intended to end up with a directory that no longer had a symLink pointing to it.
Instead you wound up with a synLink pointing to an invalid directory.
I'll wager this - you're never do this again ;-)