It was probably the "resize2fs" command which fixed it. Running without any parameters it apart from the partition would extend the partition to use up the remaining space.

Many diskcopy programs copy an exact image of the previous disk so do not necessarily extend the partition to use the extra space as well.

I've got it fixed. Turns out there were disk errors.

I did:

fsck -y /dev/sdb1

resize2fs /dev/sdb1

and now its all working well.

So I'm not sure exactly what went wrong to begin with, but it was your clues that got me set on the right path to fixing it. So thanks.

Please use code tags next time. It makes it so much easier to read.

Are you talking about /dev/sdb1? At least it looks like this has nothing to do with the lvm.

How did you set up the /dev/sdb disk? Did you just do some sort of disk copy or something like dd? If so it will have copied an image of the disk over including the partition size and you will then need to extend the partition to use the whole disk.

Please also give the output to the "mount" command?

You were right. It seems to be reporting the wrong number here.

[root@drsassafras ~]# df -h

Filesystem                Size  Used Avail Use% Mounted on

/dev/mapper/clearos-root  457G   35G  423G   8% /

devtmpfs                  3.9G     0  3.9G   0% /dev

tmpfs                     3.9G  8.0K  3.9G   1% /dev/shm

tmpfs                     3.9G   17M  3.9G   1% /run

tmpfs                     3.9G     0  3.9G   0% /sys/fs/cgroup

/dev/sdb1                 1.8T  1.1T  711G  60% /var/flexshare/shares/plexfiles

/dev/sda1                 3.6T  1.4T  2.1T  42% /media/usb4t

/dev/sdc1                1014M  241M  774M  24% /boot

tmpfs                     795M     0  795M   0% /run/user/992

tmpfs                     795M     0  795M   0% /run/user/0

[root@drsassafras ~]# pvdisplay

  --- Physical volume ---

  PV Name               /dev/sdc2

  VG Name               clearos

  PV Size               464.76 GiB / not usable 3.00 MiB

  Allocatable           yes 

  PE Size               4.00 MiB

  Total PE              118978

  Free PE               1

  Allocated PE          118977

  PV UUID               EpiRxo-X671-4Mrl-V30N-jHuA-KeO6-aJlcC7

[root@drsassafras ~]# 

[root@drsassafras ~]# lvdisplay

  --- Logical volume ---

  LV Path                /dev/clearos/swap

  LV Name                swap

  VG Name                clearos

  LV UUID                EuM1sn-N3E0-06XQ-UfrI-i4sx-cny0-YSrSfW

  LV Write Access        read/write

  LV Creation host, time drsassafras.me, 2017-09-30 15:53:58 -0400

  LV Status              available

  # open                 2

  LV Size                <7.88 GiB

  Current LE             2016

  Segments               1

  Allocation             inherit

  Read ahead sectors     auto

  - currently set to     256

  Block device           253:1

   

  --- Logical volume ---

  LV Path                /dev/clearos/root

  LV Name                root

  VG Name                clearos

  LV UUID                6M40Ry-wral-FAv4-w3mv-bucH-sLKl-9BEpLO

  LV Write Access        read/write

  LV Creation host, time drsassafras.me, 2017-09-30 15:53:58 -0400

  LV Status              available

  # open                 1

  LV Size                <456.88 GiB

  Current LE             116961

  Segments               1

  Allocation             inherit

  Read ahead sectors     auto

  - currently set to     256

  Block device           253:0

   

[root@drsassafras ~]#

I keep mixing the commands up. Please do:

df -h

pvdisplay

lvdisplay

Also what is the contents of "/etc/fstab".

Please put all otput between "code" tags - the piece of paper icon with <> on it.

The output from fdisk -l looks good. I don't understand the output from du -h. The clearos panel still reads incorrectly.


[root@drsassafras ~]# du -h
0 ./.pki/nssdb
0 ./.pki
40K .
[root@drsassafras ~]# fdisk -l
WARNING: fdisk GPT support is currently new, and therefore in an experimental phase. Use at your own discretion.

Disk /dev/sdb: 4000.8 GB, 4000787030016 bytes, 7814037168 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disk label type: gpt
Disk identifier: 56359E1C-FE30-4DD7-A9C1-0F9E4B7EACA1


# Start End Size Type Name
1 2048 7814035455 3.7T Microsoft basic primary

Disk /dev/sdc: 500.1 GB, 500107862016 bytes, 976773168 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk label type: dos
Disk identifier: 0x000ce61e

Device Boot Start End Blocks Id System
/dev/sdc1 * 2048 2099199 1048576 83 Linux
/dev/sdc2 2099200 976773119 487336960 8e Linux LVM
WARNING: fdisk GPT support is currently new, and therefore in an experimental phase. Use at your own discretion.

Disk /dev/sda: 4000.8 GB, 4000787029504 bytes, 7814037167 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 33553920 bytes
Disk label type: gpt
Disk identifier: 94F1E029-DDFD-42C6-A67F-738B586349DA


# Start End Size Type Name
1 65535 7814037133 3.7T Microsoft LDM d
Partition 1 does not start on physical sector boundary.

Disk /dev/mapper/clearos-root: 490.6 GB, 490569990144 bytes, 958144512 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/mapper/clearos-swap: 8455 MB, 8455716864 bytes, 16515072 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes

That output comes straight from "du". Please can you give the output to:

du -h

fdisk -l