[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

[linux-lvm] lvscan and df result differs

I have just installed lvm on my debian testing server.

I have finally managed to create a PV on a maxtor 
120G disk, the 'pvcreate' command complained about 
a partitiontable being present even if there is no 
table there.
server:~# pvcreate --version
pvcreate: Logical Volume Manager 1.0.4
Heinz Mauelshagen, Sistina Software  02/05/2002 (IOP 10)
I managed to get around that by using a v2 lvm command.
Is there a bug in 1.0.x's pvcreate?

I have also managed to create a VG a and a LV and that
seems to work. I have formatted the LV with ext3 and now
the strange thing is that lvscan reports:
server:~# lvscan 
lvscan -- ACTIVE            "/dev/vg/lg" [114.49 GB]
lvscan -- 1 logical volumes with 114.49 GB total in 1 volume group
lvscan -- 1 active logical volumes
But when using the filesystem df reports:
Filesystem             Size   Used  Avail Use% Mounted on
/dev/hde1             123GB  121GB  2.4GB  99% /store
/dev/vg/lg            122GB  121GB      0 100% /store2

/dev/hde1 is also a 120G disk but with resierfs, ext3
takeing up more size is probably normal. But the actual
size on the lvm is 122G and as you can see I can fit 
121G on the disk, so why is lvscan reporting ~115G? 
Can i safetly use my lvm setup without running the risk
of losing data?



[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]