From: "Heinz J . Mauelshagen" <mauelshagen@sistina.com>
To: linux-lvm@sistina.com
Subject: Re: [linux-lvm] lvcreate contiguous flag question
Date: Mon, 10 Sep 2001 13:15:16 +0200 [thread overview]
Message-ID: <20010910131516.D31313@sistina.com> (raw)
In-Reply-To: <3B9BD5BD.6060606@ida.xs4all.nl>; from lists@ida.xs4all.nl on Sun, Sep 09, 2001 at 10:49:01PM +0200
On Sun, Sep 09, 2001 at 10:49:01PM +0200, Jorg de Jong wrote:
> Hi,
>
> I created a lv with the option --contiguous y.
> But since my disks are rather full the created lv was NOT contiguous.
>
> Strange.
>
> If I try to change the allocation policy from contiguous to next free and to
> contiugues again for this lv, it will fail. It will only let me set it to
> next free. This makes sence since the lv is already fragmented.
>
> But why is a newly created lv that has a allocation policy contiguous
> but is fragmented non the less not reset to next free ? Or not created at all ?
It shouldn't be silently created next free.
Will check the code...
>
> regards,
>
> Jorg de Jong.
>
>
>
>
>
> _______________________________________________
> linux-lvm mailing list
> linux-lvm@sistina.com
> http://lists.sistina.com/mailman/listinfo/linux-lvm
> read the LVM HOW-TO at http://www.sistina.com/lvm/Pages/howto.html
--
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
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
prev parent reply other threads:[~2001-09-10 11:15 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-09-09 20:49 [linux-lvm] lvcreate contiguous flag question Jorg de Jong
2001-09-10 11:15 ` Heinz J . 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=20010910131516.D31313@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox