Df -h does not tally Post: 303004098

Sponsored Content

Top Forums UNIX for Beginners Questions & Answers Df -h does not tally Post 303004098 by desind on Tuesday 26th of September 2017 02:10:57 PM

09-26-2017

Registered User

Df -h does not tally

Hi,

My df -h numbers do not tally.

Code:

desind@abc123:~#> df -h
Filesystem      Size  Used Avail Use% Mounted on
/dev/xvda1       99G  6.9G   87G   8% /
tmpfs            16G     0   16G   0% /dev/shm
/dev/xvdi        50G   53M   47G   1% /home
/dev/xvdb       985G   72M  935G   1% /kafka/data/sda
/dev/xvdc       985G   19G  916G   3% /kafka/data/sdb
/dev/xvdd       985G   19G  916G   3% /kafka/data/sdc
/dev/xvde       985G   76G  859G   9% /kafka/data/sdd
/dev/xvdj        20G   44M   19G   1% /abv/monitoring
/dev/xvdf        69G  3.1G   63G   5% /cxt/sfw
/dev/xvdl       7.8G   19M  7.4G   1% /tmp
/dev/xvdg       9.8G  3.1G  6.2G  34% /var
/dev/xvdh        50G  205M   47G   1% /var/log
cm_processes     16G  168M   16G   2% /var/run/cloudera-scm-agent/process
/dev/xvdk        79G  214M   75G   1% /fgv/pep

I am concerned about the /kafka/data/* directories.

for example /kafka/data/sdd the used column is incorrect.

i did a du and the number still says 76G

Code:

desind@abc123:/kafka/data/sdd#> sudo du -sh
76G

If total size is 985G and used is 76G, then the available disk must be 909G

Is this a bug in redhat linux 6.7 ? can i check that is the exact usage ?

Last edited by desind; 09-26-2017 at 03:15 PM.. Reason: code tags

desind

View Public Profile for desind

Find all posts by desind

LEARN ABOUT OSF1

vgimportclone

VGIMPORTCLONE(8)					      System Manager's Manual						  VGIMPORTCLONE(8)

NAME

       vgimportclone - import and rename duplicated volume group (e.g. a hardware snapshot)

SYNOPSIS

       vgimportclone [-n|--basevgname VolumeGroupName] [-i|--import] PhysicalVolume [PhysicalVolume...]

DESCRIPTION

       vgimportclone is used to import a duplicated VG (e.g. hardware snapshot).  Duplicate VG(s) and PV(s) are not able to be used until they are
       made to coexist with the origin VG(s) and PV(s).  vgimportclone renames the VG associated with the specified PV(s) and changes the  associ-
       ated VG and PV UUIDs.

OPTIONS

       See lvm for common options.

       -n|--basevgname VolumeGroupName
	      By  default  the	snapshot  VG  will be renamed to the original name plus a numeric suffix to avoid duplicate naming (e.g. 'test_vg'
	      would be renamed to 'test_vg1').	This option will override the base VG name that is used for all  VG  renames.	If  a  VG  already
	      exists with the specified name a numeric suffix will be added (like the previous example) to make it unique.

       -i|--import
	      Import exported Volume Groups.  Otherwise VGs that have been exported will not be changed (nor will their associated PVs).

ENVIRONMENT VARIABLES

       LVM_BINARY
	      The LVM2 binary to use.  Defaults to "lvm".

EXAMPLES

       The  origin VG vg00 has origin PVs /dev/sda and /dev/sdb and the respective snapshot PVs are /dev/sdc and /dev/sdd.  To rename the VG asso-
       ciated with /dev/sdc and /dev/sdd from vg00 to vg00_snap (and to change associated VG and PV UUIDs) do:

	    vgimportclone --basevgname vg00_snap /dev/sdc /dev/sdd

SEE ALSO

       lvm(8)

Red Hat, Inc.						 LVM TOOLS 2.02.95(2) (2012-03-06)					  VGIMPORTCLONE(8)