[SOLVED] ubuntu 19 running out of space when there is plenty of
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.
First of all, I can't see the array in the list. And also, the lv size is being reduced when I copy files to the array. Therefore, the lv will run out of space. Why is that?
The array seems to be mapped into LV's (or just a single one), so is in the mount list as /dev/mapper.
If you would have used the array directly it would have been under a /dev/md (multi-device) path (that is: software RAID, hardware raid is seen as a single device as the O/S doesn't know it IS a RAID one).
You don't see the array because you didn't mount it.
Quote:
And also, the lv size is being reduced when I copy files to the array.
You can't copy files to the array, since you didn't mount it. I guess you copy them from one location in the LV to another, thereby occupying more space.
I just rechecked for a millionth time and now, found out that it was not added in fstab. Just readded it, rebooted the server and not, it shows under df -h
# du -h --max-depth=1 | sort -hr
du: cannot access './proc/2150/task/2150/fd/4': No such file or directory
du: cannot access './proc/2150/task/2150/fdinfo/4': No such file or directory
du: cannot access './proc/2150/fd/3': No such file or directory
du: cannot access './proc/2150/fdinfo/3': No such file or directory
8.9G .
4.4G ./usr
2.7G ./var
1.7G ./snap
201M ./boot
16M ./run
14M ./etc
100K ./root
64K ./home
28K ./mnt
24K ./tmp
16K ./lost+found
8.0K ./media
4.0K ./srv
4.0K ./opt
4.0K ./cdrom
0 ./sys
0 ./proc
0 ./dev
Any files you wrote to /mnt/raid1 when it was not mounted would be using space on the / filesystem.
To find which directories are using the most space. However, it will not show files written to /mnt/raid1 that are on the / filesystem if the raid is mounted.
/mnt/raid1# ls -la
total 24
drwxr-xr-x 3 root root 4096 Mar 20 15:11 .
drwxr-xr-x 4 root root 4096 Mar 20 15:11 ..
drwx------ 2 root root 16384 Mar 20 15:11 lost+found
Code:
/# du -hs * | sort -rh | head -5
du: cannot access 'proc/3800/task/3800/fd/4': No such file or directory
du: cannot access 'proc/3800/task/3800/fdinfo/4': No such file or directory
du: cannot access 'proc/3800/fd/3': No such file or directory
du: cannot access 'proc/3800/fdinfo/3': No such file or directory
4.4G usr
2.7G var
1.7G snap
201M boot
41M run
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.