


What to do if rm deletion does not release space in Linux
解决方法:1、利用“lsof | grep deleted”命令,获取已经被删除但是仍被应用程序占用的进程;2、利用kill命令,删除获取的进程即可释放删除的空间,语法为“kill -9 获取到占用被删文件的进程号”。
本教程操作环境:linux7.3系统、Dell G3电脑。
linux中rm删除不释放空间怎么办
因为被删除的文件在删除的时侯还是进程在操作(打开、访问等)的缘故,rm只完成了在磁盘上文件实体的释放,而类似free list结构中相应的文件系统因进程的操作相应的inode并未释放。
解决的方法:这样的问题解决起来也很简单,找到操作的进程,kill掉就可以了,可是找到操作的进程恰恰是本问题的难点和关键。
这样的问题也可以通过重启机器和nmount/mount文件系统这样的方式解决,但这样的方法我是不提倡的,小小的问题就重启机器,小题大做。
过程:
1、找到正在用被删文件的进程
lsof | grep deleted
可以获取一个已经被删除但是仍然被应用程序占用的文件列表
用该命令后,我发现占用的文件列表非常多,我们需要将占用已删除文件的进程给一个一个的杀掉
示例如下:
[root@nc-ftp02 data]# lsof -n /data |grep deleted sh 8757 root 1w REG 202,5 287246420690 12 /data/nohup.out (deleted) sh 8757 root 2w REG 202,5 287246420690 12 /data/nohup.out (deleted) rsync 28485 root 1w REG 202,5 287246420690 12 /data/nohup.out (deleted) rsync 28485 root 2w REG 202,5 287246420690 12 /data/nohup.out (deleted) ssh 28486 root 2w REG 202,5 287246420690 12 /data/nohup.out (deleted) ssh 28486 root 6w REG 202,5 287246420690 12 /data/nohup.out (deleted) [root@nc-ftp02 data]# lsof -n /data |grep deleted|awk '{print $2}' 8757 8757 28674 28674 28675 28675 [root@nc-ftp02 data]# lsof -n /data |grep deleted|awk '{print $2}'|xargs kill -9 [root@nc-ftp02 data]# lsof -n /data |grep deleted [root@nc-ftp02 data]# df -h Filesystem Size Used Avail Use% Mounted on /dev/xvda2 99G 4.2G 90G 5% / tmpfs 3.9G 228K 3.9G 1% /dev/shm /dev/xvda1 380M 66M 294M 19% /boot /dev/xvda5 386G 22G 345G 6% /data
2、kill掉相应的进程空间就释放了
kill -9 PID
推荐学习:Linux视频教程
The above is the detailed content of What to do if rm deletion does not release space in Linux. For more information, please follow other related articles on the PHP Chinese website!

Hot AI Tools

Undresser.AI Undress
AI-powered app for creating realistic nude photos

AI Clothes Remover
Online AI tool for removing clothes from photos.

Undress AI Tool
Undress images for free

Clothoff.io
AI clothes remover

Video Face Swap
Swap faces in any video effortlessly with our completely free AI face swap tool!

Hot Article

Hot Tools

Notepad++7.3.1
Easy-to-use and free code editor

SublimeText3 Chinese version
Chinese version, very easy to use

Zend Studio 13.0.1
Powerful PHP integrated development environment

Dreamweaver CS6
Visual web development tools

SublimeText3 Mac version
God-level code editing software (SublimeText3)

Hot Topics



How to use Docker Desktop? Docker Desktop is a tool for running Docker containers on local machines. The steps to use include: 1. Install Docker Desktop; 2. Start Docker Desktop; 3. Create Docker image (using Dockerfile); 4. Build Docker image (using docker build); 5. Run Docker container (using docker run).

Docker process viewing method: 1. Docker CLI command: docker ps; 2. Systemd CLI command: systemctl status docker; 3. Docker Compose CLI command: docker-compose ps; 4. Process Explorer (Windows); 5. /proc directory (Linux).

Troubleshooting steps for failed Docker image build: Check Dockerfile syntax and dependency version. Check if the build context contains the required source code and dependencies. View the build log for error details. Use the --target option to build a hierarchical phase to identify failure points. Make sure to use the latest version of Docker engine. Build the image with --t [image-name]:debug mode to debug the problem. Check disk space and make sure it is sufficient. Disable SELinux to prevent interference with the build process. Ask community platforms for help, provide Dockerfiles and build log descriptions for more specific suggestions.

VS Code system requirements: Operating system: Windows 10 and above, macOS 10.12 and above, Linux distribution processor: minimum 1.6 GHz, recommended 2.0 GHz and above memory: minimum 512 MB, recommended 4 GB and above storage space: minimum 250 MB, recommended 1 GB and above other requirements: stable network connection, Xorg/Wayland (Linux)

The reasons for the installation of VS Code extensions may be: network instability, insufficient permissions, system compatibility issues, VS Code version is too old, antivirus software or firewall interference. By checking network connections, permissions, log files, updating VS Code, disabling security software, and restarting VS Code or computers, you can gradually troubleshoot and resolve issues.

VS Code is available on Mac. It has powerful extensions, Git integration, terminal and debugger, and also offers a wealth of setup options. However, for particularly large projects or highly professional development, VS Code may have performance or functional limitations.

VS Code is the full name Visual Studio Code, which is a free and open source cross-platform code editor and development environment developed by Microsoft. It supports a wide range of programming languages and provides syntax highlighting, code automatic completion, code snippets and smart prompts to improve development efficiency. Through a rich extension ecosystem, users can add extensions to specific needs and languages, such as debuggers, code formatting tools, and Git integrations. VS Code also includes an intuitive debugger that helps quickly find and resolve bugs in your code.

How to back up VS Code configurations and extensions? Manually backup the settings file: Copy the key JSON files (settings.json, keybindings.json, extensions.json) to a safe location. Take advantage of VS Code synchronization: enable synchronization with your GitHub account to automatically back up all relevant settings and extensions. Use third-party tools: Back up configurations with reliable tools and provide richer features such as version control and incremental backups.
