From: "Heinz J. Mauelshagen" <Mauelshagen@sistina.com>
To: linux-lvm@sistina.com
Subject: Re: [linux-lvm] LVM questions & problems.
Date: Mon, 7 May 2001 10:28:44 +0000 [thread overview]
Message-ID: <20010507102844.B25752@sistina.com> (raw)
In-Reply-To: <989197513.8109.6.camel@localhost>; from raheesom@navpoint.com on Sun, May 06, 2001 at 09:05:13PM -0400
On Sun, May 06, 2001 at 09:05:13PM -0400, Rupert Heesom wrote:
> I'm practicing doing some LVM commands, and am coming up with some
> problems -
>
> Most disconcerting is that when I try to create a directory in the LV, I
> get the following error - (this does not happen all the time, but almost
> all the time 99%) -
>
> [root@localhost Tmp]# mkdir test1
> mkdir: cannot create directory `test1': Input/output error
You didn't metion, if the filesystem is still in a sane state.
Did you check your syslog for "accessess beyond the end of the device"
which indicate fs related problems?
If so: did you run fsck to fix those and did you retest?
>
> Creating normal files on the LV is not a problem.
>
> Also, the figures in the following outputs don't seem to make sense to
> me -
>
> 287Mb of space taken on my LV lvol1 (shown using du -h).
du is a filesystem tool which tells you how much space is used
from the fs perspective.
The LV tools provide information from the underlying block device being
exposed by the LVM to the filesytem or other users (like databases etc.).
>
> LV lvol1 - shows all 75 logical extends taken, I'm assuming filling up
> the 300Mb LV size.
>
> LV Size 300 MB
> Current LE 75
> Allocated LE 75
O.k.
That shows, that you have a 300M logical volume, which you said above.
vgdisplay on your volume group gives you (beside other information)
the size of the physical extents (PEs) which is 4M by default.
You can change that in order to address bigger configurations with
"vgcreate -s". Please see "man vgcreate" for further details.
>
>
> PV shows too many physical extends used for the proportion of disk space
> used. -
>
> Total PE 76
> Free PE 1
That's ok because you allocated 75PEs which are 300M based on
4M PE size.
>
> PVdisplay shows too many physical extents used again
>
> Total PE 76
> Free PE 1
> Allocated PE 75
Same as above.
Please have a look at the LVM howto at www.sistina.com/lvm
for further hints on LVM usage.
Regards,
Heinz -- The LVM Guy --
>
>
> ----------------------------------------
>
> LVM command outputs
> -------------------
>
> [root@localhost Tmp]# lvdisplay /dev/vg/lvol1
> lvdisplay
> --- Logical volume ---
> LV Name /dev/vg/lvol1
> VG Name vg
> LV Write Access read/write
> LV Status available
> LV # 1
> # open 1
> LV Size 300 MB
> Current LE 75
> Allocated LE 75
> Allocation next free
> Read ahead sectors 120
> Block device 58:0
>
>
> [root@localhost Tmp]# pvdisplay /dev/sdb1
> pvdisplay
> --- Physical volume ---
> PV Name /dev/sdb1
> VG Name vg
> PV Size 305.89 MB / NOT usable 1.89 MB [LVM: 121 KB]
> PV# 1
> PV Status available
> Allocatable yes
> Cur LV 1
> PE Size (KByte) 4096
> Total PE 76
> Free PE 1
> Allocated PE 75
> PV UUID wm3nGp-pEem-0byC-3JOs-OFs4-3kv2-EkPxaK
>
>
> [root@localhost Tmp]# vgdisplay
> vgdisplay
> --- Volume group ---
> VG Name vg
> VG Access read/write
> VG Status available/resizable
> VG # 0
> MAX LV 256
> Cur LV 1
> Open LV 1
> MAX LV Size 255.99 GB
> Max PV 256
> Cur PV 1
> Act PV 1
> VG Size 304 MB
> PE Size 4 MB
> Total PE 76
> Alloc PE / Size 75 / 300 MB
> Free PE / Size 1 / 4 MB
> VG UUID 0ZyZNT-53L9-tAFJ-GCa4-1Zr5-nZli-IFIbIP
>
>
> --
> regs
> rupert
>
> _______________________________________________
> linux-lvm mailing list
> linux-lvm@sistina.com
> http://lists.sistina.com/mailman/listinfo/linux-lvm
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Heinz Mauelshagen Sistina Software Inc.
Senior Consultant/Developer Am Sonnenhang 11
56242 Marienrachdorf
Germany
Mauelshagen@Sistina.com +49 2626 141200
FAX 924446
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
next prev parent reply other threads:[~2001-05-07 10:28 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-05-07 1:05 [linux-lvm] LVM questions & problems Rupert Heesom
2001-05-07 10:28 ` Heinz J. Mauelshagen [this message]
2001-05-07 15:57 ` Rupert Heesom
2001-05-08 9:45 ` Heinz J. Mauelshagen
2001-05-08 16:25 ` Andreas Dilger
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=20010507102844.B25752@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.