All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Heinz J . Mauelshagen" <mauelshagen@sistina.com>
To: linux-lvm@sistina.com
Subject: Re: [linux-lvm] lvscan and df result differs
Date: Mon Oct 28 03:07:01 2002	[thread overview]
Message-ID: <20021028100325.B16452@sistina.com> (raw)
In-Reply-To: <1035675002.11490.15.camel@sleep>; from magnus@switchbeat.com on Sun, Oct 27, 2002 at 01:30:01AM +0200

On Sun, Oct 27, 2002 at 01:30:01AM +0200, Magnus Sandberg wrote:
> 
> 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.
> --8<--
> server:~# pvcreate --version
> pvcreate: Logical Volume Manager 1.0.4
> Heinz Mauelshagen, Sistina Software  02/05/2002 (IOP 10)
> --8<--
> I managed to get around that by using a v2 lvm command.
> Is there a bug in 1.0.x's pvcreate?

Did you zero the partition table?
i.e. "dd if=/dev/zero of=/dev/YourWholeDisk count=1 bs=512"

v1 "pvcreate /dev/YourWholeDisk" should work fine then.

> 
> 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:
> --8<--
> 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
> --8<--
> But when using the filesystem df reports:
> --8<--
> Filesystem             Size   Used  Avail Use% Mounted on
> /dev/hde1             123GB  121GB  2.4GB  99% /store
> /dev/vg/lg            122GB  121GB      0 100% /store2
> --8<--
> 
> /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?

Can't reproduce that with df 4.1 here :(
That's probably just the old divide by 1k or 1024 thing.

What does "df -k" say and how does it compare to the lvscan output?

> 
> 
> Thanks,
> 
> /Magnus
> 
> 
> _______________________________________________
> linux-lvm mailing list
> linux-lvm@sistina.com
> http://lists.sistina.com/mailman/listinfo/linux-lvm
> read the LVM HOW-TO at http://tldp.org/HOWTO/LVM-HOWTO/

-- 

Regards,
Heinz    -- The LVM Guy --

*** Software bugs are stupid.
    Nevertheless it needs not so stupid people to solve them ***

=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-

Heinz Mauelshagen                                 Sistina Software Inc.
Senior Consultant/Developer                       Am Sonnenhang 11
                                                  56242 Marienrachdorf
                                                  Germany
Mauelshagen@Sistina.com                           +49 2626 141200
                                                       FAX 924446
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-

  reply	other threads:[~2002-10-28  3:07 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-10-26 18:31 [linux-lvm] lvscan and df result differs Magnus Sandberg
2002-10-28  3:07 ` Heinz J . Mauelshagen [this message]
2002-10-28  9:24   ` Magnus Sandberg
2002-10-28  9:38     ` James Hawtin

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20021028100325.B16452@sistina.com \
    --to=mauelshagen@sistina.com \
    --cc=linux-lvm@sistina.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.