[pve-devel] /var/lib/vz as a dataset

While we are on the subject of /var/lib/vz… Does anyone see a problem with having the “local” storage be a zfs dataset. I don’t really need it, but I can’t delete it from the UI. I need to exclude the dir from my znapzend auto-snapshot plan. I succeeded by doing: zfs create -o

Re: [pve-devel] easy one: ls /var/lib/vz for me plz

> On Jun 16, 2016, at 21:40, Michael Rasmussen wrote: > > I guess root is for OpenVZ > Oh, I hinted at “zfs” thinking it would be obvious, but I guess it’s not since zfs appeared prior to proxmox 4.x. So I am running 4.2-5 (no OpenVZ). Thanks for the quick answer.

Re: [pve-devel] easy one: ls /var/lib/vz for me plz

> On Jun 16, 2016, at 21:29, Jean-Francois Dagenais <jeff.dagen...@gmail.com> > wrote: > > Hi all, > > Accidentally deleted one (I think, don’t know which) directory in > /var/lib/vz… Ironically, I was actually in the process of setting up znapzend > to periodi

[pve-devel] easy one: ls /var/lib/vz for me plz

Hi all, Accidentally deleted one (I think, don’t know which) directory in /var/lib/vz… Ironically, I was actually in the process of setting up znapzend to periodically snapshot my zfs datasets to prevent exactly this kind of accident! Super odd. Could someone show me their “ls /var/lib/vz” so

Re: [pve-devel] [PATCH manager 2/2] vzdump: make exclude-path from config file work again

> On Mar 3, 2016, at 09:34, Jean-Francois Dagenais <jeff.dagen...@gmail.com> > wrote: > > Contrary to the docs (wiki, man page, etc.), the '/dir/.+' notation doesn't > seem > to work here. If I put these instead in vzdump.conf: '/dir/*' then it works. > > Same

Re: [pve-devel] [PATCH manager 2/2] vzdump: make exclude-path from config file work again

While we are on the subject of vzdump. One thing that fails when restoring dumps is the lack of the original directory structure. Here's an example: /var/log/?* is excluded, however, there are subdirectories in there which were carefully created by a package managers (APT or RPM) at package

[pve-devel] [PATCH] vzdump: make sure only DOT pid files excluded

and not files like "acpid" Signed-off-by: Jean-Francois Dagenais <jeff.dagen...@gmail.com> --- PVE/VZDump.pm | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/PVE/VZDump.pm b/PVE/VZDump.pm index 8f5af3f..a3d1f2c 100644 --- a/PVE/VZDump.pm +++ b/PVE/VZDump.pm

Re: [pve-devel] [PATCH manager 2/2] vzdump: make exclude-path from config file work again

> On Mar 3, 2016, at 03:22, Wolfgang Bumiller wrote: > > Call split_args() on the 'exclude-path' option read from > /etc/vzdump.conf > > With the move to the generic JSONSchema::parse_config() in > commit 16145cba the call to split_args() for 'exclude-path' > was

Re: [pve-devel] [PATCH manager 1/2] vzdump: revert /var/run stdexclude entry to its original

> On Mar 3, 2016, at 03:55, Wolfgang Bumiller wrote: > > It used to be /var/run/.+pid when we used regular > expressions so now it should be /var/run/?*pid > --- > PVE/VZDump.pm | 2 +- > 1 file changed, 1 insertion(+), 1 deletion(-) > > diff --git a/PVE/VZDump.pm

[pve-devel] vzdump.conf exclude-path parsing

Hi all, First time poster. I've been digging into a problem I am getting with Proxmox VE 4.1-15. I am specifying a pattern in "exclude-path" and am getting a perl error: Can't use string (""/dir1/.+" "/dir2/.+"") as an ARRAY ref while "strict refs" in use at /usr/share/perl5/PVE/VZDump.pm line