search for: snapdirs

Hello, i installed zfs-auto-snapshot with Samba/Windows Shadow Copy. If the share contains "path = /srv/userdata/" it runs for me. But if I use "path = /srv/userdata/%U" I get no "Previous Versions" on my Win10 Client. I think the problem is the variable "shadow: snapdir = .zfs/snapshot". I tried with "shadow: snapdir = ../.zfs/snapshot" and

I was looking at a case where I have a 'Documents' dir mounted from my server. It's setup is: [Documents] acl group control = yes block size = 4096 store dos attributes = yes map acl inherit = yes inherit acls = yes comment = Domain User's Home Documents path = /home/%D/Documents/%U vfs objects = recycle, readahead, shadow_copy2 recycle:

OS platform: FreeBSD 10.1-RELEASE-p25 Filesystem: ZFS Samba version: upgraded from 4.1.17 to 4.1.22 Problem: I have been using the shadow_copy2 and zfsacl VFS modules to enable access control and the Previous Versions feature for Windows clients. With /usr/local/etc/smb4.conf configured this way (excerpt): vfs objects = shadow_copy2 zfsacl shadow:snapdir = .zfs/snapshot

Hi there I'm having some troubles with Shadow Copy2 & zfs Snapshots. I have hourly and daily snapshots. If I use the following settings it works (but omits daily snapshots): vfs objects = shadow_copy2 shadow:snapdir = .zfs/snapshot shadow:sort = desc shadow:localtime = yes shadow:format = easysnap-hourly_%Y-%m-%d-%H-%M-UTC However when I try to use the BRE with the prefix,

Author: lling Repository: /hg/zfs-crypto/gate Revision: 2de9ffe8718409582bf049abea4af81f06a89482 Log message: 6399899 change the default value of snapdir property to "hidden" Files: update: usr/src/common/zfs/zfs_prop.c

I have: interfaces = lo0, eth2 and: socket address = 192.168.3.1 socket address = 127.0.0.l in my smb.conf, but when I try to "net group add anything" (on server running samba 3.5.2, as a DC): <asks for current log'ed in users's password> mypwd Could not connect to server 127.0.0.1 Connection failed: NT_STATUS_CONNECTION_REFUSED So what am I missing? Shouldn't

...ether for moving, cloning, sizing, etc, you can''t view .zfs/ from within the zone because the zone root is one dir down: /zones <-- Dataset /zones/myzone01 <-- Dataset, .zfs is located here. /zones/myzone01/root <-- Directory, want .zfs Here! The ultimate idea is to make ZFS snapdirs accessable from within the zone. benr. This message posted from opensolaris.org

On Thu, Aug 2, 2018 at 11:11 AM, Rowland Penny via samba < samba at lists.samba.org> wrote: > On Thu, 2 Aug 2018 11:02:45 -0400 > pisymbol <pisymbol at gmail.com> wrote: > > > Whoops! Replying to all! > > > > On Thu, Aug 2, 2018 at 10:55 AM, Rowland Penny via samba < > > samba at lists.samba.org> wrote: > > > > > On Thu, 2 Aug 2018

