On Tue, Jul 31, 2018 at 02:35:42PM +0200, Zdenek Kabelac wrote:
> If you monitor amount of free space for data AND for metadata in thin-pool
> yourself you can keep easily threshold == 100.
Understood. Two things:
1) basically threshold < 100 allows you to hit the limit, have LVM pause
IO, alloca
On Fri, Jul 27, 2018 at 11:26:58AM -0700, Marc MERLIN wrote:
> Hi Zdenek,
>
> Thanks for your helpful reply.
Ha again Zdenek,
Just to confirm, am I going to be ok enough with the scheme I described
as long as I ensure that 'Allocated pool data' does not get to 100% ?
For n
On Fri, Jul 27, 2018 at 05:09:54PM -0400, John Stoffel wrote:
> That's the key part that I didn't realize. And this is why I'm still
> leary of btrfs (and zfs for that matter) since as you push the limits,
> they tend to fall off a cliff performance wise, instead of degrading
> more gracefully. S
On Fri, Jul 27, 2018 at 03:31:36PM -0400, John Stoffel wrote:
> Why don't you run quotas on your filesystems? Also, none of the
> filesystems in Linux land that I'm aware of supports shrinking the
> filesystem while live, it's all a unmount, shrink FS, shrink volume
> (carefully!) and then re-moun
On Fri, Jul 27, 2018 at 02:43:21PM +0200, Zdenek Kabelac wrote:
> >It's looking better now:
> >gargamel:~# lvcreate -L 14.50TiB -Zn -T vgds2/thinpool2
> > Using default stripesize 64.00 KiB.
> > Thin pool volume with chunk size 8.00 MiB can address at most <1.98 PiB
> > of data.
> > semid
Hi Zdenek,
Thanks for your helpful reply.
On Fri, Jul 27, 2018 at 02:59:28PM +0200, Zdenek Kabelac wrote:
> Dne 26.7.2018 v 18:31 Marc MERLIN napsal(a):
> >Still learning about thin volumes.
> >Why do I want my thin pool to get auto extended? Does "extended" mean
> &g
Still learning about thin volumes.
Why do I want my thin pool to get auto extended? Does "extended" mean
resized?
Why would I want to have thin_pool_autoextend_threshold below 100 and
have it auto extend as needed vs having all of them be at 100, knowing
that underlying block allocation will fail
On Thu, Jul 26, 2018 at 10:40:42AM +0200, Zdenek Kabelac wrote:
> What are you trying to achieve with 'mkdir /dev/vgds2/' ?
> You shall never ever touch /dev content - it's always under full control
> of udev - if you start to create there your own files and directories you
> will break whole usa
On Wed, Jul 25, 2018 at 05:41:54PM -0700, Marc MERLIN wrote:
> Howdy,
>
> Kernel 4.17, trying thin LV for the first time, and I'm getting this:
> gargamel:~# lvcreate -L 14.50TiB -Zn -T vgds2/thinpool2
> Using default stripesize 64.00 KiB.
> Thin pool volume with
Howdy,
Kernel 4.17, trying thin LV for the first time, and I'm getting this:
gargamel:~# lvcreate -L 14.50TiB -Zn -T vgds2/thinpool2
Using default stripesize 64.00 KiB.
Thin pool volume with chunk size 8.00 MiB can address at most <1.98 PiB of
data.
/dev/mapper/vgds2-thinpool2_tmeta: open
10 matches
Mail list logo
