On Wed, May 25, 2016 at 05:05:03PM +0200, tapczan wrote:
> On 25 May 2016 at 16:59, Stéphane Graber wrote:
> > Well, now that's just weird... why would LXD think that /dev/zfs is the
> > backing block for your zpool...
> >
> > Can you paste a "zpool status"?
>
> # zpool
On 25/05/2016 16:05, tapczan wrote:
Hmm, important thing is that this zfs pool is build on top of LVM
volume (which name is "zfs"):
--- Logical volume ---
LV Path/dev/vg0/zfs
LV Namezfs
VG Namevg0
I would expect the logical volume to
On 25 May 2016 at 16:59, Stéphane Graber wrote:
> Well, now that's just weird... why would LXD think that /dev/zfs is the
> backing block for your zpool...
>
> Can you paste a "zpool status"?
# zpool status
pool: lxd
state: ONLINE
scan: none requested
config:
NAME
On Wed, May 25, 2016 at 04:56:10PM +0200, tapczan wrote:
> On 25 May 2016 at 16:50, Stéphane Graber wrote:
> > Can you check through /dev for the device with:
> > - type: block
> > - major: 10
> > - minor: 55
>
> # ls -la /dev/
> crw--- 1 root root 10, 55 May
On 25 May 2016 at 16:50, Stéphane Graber wrote:
> Can you check through /dev for the device with:
> - type: block
> - major: 10
> - minor: 55
# ls -la /dev/
crw--- 1 root root 10, 55 May 25 12:17 zfs
> In general, the LXD code does figure out what the
On Wed, May 25, 2016 at 04:23:07PM +0200, tapczan wrote:
> Hello
>
> As I understand ZFS is recommended filesystem for LXD. However is that
> possible that limiting block I/O resources on ZFS is not working?
>
> # lxc info | grep zfs
> storage: zfs
> storage.zfs_pool_name: lxd
>
>
> # lxc
Hello
As I understand ZFS is recommended filesystem for LXD. However is that
possible that limiting block I/O resources on ZFS is not working?
# lxc info | grep zfs
storage: zfs
storage.zfs_pool_name: lxd
# lxc config device set c1 root limits.read 10MB
error: Block device doesn't support
Hi all,
I am using
# lxc-info --version
2.0.1
and try to create a LXC like this :
# lxc-create --template download -n Alpine-3.3.x --bdev overlayfs -- --dist
alpine --release 3.3 --arch amd64
which works like a charm.
Then I create a snapshot clone :
# lxc-copy --name=Alpine-3.3.x
I've been using btrfs quite a lot and it's great technology. There are
some shortcomings though:
1) compression only really works with compress-force mount argument
On a system which only stores text logs (receiving remote rsyslog logs),
I was gaining around 10% with compress=zlib mount