...level = 1 [applied] path = /mnt/trunk/MM/applied printable = no veto files = /.snapshot/.windows/.mac/.zfs/ writeable = yes browseable = yes shadow:snapdir = .zfs/snapshot shadow:sort = desc shadow:localtime = yes shadow:format = auto-%Y%m%d.%H%M-1w shadow:snapdirseverywhere = yes vfs objects = shadow_copy2 zfs_space zfsacl aio_pthread streams_xattr hide dot files = yes guest ok = no nfs4:mode = special nfs4:acedup = merge nfs4:chown = true zfsacl:acesort = dontcare veto oplock files = /*.dbf/*.DBF/*.ndx/*.NDX/ [deploy] p...

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]

Hello, Thank you everyone in advance for your time and support? I am the Administrator of a small network, with about 60 desktops (mostly windows 10) that connect to a Linux VM running samba for file sharing).? In the last few months I completed the transition from the Samba server running as a vm on an OpenVZ machine.? It was running Centos 6, with an older version of samba.? Now the server has

On Fri, Jan 01, 2016 at 09:38:09PM +0800, QIU Quan wrote: > OS platform: FreeBSD 10.1-RELEASE-p25 > Filesystem: ZFS > Samba version: upgraded from 4.1.17 to 4.1.22 > > Problem: > > I have been using the shadow_copy2 and zfsacl VFS modules to enable > access control and the Previous Versions feature for Windows clients. > With /usr/local/etc/smb4.conf configured this

I have "/home" as a logical volume. I have snapshots: LV VG Attr LSize Origin Snap% Move Log Copy% Convert 2010.02.05-01.26.19 Home swi-ao 10.00G lvol0 39.81 2010.02.06-02.37.52 Home swi-ao 5.00G lvol0 0.25 lvol0 Home owi-ao 1.00T and they are mounted:

Whoops! Replying to all! On Thu, Aug 2, 2018 at 10:55 AM, Rowland Penny via samba < samba at lists.samba.org> wrote: > On Thu, 2 Aug 2018 10:43:26 -0400 > pisymbol via samba <samba at lists.samba.org> wrote: > > > Full disclosure: This is an exported share on a QNAP NAS device. > > Even fuller disclosure ;-) > You haven't given us enough info > I can

Forgot to CC the list. -------- Original Message -------- SUBJECT: Re: [Samba] Can't add users to well known groups... DATE: Mon, 12 Sep 2011 15:51:31 +0200 FROM: Fran?ois Legal TO: Linda Walsh Not sure if this is relevant, but if (first case shown down here) "Domain Admins" is not so much a group but a map to unix group, I'm not surprised that you

On Thu, 2 Aug 2018 11:17:47 -0400 pisymbol <pisymbol at gmail.com> wrote: > On Thu, Aug 2, 2018 at 11:11 AM, Rowland Penny via samba < > samba at lists.samba.org> wrote: > > > On Thu, 2 Aug 2018 11:02:45 -0400 > > pisymbol <pisymbol at gmail.com> wrote: > > > > > Whoops! Replying to all! > > > > > > On Thu, Aug 2, 2018 at

Does anyone have scripts they use for doing this automatically that they use? I'd like to compare it to mine and see what features I might have left out that I might want... Currently nightly, the script determines the changes during the day (snaps take about 60-150 minutes to create, so once a day is all I do right now). It uses a simple config-file to drive what directories to ignore and

...= /tmp/ctdb.socket gpfs:sharemodes = yes gpfs:winattr = yes gpfs:leases = yes gpfs:dfreequota = yes nfs4:mode = simple nfs4:chown = yes nfs4:acedup = merge fileid:algorithm = fsname force unknown acl user = yes shadow:snapdir = .snapshots shadow:fixinodes = yes shadow:snapdirseverywhere = yes shadow:sort = desc syncops:onclose = no syncops:onmeta = no kernel oplocks = yes level2 oplocks = yes oplocks = yes notify:inotify = no wide links = no async smb echo handler = yes dmapi support = yes aio write size = 1 aio read size = 1 sock...

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 =

...d > printable = no > veto files = /.snapshot/.windows/.mac/.zfs/ > writeable = yes > browseable = yes > shadow:snapdir = .zfs/snapshot > shadow:sort = desc > shadow:localtime = yes > shadow:format = auto-%Y%m%d.%H%M-1w > shadow:snapdirseverywhere = yes > vfs objects = shadow_copy2 zfs_space zfsacl aio_pthread streams_xattr > hide dot files = yes > guest ok = no > nfs4:mode = special > nfs4:acedup = merge > nfs4:chown = true > zfsacl:acesort = dontcare > veto oplock fi...