Linux - ServerThis forum is for the discussion of Linux Software used in a server related context.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Hi,
I have a lubuntu 16.04 server with apache, php, mariadb and moodle 3.2 installed. The name (hostname) of the server is "servweb". It has a 500 Gb SSD hard drive and 24 GB RAM. I have backup copies and I realized that the last backup copy was 450 GB. Checking the files I see that there is a "file" of 430 GB size. The path of this "file" is /dev/mapper/servweb--vg-root but I don't know exactly what it is, if it is a file, a directory or a "reserved space".
I think that if I don't do something about it the system will be blocked, because it will run out of physical space if this "file" continues increasing.
Why is it so big? How can I reduce it, if it is possible? What exactly is this "file"?
/dev/mapper/servweb--vg-root should be a device file, not a regular file, and occupy no space at all. Is the 450GB file only in the backup or also on the live system? In the former case, could it be that the device's contents rather than the device file was copied to the backup?
In case the 450GB are occupied on the live system, the ls -l and file commands will be the first step towards understanding its nature.
/dev/mapper/servweb--vg-root should be a device file, not a regular file, and occupy no space at all. Is the 450GB file only in the backup or also on the live system? In the former case, could it be that the device's contents rather than the device file was copied to the backup?
In case the 450GB are occupied on the live system, the ls -l and file commands will be the first step towards understanding its nature.
I think is also on the live system. I posted results of commands suggested by Syg00.
To easely view this results I attach a capture image.
It would be much easier to put code tags around the output.
In any case, most of your root filesystem is filled up. Have a closer look at /dev/mapper/servweb--vg-root.
It would seem that the servidor volume group used to be called servweb, but somehow the device file was turned into a regular file. You can check that with ls -l and file.
I also recommend you have a look at your LVM configuration. As root, run these commands:
Code:
pvs
vgs
lvs
and post their output (don't forget the code tags; if you don't know what I mean, look down about one centimeter).
It would be much easier to put code tags around the output.
In any case, most of your root filesystem is filled up. Have a closer look at /dev/mapper/servweb--vg-root.
It would seem that the servidor volume group used to be called servweb, but somehow the device file was turned into a regular file. You can check that with ls -l and file.
I also recommend you have a look at your LVM configuration. As root, run these commands:
Code:
pvs
vgs
lvs
and post their output (don't forget the code tags; if you don't know what I mean, look down about one centimeter).
Since you have no servweb volume group, it should be safe to delete /dev/mapper/servweb--vg-root.
I've made a mistake with hostname at the beginning of this post, as you have seen. The hostname is servidorweb (sorry).
Must have a servidorweb volume group?
Must I delete this file (/dev/mapper/servidorweb--vg-root)? If yes, does it will continue working fine?
Do you know, or have any idea, how this file is there?
How can this affect to the performance of the server? (I have no idea about this problem. So I need help and ask a lot of questions. I'm very grateful for helping me).
By the way, the directory /dev/mapper contents this:
Code:
root@servidorweb:/dev/mapper# ls -l
total 0
crw------- 1 root root 10, 236 mar 27 09:39 control
lrwxrwxrwx 1 root root 7 mar 27 09:39 servidorweb--vg-root -> ../dm-0
lrwxrwxrwx 1 root root 7 mar 27 09:39 servidorweb--vg-swap_1 -> ../dm-1
Last edited by llsastre; 04-05-2019 at 09:46 AM.
Reason: adding infomation
What the OP posted seems normal and I suspect that servweb was in error and should be servidorweb in post #1. Don't delete anything in /dev.
As posted in #2 /dev lives in memory only and any big files would be located elsewhere in the directory tree.
This server (servidorweb) has a second hard disk, 2 Tb HDD, for cron local backups (then this backups copy to FTP server by a cron task). This HDD is in /media directory. Now it is about 390 Gb backups. Is it reflected on /dev/mapper/servidorweb--vg-root file perhaps?
The second disk is sdb which does not appear to be mounted from the posted information. No it is not reflected in vg-root. vg-root is your / filesystem, is part of the LVM and lives within the sda5 partition.
Your root filesystem i.e. / is 97% full. Although there is some reserved space which is not included. If sdb failed to mount then any backups would be written to / instead of sdb. Have you checked /media for files?
The second disk is sdb which does not appear to be mounted from the posted information. No it is not reflected in vg-root. vg-root is your / filesystem, is part of the LVM and lives within the sda5 partition.
Your root filesystem i.e. / is 97% full. Although there is some reserved space which is not included. If sdb failed to mount then any backups would be written to / instead of sdb. Have you checked /media for files?
Yes, was it! How silly I am. In /media directory there are two directories: /administrador and /root. Backups copy to /administrador, which is in local SSD, not to /root because sdb was not mounted (I didn't realise it). I've mounted sdb which is in /media/root and I've moved all files from /media/administador to /media/root and I've reviewed script to backup to /media/root and now...
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.