Stack Exchange Network

Stack Exchange network consists of 175 Q&A communities including Stack Overflow, the largest, most trusted online community for developers to learn, share their knowledge, and build their careers.

Visit Stack Exchange
The results are in! See what nearly 90,000 developers picked as their most loved, dreaded, and desired coding languages and more in the 2019 Developer Survey.

Easy enough. The // sequence isn't a comment in bash (# is). The statement OUT_DIR=x // text had no effect* except a cryptic error message. Thus, with the OUT_DIR being an empty string, one of the commands eventually executed was rm -rf /*. Some directories placed directly underneath / weren't removed due to user not having permissions, but it appears that ...


1) He erroneously assumed that // was a bash comment. It is not, only # is. The shell interpreted // text as a normal command, and did not find a binary called //, and did nothing. In bash, when you have a variable assignment (OUT_DIR=/data/backup/mongod/tmp) directly preceding a command (// text), it only sets the variable while running the command. ...


You're requesting the volume to shrink by 11GB, yet you only have about 6GB unallocated. You can more efficiently use allocated extents by rebalancing the volume. Executing a command similar to btrfs balance start /home will start that process, and it may take some time to complete. But I don't know if that will free up enough for a large amount of ...


1) Bash comments start with #. Sorry for your loss. 2) Restore from backup is the only way to proceed here, unfortunately.


I have setup a few NAS boxes that are nothing but a bunch of disks and a network interface. Definitely not a windows server, they were running busybox under the hood. So the disks would be formatted using the ext* file system and sharing is done with samba. This works ok if you just want to copy a file every now and then. But a lot of the metadata in the ...

Only top voted, non community-wiki answers of a minimum length are eligible