From: Heinz Mauelshagen <mauelshagen@redhat.com>
To: LVM general discussion and development <linux-lvm@redhat.com>
Cc: hjm@redhat.com
Subject: Re: [linux-lvm] Meaning of strict allocation
Date: Wed, 14 Apr 2004 10:44:04 +0200 [thread overview]
Message-ID: <20040414084404.GB22343@redhat.com> (raw)
In-Reply-To: <BAY16-DAV32wB0jTj7z000022e2@hotmail.com>
On Thu, Apr 08, 2004 at 07:57:07PM -0700, sachin wrote:
> Hi
>
> when I executed the lvdisplay command i get the following output
>
> --- Logical volume ---
> LV Name /dev/vg/lv1
> VG Name vg
> LV Write Access read/write
> LV Status available
> LV # 1
> # open 0
> LV Size 4 GB
> Current LE 1024
> Allocated LE 1024
> Stripes 4
> Stripe size (KByte) 16
> Allocation next free
> Read ahead sectors 1024
> Block device 58:0
>
> Can any one tell me what that ALLOCATION next free means
> and also what strict allocation means.
'Next free' allocates the next free physical extents it finds in
the VG while extending any logical volume.
There's no 'strict' allocation in LVM.
Your other option is 'contiguous' which means allocation of subsequent areas
of PEs.
>
> I also tried lvdisplay with -v option
>
> it gives me read and writes
> What that exactly means
> 1. No of read and write operation
> 2 No of blocks transferd
> 3. No of sectors read or written
1
>
> One more thing this io statics is from which time
> 1. bootup time
> 2. lv creation time
3. VG activation time (vgchange -ay)
>
> Thanks
> Sachin.
> _______________________________________________
> linux-lvm mailing list
> linux-lvm@redhat.com
> https://www.redhat.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 Red Hat GmbH
Consulting Development Engineer Am Sonnenhang 11
56242 Marienrachdorf
Germany
Mauelshagen@RedHat.com +49 2626 141200
FAX 924446
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
prev parent reply other threads:[~2004-04-14 8:44 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-09 2:57 [linux-lvm] Meaning of strict allocation sachin
2004-04-14 8:44 ` Heinz Mauelshagen [this message]
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=20040414084404.GB22343@redhat.com \
--to=mauelshagen@redhat.com \
--cc=hjm@redhat.com \
--cc=linux-lvm@redhat.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox