Why does a LVM mapped partition add disk usage to root partition?

The name of the pictureThe name of the pictureThe name of the pictureClash Royale CLAN TAG#URR8PPP








up vote
0
down vote

favorite












Situation

On a server there are separate LVs with their respective mount points for /, /var, and /home.



LV sizes:
/ = 38G ("used": 34G)
/var = 184G (used: 25G)
/home = 680G (used: 270G)



What puzzles me is that df -h shows Use% of 94% for /, corresponding to 34G out of 37G. The real total disk-usage on / is ~5G as I could verify via



~# du -ch --max-depth=1 --exclude=/var --exclude=/home /

4,0K /selinux
4,0K /dev
7,2M /bin
16K /lost+found
93M /boot
8,0K /mnt
7,6M /sbin
6,0M /run
0 /proc
76K /build
0 /sys
432M /etc
643M /lib
4,0K /lib64
11M /root
3,1G /usr
16K /nonexistent
20K /tmp
20K /srv
346M /opt
44K /media
4,6G /
4,6G total


I have checked for all the common known locations of where possibly large files could be hiding, but there is nothing, even checked for the inodes et cetera.



So I am getting suspicious that mounting the LV of /var adds to the disk-usage of /. Is this correct? And if so, what did I do wrong in the LV mapping and how to solve this issue? Then, what is the point of having separate PVs in the first place?










share|improve this question

















  • 1




    Drop to single user mode. Unmount /var. See if there's another /var underneath it.
    – steeldriver
    Jan 27 at 20:12














up vote
0
down vote

favorite












Situation

On a server there are separate LVs with their respective mount points for /, /var, and /home.



LV sizes:
/ = 38G ("used": 34G)
/var = 184G (used: 25G)
/home = 680G (used: 270G)



What puzzles me is that df -h shows Use% of 94% for /, corresponding to 34G out of 37G. The real total disk-usage on / is ~5G as I could verify via



~# du -ch --max-depth=1 --exclude=/var --exclude=/home /

4,0K /selinux
4,0K /dev
7,2M /bin
16K /lost+found
93M /boot
8,0K /mnt
7,6M /sbin
6,0M /run
0 /proc
76K /build
0 /sys
432M /etc
643M /lib
4,0K /lib64
11M /root
3,1G /usr
16K /nonexistent
20K /tmp
20K /srv
346M /opt
44K /media
4,6G /
4,6G total


I have checked for all the common known locations of where possibly large files could be hiding, but there is nothing, even checked for the inodes et cetera.



So I am getting suspicious that mounting the LV of /var adds to the disk-usage of /. Is this correct? And if so, what did I do wrong in the LV mapping and how to solve this issue? Then, what is the point of having separate PVs in the first place?










share|improve this question

















  • 1




    Drop to single user mode. Unmount /var. See if there's another /var underneath it.
    – steeldriver
    Jan 27 at 20:12












up vote
0
down vote

favorite









up vote
0
down vote

favorite











Situation

On a server there are separate LVs with their respective mount points for /, /var, and /home.



LV sizes:
/ = 38G ("used": 34G)
/var = 184G (used: 25G)
/home = 680G (used: 270G)



What puzzles me is that df -h shows Use% of 94% for /, corresponding to 34G out of 37G. The real total disk-usage on / is ~5G as I could verify via



~# du -ch --max-depth=1 --exclude=/var --exclude=/home /

4,0K /selinux
4,0K /dev
7,2M /bin
16K /lost+found
93M /boot
8,0K /mnt
7,6M /sbin
6,0M /run
0 /proc
76K /build
0 /sys
432M /etc
643M /lib
4,0K /lib64
11M /root
3,1G /usr
16K /nonexistent
20K /tmp
20K /srv
346M /opt
44K /media
4,6G /
4,6G total


I have checked for all the common known locations of where possibly large files could be hiding, but there is nothing, even checked for the inodes et cetera.



So I am getting suspicious that mounting the LV of /var adds to the disk-usage of /. Is this correct? And if so, what did I do wrong in the LV mapping and how to solve this issue? Then, what is the point of having separate PVs in the first place?










share|improve this question













Situation

On a server there are separate LVs with their respective mount points for /, /var, and /home.



LV sizes:
/ = 38G ("used": 34G)
/var = 184G (used: 25G)
/home = 680G (used: 270G)



What puzzles me is that df -h shows Use% of 94% for /, corresponding to 34G out of 37G. The real total disk-usage on / is ~5G as I could verify via



~# du -ch --max-depth=1 --exclude=/var --exclude=/home /

4,0K /selinux
4,0K /dev
7,2M /bin
16K /lost+found
93M /boot
8,0K /mnt
7,6M /sbin
6,0M /run
0 /proc
76K /build
0 /sys
432M /etc
643M /lib
4,0K /lib64
11M /root
3,1G /usr
16K /nonexistent
20K /tmp
20K /srv
346M /opt
44K /media
4,6G /
4,6G total


I have checked for all the common known locations of where possibly large files could be hiding, but there is nothing, even checked for the inodes et cetera.



So I am getting suspicious that mounting the LV of /var adds to the disk-usage of /. Is this correct? And if so, what did I do wrong in the LV mapping and how to solve this issue? Then, what is the point of having separate PVs in the first place?







server partitioning mount disk-usage lvm






share|improve this question













share|improve this question











share|improve this question




share|improve this question










asked Jan 27 at 19:39









leonis_csem

193115




193115







  • 1




    Drop to single user mode. Unmount /var. See if there's another /var underneath it.
    – steeldriver
    Jan 27 at 20:12












  • 1




    Drop to single user mode. Unmount /var. See if there's another /var underneath it.
    – steeldriver
    Jan 27 at 20:12







1




1




Drop to single user mode. Unmount /var. See if there's another /var underneath it.
– steeldriver
Jan 27 at 20:12




Drop to single user mode. Unmount /var. See if there's another /var underneath it.
– steeldriver
Jan 27 at 20:12















active

oldest

votes











Your Answer







StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "89"
;
initTagRenderer("".split(" "), "".split(" "), channelOptions);

StackExchange.using("externalEditor", function()
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled)
StackExchange.using("snippets", function()
createEditor();
);

else
createEditor();

);

function createEditor()
StackExchange.prepareEditor(
heartbeatType: 'answer',
convertImagesToLinks: true,
noModals: false,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
);



);













 

draft saved


draft discarded


















StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1000485%2fwhy-does-a-lvm-mapped-partition-add-disk-usage-to-root-partition%23new-answer', 'question_page');

);

Post as a guest



































active

oldest

votes













active

oldest

votes









active

oldest

votes






active

oldest

votes















 

draft saved


draft discarded















































 


draft saved


draft discarded














StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1000485%2fwhy-does-a-lvm-mapped-partition-add-disk-usage-to-root-partition%23new-answer', 'question_page');

);

Post as a guest













































































Popular posts from this blog

Which professions warranted travel in Medieval times?

How do so many people here on Academia.SE, and in general, afford lavish higher education programs?

Trouble downloading packages list due to a “Hash sum mismatch” error