thin provisioning in a centos host?
Hi all,
Is it possible to do this? I need to create some sparse volumes/block virtual devices to be served via iscsi target. Thanks _______________________________________________ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos |
thin provisioning in a centos host?
On 12.10.2012 14:43, C. L. Martinez wrote:
> Hi all, > > Is it possible to do this? I need to create some sparse volumes/block > virtual devices to be served via iscsi target. Yes, it is, if you use qcow2 files for example. It would also be possible to use LVM but the feature is still in "experimental" state. -- Sent from the Delta quadrant using Borg technology! Nux! www.nux.ro _______________________________________________ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos Fri Oct 12 19:30:01 2012 Return-Path: <anaconda-devel-list-bounces@redhat.com> X-Spam-Checker-Version: SpamAssassin 3.3.2 (2011-06-06) on eagle542.startdedicated.com X-Spam-Level: X-Spam-Status: No, score=-7.0 required=5.0 tests=DKIM_ADSP_CUSTOM_MED, DKIM_SIGNED,FREEMAIL_FROM,RCVD_IN_DNSWL_HI,RP_MATC HES_RCVD,SPF_HELO_PASS, SPF_PASS,T_DKIM_INVALID autolearn=ham version=3.3.2 X-Original-To: tom@linux-archive.org Delivered-To: tom-linux-archive.org@eagle542.startdedicated.com Received: from mx3-phx2.redhat.com (mx3-phx2.redhat.com [209.132.183.24]) by eagle542.startdedicated.com (Postfix) with ESMTP id 5D89B20E0086 for <tom@linux-archive.org>; Fri, 12 Oct 2012 18:50:37 +0200 (CEST) Received: from lists01.pubmisc.prod.ext.phx2.redhat.com (lists01.pubmisc.prod.ext.phx2.redhat.com [10.5.19.33]) by mx3-phx2.redhat.com (8.13.8/8.13.8) with ESMTP id q9CGlrZ9030200; Fri, 12 Oct 2012 12:47:55 -0400 Received: from int-mx02.intmail.prod.int.phx2.redhat.com (int-mx02.intmail.prod.int.phx2.redhat.com [10.5.11.12]) by lists01.pubmisc.prod.ext.phx2.redhat.com (8.13.8/8.13.8) with ESMTP id q9CGlqq3028378 for <anaconda-devel-list@listman.util.phx.redhat.com>; Fri, 12 Oct 2012 12:47:52 -0400 Received: from mx1.redhat.com (ext-mx16.extmail.prod.ext.phx2.redhat.com [10.5.110.21]) by int-mx02.intmail.prod.int.phx2.redhat.com (8.13.8/8.13.8) with ESMTP id q9CGllYx022207 for <anaconda-devel-list@redhat.com>; Fri, 12 Oct 2012 12:47:47 -0400 Received: from mail-we0-f174.google.com (mail-we0-f174.google.com [74.125.82.174]) by mx1.redhat.com (8.14.4/8.14.4) with ESMTP id q9CGljar007965 for <anaconda-devel-list@redhat.com>; Fri, 12 Oct 2012 12:47:46 -0400 Received: by mail-we0-f174.google.com with SMTP id t9so2043935wey.33 for <anaconda-devel-list@redhat.com>; Fri, 12 Oct 2012 09:47:45 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type:content-transfer-encoding; bh=Eaqy02YDguRfSowqb3QuQGedJWcSa080B17vqC9lP+o=; b=VSl712gKz0t3MYBNUbrm+sukqaf2yOMLmwrHSH+7JUge4Ir4 TB7ECGIqiOakN8p0Jt utnFuhuOrYCq+/2fIVUrgo+Tljeeflcp167w15OVtOHucmjdxOaKJor2pPkhx4PB hCQV U56AhcWcryyaKwqSwRNxVc43CPYawqL/5/jvOVKBrRiuGxewOKFOwQep0XVDGtSyABts b/1TuKkiMtqe2p6zy363nzs18kbE4T3DWxK57/LLkOD+uxX59MK4klO4fPehxtOGjStr 7f2OB06rkX0oPW3mGijMQ71EvFWYWvtmD8pkkpAISjK2iieNtL m6xTxKhSYi9F+uGH+C fLqw== Received: by 10.216.70.13 with SMTP id o13mr3174148wed.184.1350060465227; Fri, 12 Oct 2012 09:47:45 -0700 (PDT) Received: from localhost.localdomain ([217.28.190.130]) by mx.google.com with ESMTPS id eq2sm4575146wib.1.2012.10.12.09.47.42 (version=TLSv1/SSLv3 cipher=OTHER); Fri, 12 Oct 2012 09:47:44 -0700 (PDT) Message-ID: <50784935.1080002@gmail.com> Date: Fri, 12 Oct 2012 16:45:41 +0000 From: =?UTF-8?B?IkrDs2hhbm4gQi4gR3XDsG11bmRzc29uIg==?= <johannbg@gmail.com> User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:15.0) Gecko/20120911 Thunderbird/15.0.1 MIME-Version: 1.0 To: anaconda-devel-list@redhat.com Subject: Re: Root password and the location of the done button References: <tqyfbxt88a4kstwlan5afu4c.1350056799788@email.andr oid.com> In-Reply-To: <tqyfbxt88a4kstwlan5afu4c.1350056799788@email.andr oid.com> X-RedHat-Spam-Score: -2.7 (BAYES_00, DKIM_SIGNED, DKIM_VALID, DKIM_VALID_AU, FREEMAIL_FROM, RCVD_IN_DNSWL_LOW, SPF_PASS) X-Scanned-By: MIMEDefang 2.67 on 10.5.11.12 X-Scanned-By: MIMEDefang 2.68 on 10.5.110.21 X-loop: anaconda-devel-list@redhat.com X-BeenThere: anaconda-devel-list@redhat.com X-Mailman-Version: 2.1.12 Precedence: junk Reply-To: Discussion of Development and Customization of the Red Hat Linux Installer <anaconda-devel-list@redhat.com> List-Id: Discussion of Development and Customization of the Red Hat Linux Installer <anaconda-devel-list.redhat.com> List-Unsubscribe: <https://www.redhat.com/mailman/options/anaconda-devel-list>, <mailto:anaconda-devel-list-request@redhat.com?subject=unsubscribe> List-Archive: <https://www.redhat.com/archives/anaconda-devel-list> List-Post: <mailto:anaconda-devel-list@redhat.com> List-Help: <mailto:anaconda-devel-list-request@redhat.com?subject=help> List-Subscribe: <https://www.redhat.com/mailman/listinfo/anaconda-devel-list>, <mailto:anaconda-devel-list-request@redhat.com?subject=subscribe> Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="us-ascii"; Format="flowed" Sender: anaconda-devel-list-bounces@redhat.com Errors-To: anaconda-devel-list-bounces@redhat.com On 10/12/2012 03:50 PM, Chris Murphy wrote: > The Done button location is not ideal. > > The problem with Root password and Minimal Install I don't understand. But the need to set a password isn't made clear for no-GUI package sets. But you can boot in Rescue/single-user mode and set the root password. The password dialog has been removed from the main hub and put into the actual installing widget and currently is not working there or is working on a whim. We in the QA community require that set password spoke to be present at all time in for all package set because we need to be able to set the root password *always* and have the ability to login not matter what after the initial installation during the development phase to be able to test. You or any designer can try to make the argument here like you are doing that reporters can always workaround the lack of root password by adding various kernel command line switches but that is not true for example if the menu in grub is busted for one reason or another ( two or more such bugs have happened for virtual images in kvm just during this development cycle ) and here is one that happens with beta-tc3 every time I try to type something on the terminal after installing without root password atkbd serio0: Unknown key pressed ( translated set 2, code 0x0 on isa0060&serio0) atkbd serio0: Use 'setkeykeycodes 00 <keycode>' to make it known The harder it gets for reporter to actually test the distribution the fewer and far between they come and shorter they stay ( which is not something we want or need in the project )... JBG _______________________________________________ Anaconda-devel-list mailing list Anaconda-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/anaconda-devel-list |
thin provisioning in a centos host?
On Fri, Oct 12, 2012 at 4:48 PM, Nux! <nux@li.nux.ro> wrote:
> On 12.10.2012 14:43, C. L. Martinez wrote: >> Hi all, >> >> Is it possible to do this? I need to create some sparse volumes/block >> virtual devices to be served via iscsi target. > > Yes, it is, if you use qcow2 files for example. It would also be > possible to use LVM but the feature is still in "experimental" state. > Uhmm .. yes, qcow2 is an option, but it is a very poor option. Performance is horrible when you use an iscsi client to connect to iscsi target serving a qcow2 sparse file .... _______________________________________________ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos |
thin provisioning in a centos host?
On Fri, Oct 12, 2012 at 11:59 AM, C. L. Martinez <carlopmart@gmail.com> wrote:
> >> >> Yes, it is, if you use qcow2 files for example. It would also be >> possible to use LVM but the feature is still in "experimental" state. >> > > Uhmm .. yes, qcow2 is an option, but it is a very poor option. > Performance is horrible when you use an iscsi client to connect to > iscsi target serving a qcow2 sparse file .... I don't really see how this could be done efficiently. I'd probably try running the whole machine under VMware ESXi but wouldn't expect great performance there either. -- Les Mikesell lesmikesell@gmail.com _______________________________________________ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos |
thin provisioning in a centos host?
On Fri, Oct 12, 2012 at 5:24 PM, Les Mikesell <lesmikesell@gmail.com> wrote:
> On Fri, Oct 12, 2012 at 11:59 AM, C. L. Martinez <carlopmart@gmail.com> wrote: >> >>> >>> Yes, it is, if you use qcow2 files for example. It would also be >>> possible to use LVM but the feature is still in "experimental" state. >>> >> >> Uhmm .. yes, qcow2 is an option, but it is a very poor option. >> Performance is horrible when you use an iscsi client to connect to >> iscsi target serving a qcow2 sparse file .... > > I don't really see how this could be done efficiently. I'd probably > try running the whole machine under VMware ESXi but wouldn't expect > great performance there either. > Uhmm lvm will be the option, but Nux had said, it is an experimental feature ... _______________________________________________ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos |
| All times are GMT. The time now is 01:09 AM. |
VBulletin, Copyright ©2000 - 2013, Jelsoft Enterprises Ltd.
Content Relevant URLs by vBSEO ©2007, Crawlability, Inc.