LVM and VxVM
cancel
Showing results for 
Search instead for 
Did you mean: 

bdf output of the lv and filesytem showing different size

 
Highlighted
arunthoray
Occasional Advisor

bdf output of the lv and filesytem showing different size

Output of the bdf command and bdf with lvol parameter showing different size

 

eg:

 

#bdf  /data

Filesystem          kbytes    used   avail %used Mounted on
/dev/vg03/vol4
                   609222656 386209598 210049203   65% /test/opt/data

#bdf  /dev/vg03/vol4


Filesystem          kbytes    used   avail %used Mounted on
/dev/vg03/lvol4
                   609222656 427236041 170612452   71% /test/opt/data

3 REPLIES 3
Highlighted

Re: bdf output of the lv and filesytem showing different size

share the output of mount command .

# mount


Sachin Rajput
================
Highlighted
Emil Velez_2
Trusted Contributor

Re: bdf output of the lv and filesytem showing different size

I am very suprised by this..  I got the same type of output but only the avail column was different by only a little bit.   Suspect it is a minor issue on the calculation but wanted to say I got it too and was suprised.

Emil Velez
Instructor Storage, Servers, HP-UX and Partner Courses
Hewlett Packard Enterprise Education Services
Ask me about training on StoreServ (3PAR) StoreOnce, StoreEasy, StoreAll, StoreVirtual, HP-UX, ServiceGuard and HPE Partner Ready Certification Training

internet: Emil.Velez@hpe.com
Linkedin: http://www.linkedin.com/in/emilvelez

HPE Master ASE Server Solutions Architect V3
HPE Master ASE Storage Solutions Architect V2
HP UNIX Certified (ASE HPUX 11iv3 Administration V1)
Certified HPE Instructor
HPE Product Certified - OneView [2016]
HP Sales Certified -Servers, Converged Systems and Services [2015]
HPE Product Certified - Converged Solutions [2017]
Highlighted
Bill Hassell
Honored Contributor

Re: bdf output of the lv and filesytem showing different size

It is a curious anomaly -- it occurs on 10.20 through 11.31. My guess is that bdf was never designed to look at a device file, so using an lvol (raw or cooked) is getting the information in an unexpected way. Until HP changes the bdf code to either report correctly or disallow device files, the answer is: unsupported



Bill Hassell, sysadmin