Displaying 6 results from an estimated 6 matches for "autosnap_2019".
2019 Sep 01
3
vfs_shadow_copy2 not working
Hi Jeremy,
Here's the log with log level 10: https://pastebin.com/0EAuz2B8
The location of the shared folder: /pool/shadowtest
The location of the snapshots: /pool/shadowtest/.zfs/snapshot
Here are how snapshots are named:
autosnap_2019-09-01_13:29:01_daily
autosnap_2019-09-01_13:29:01_hourly
autosnap_2019-09-01_13:44:09_frequently
And this is currently in my smb.conf file:
[shadowtest]
path = /pool/shadowtest
valid users = user1
read only = no
writeable = yes
guest ok = no
create mode = 770
directory mode = 770
vfs objects =...
2019 Aug 10
2
vfs_shadow_copy2 not working
So I'm trying to get shadow copies to work with Windows clients. The snapshots are being stored at /test/.zfs/snapshot
The snapshots are being named like so:
autosnap_2019-08-10_21:00:00_frequently
autosnap_2019-08-10_21:00:00_monthly
autosnap_2019-08-10_22:00:00_hourly
This is in my smb.conf:
[test]
vfs objects = shadow_copy2
shadow:snapdir = /test/.zfs/snapshot
shadow:snapprefix = ^autosnap_
shadow:format = %Y-%m-%d_%H:%M:%S_\(frequently\)\{0,1\}\(hourly\)\{0,1\}...
2019 Sep 02
2
vfs_shadow_copy2 not working
On Sun, Sep 1, 2019 at 3:24 PM douxevip via samba <samba at lists.samba.org>
wrote:
> > The location of the shared folder: /pool/shadowtest
> > The location of the snapshots: /pool/shadowtest/.zfs/snapshot
> > Here are how snapshots are named:
> >
> > autosnap_2019-09-01_13:29:01_daily
> > autosnap_2019-09-01_13:29:01_hourly
> > autosnap_2019-09-01_13:44:09_frequently
> >
I'm not saying this is what your problem is, but if this is FreeBSD < 12,
then MNAMELEN in mount.h is 88. FreeBSD 12 bumps this limit to 1024. This
means that you...
2019 Sep 01
0
vfs_shadow_copy2 not working
...protonmail.com> wrote:
> Hi Jeremy,
>
> Here's the log with log level 10: https://pastebin.com/0EAuz2B8
>
> The location of the shared folder: /pool/shadowtest
> The location of the snapshots: /pool/shadowtest/.zfs/snapshot
> Here are how snapshots are named:
>
> autosnap_2019-09-01_13:29:01_daily
> autosnap_2019-09-01_13:29:01_hourly
> autosnap_2019-09-01_13:44:09_frequently
>
> And this is currently in my smb.conf file:
>
> [shadowtest]
> path = /pool/shadowtest
> valid users = user1
> read only = no
> writeable = yes
> guest ok = no
&g...
2019 Aug 12
0
vfs_shadow_copy2 not working
On Sat, Aug 10, 2019 at 11:22:53PM +0000, douxevip via samba wrote:
> So I'm trying to get shadow copies to work with Windows clients. The snapshots are being stored at /test/.zfs/snapshot
>
> The snapshots are being named like so:
>
> autosnap_2019-08-10_21:00:00_frequently
> autosnap_2019-08-10_21:00:00_monthly
> autosnap_2019-08-10_22:00:00_hourly
>
> This is in my smb.conf:
>
> [test]
> vfs objects = shadow_copy2
> shadow:snapdir = /test/.zfs/snapshot
> shadow:snapprefix = ^autosnap_
> shadow:format = %Y-%m-...
2019 Sep 02
0
vfs_shadow_copy2 not working
...On Sun, Sep 1, 2019 at 3:24 PM douxevip via samba samba at lists.samba.org
> wrote:
>
> > > The location of the shared folder: /pool/shadowtest
> > > The location of the snapshots: /pool/shadowtest/.zfs/snapshot
> > > Here are how snapshots are named:
> > > autosnap_2019-09-01_13:29:01_daily
> > > autosnap_2019-09-01_13:29:01_hourly
> > > autosnap_2019-09-01_13:44:09_frequently
>
> I'm not saying this is what your problem is, but if this is FreeBSD < 12,
> then MNAMELEN in mount.h is 88. FreeBSD 12 bumps this limit to 1024. This
&g...