search for: thinp

When a disk image uses LVM thinp (thin provisioning), the guestfs_lvs API would return the thinp pools. This confused other APIs because thinp pools don't have corresponding /dev/VG/LV device nodes. Filter the LVs that are returned using "lv_role=public". Thanks: Fabian Deutsch --- daemon/lvm.c | 4 +++- 1 file c...

https://bugzilla.redhat.com/show_bug.cgi?id=984236 kernel-3.10.0-1.fc20.x86_64 Should it be possible to mkfs.btrfs on a virtual LV backed by LVM thinp? I can successfully create an XFS fs on the same virtual device. The virtual LV is 16TB in size, I haven''t tried anything smaller yet to see if that''s the problem. There is a dmesg attached to the bug report. Just because it works with mkfs.xfs doesn''t mean it''s...

On Tuesday 10 November 2015 12:06:21 Richard W.M. Jones wrote: > When a disk image uses LVM thinp (thin provisioning), the guestfs_lvs > API would return the thinp pools. This confused other APIs because > thinp pools don't have corresponding /dev/VG/LV device nodes. > > Filter the LVs that are returned using "lv_role=public". > > Thanks: Fabian Deutsch > -...

...l variables list GSL_LIB, value c:/R/GSL_test2/lib/ GSL_INC, value c:/R/GSL_test2/inc/ The source C code is #include <stdio.h> #include <math.h> #include <stdlib.h> #include <gsl/gsl_rng.h> #include <gsl/gsl_randist.h> #include <R.h> void gibbsGSL(int *Np,int *thinp,int *seedp,double *xvec,double *yvec) { int i,j; int N=*Np,thin=*thinp,seed=*seedp; gsl_rng *r = gsl_rng_alloc(gsl_rng_mt19937); gsl_rng_set(r,seed); double x=0; double y=0; for (i=0;i<N;i++) { for (j=0;j<thin;j++) { x=gsl_ran_gamma(r,3.0,1.0/(y...

...t. GSL_LIB, value c:/R/GSL_test2/lib/ GSL_INC, value c:/R/GSL_test2/inc/ The failing C source code is #include <stdio.h> #include <math.h> #include <stdlib.h> #include <gsl/gsl_rng.h> #include <gsl/gsl_randist.h> #include <R.h> void gibbsGSL(int *Np,int *thinp,int *seedp,double *xvec,double *yvec) { int i,j; int N=*Np,thin=*thinp,seed=*seedp; gsl_rng *r = gsl_rng_alloc(gsl_rng_mt19937); gsl_rng_set(r,seed); double x=0; double y=0; for (i=0;i<N;i++) { for (j=0;j<thin;j++) { x=gsl_ran_gamma(r,3...

Gluster-Users, We currently have a 30 node Gluster Distributed-Replicate 15 x 2 filesystem. Each node has a ~20TB xfs filesystem mounted to /data and the bricks live on /data/brick. We have been very happy with this setup, but are now collecting more data that doesn't need to be replicated because it can be easily regenerated. Most of the data lives on our replicated volume and is

...--type snapshot --virtualsize 1048576K storage) unexpected exit status >> 5: Volume group "storage" has insufficient free space (0 extents): 1 >> required. >> >> When I create thin volume manually, I do not see it: >> >> # lvcreate -n big -V 500G --thinpool storage/lvol1 >> Using default stripesize 64.00 KiB. >> WARNING: Sum of all thin volume sizes (500.00 GiB) exceeds the size of >> thin pool storage/lvol1 and the size of whole volume group (267.93 GiB)! >> For thin pool auto extension activation/thin_pool_a...

...#39;t have enough fingers to count the number of lvm commands. There's so much intricate detail required for creating LVM layouts and doing snapshots and snapshot deletion compared to Btrfs that I've just about given up on LVM. I've also never had Btrfs snapshots explode on me like LVM thinp snapshots have when the metadata pool wasn't made big enough in advance (and it isn't made big enough by default, apparently). Most any typical maneuver done on LVM can be done much more easily and intuitively with Btrfs. So these days I just focus on Btrfs even though I definitely don'...

...;rescue> exit Note (2) The virt-rescue steps could also be done using guestfish (or the API) which is especially useful if you wish to automate any of this. Note (3) There's an entirely different way to think about this, which is also much easier. Make the file sparse (or use qcow2 or LVM thinp), using virt-sparsify. It'll save MORE disk space ... Rich. -- Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones virt-top is 'top' for virtual machines. Tiny program with many powerful monitoring features, net stats, disk stats, logging, etc. http://peop...

...that users are used to being involved in details like making specific partitions in a specific order with specific sizes. The new UI de-emphasizes the need to be involved in that level of detail. It ends up making things more consistent regardless of which "device type" you use: LVM, LVM thinp, standard, or Btrfs. If you emphasize partitions, then you have to emphasize the user needing to know esoteric things. What is NOT obvious: for single device installs, if you omit the size in the create mount point dialog, the size of the resulting volume will consume all remaining space. But sinc...

Le 18/02/2015 09:24, Michael Volz a ?crit : > md127 apparently only uses 81.95GB per disk. Maybe one of the partitions has the wrong size. What's the output of lsblk? I just spent a few hours experimenting with the CentOS 7 installer in a VirtualBox guest with four virtual hard disks. I can now confirm this is a very stupid bug in the (very stupid) installer. Or at least one more random

On 06/27/2011 07:46 AM, NeilBrown wrote: > On Thu, 23 Jun 2011 12:53:37 +0200 Nico Schottelius > <nico-lkml-20110623@schottelius.org> wrote: > >> Good morning devs, >> >> I''m wondering whether the raid- and volume-management-builtin of btrfs is >> actually a sane idea or not. >> Currently we do have md/device-mapper support for raid >>