similar to: Shadow_copy2 and exposing multiple levels of snapshots

zfs get all claims that i have 523G used by snapshot. i want to get rid of it. but when i look at the space used by each snapshot i can''t find the one that can occupy so much space daten/backups used 959G - daten/backups

Formerly, if you interrupted a zfs receive, it would leave a clone with a % in its name, and you could find it via "zdb -d" and then you could destroy the clone, and then you could destroy the filesystem you had interrupted receiving. That was considered a bug, and it was fixed, I think by Sun. If the lingering clone was discovered laying around, zfs would automatically destroy it.

In the last few days my performance has gone to hell. I''m running: # uname -a SunOS nissan 5.11 snv_150 i86pc i386 i86pc (I''ll upgrade as soon as the desktop hang bug is fixed.) The performance problems seem to be due to excessive I/O on the main disk/pool. The only things I''ve changed recently is that I''ve created and destroyed a snapshot, and I used

Hi (+mailing list again for the archives) My config which does show previous versions: # /usr/local/samba/sbin/smbd --version Version 4.6.11 To avoid having this config block within in each share, I define the following within the [global] section:   shadow:snapprefix = ^\(monthly\)\{0,1\}\(weekly\)\{0,1\}\(daily\)\{0,1\}$   shadow:delimiter = _UTC_   shadow:format =

Hi, I notice you're using 4.6.2 and I'm using 4.6.11. I made the following comment at some point within [global]:   #disable "unix extensions" to avoid using "allow insecure wide links"   #  for access to ../xxxx_SNAPS for BTRFS "previous versions" snapshots   #  --it seems to have reverted once more to not need the below two settings   ##unix

Hi, As per the list.samba.org link, did you try including the delimiter within the format, ie as shown in the following? shadow:snapprefix = ^d[A-Za-z0-9]*y$ shadow:delimiter = _IPG_ shadow:format = _IPG_%Y.%m.%d-%H.%M.%S Regards, Mike On 16/02/2018 16:50, Edouard Guigné via samba wrote: > Hello Dear Samba Users, > > I have sucessfully set a samba share on a centos 7 box (samba 4.6.2)

Hi Alexander # net conf delparm projects shadow:snapprefix does not change a thing. The error persists. (I killed my smb session before trying again). log still says: [2023/05/22 15:23:23.324179,? 1] ../../source3/modules/vfs_shadow_copy2.c:2222(shadow_copy2_get_shadow_copy_data) ? shadow_copy2_get_shadow_copy_data: SMB_VFS_NEXT_OPEN failed for

Hello Dear Samba Users, I have sucessfully set a samba share on a centos 7 box (samba 4.6.2) and succeeded into make work snapshots (vfs_shadow_copy2 with xfs and lvm). The snapshots appears well in windows previous versions. However, I expected to go further with snapshots and use the options "shadow:snapprefix" and "shadow:delimiter"in order to filter daily, weekly

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]

Hi Sebastian, why are you using shadow:snapprefix if this is just ?snap?? Does it work using ONLY shadow:format = snap_GMT-%Y.%m.%d-%H.%M.%S ? If you use snapprefix you also need to use shadow:delimiter (in your case this would be ?_?). However, I never managed to get it working with snapprefix on my machines. Alexander > On Monday, May 22, 2023 at 2:52 PM, Sebastian Neustein via samba

The last email had 1 little error in the smb.conf that I forgot to edit for the email: skyhawk2x4tb was the old poolname, I have it renamed to /pool now, so this is not a source of the problem. ??????? Original Message ??????? On Sunday, September 1, 2019 2:20 PM, douxevip <douxevip at protonmail.com> wrote: > Hi Jeremy, > > Here's the log with log level 10:

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 =

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

Hello all, I already successfully configured shadow copy service without a delimiter and regex. But as soon as I try to get this to work with regex, nothing shows up on the win client. My config looks like this: [global] shadow: localtime = yes shadow: sort = desc shadow: format = _%FT%T shadow: delimiter = _ shadow: snapprefix = ^\(monthly\)\{0,1\}\(weekly\)\{0,1\}\(daily\)\{0,1\}$

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

On 5/23/24 22:58, Andrew Bartlett wrote: > Can you post your smb.conf. Actually no, as I don't have *one* smb.conf. I'll add three of them (the last three were I had this problem) at the end of this email. As you can see they are not exactly identical. > Have you used any of our fallback VFS modules instead of xattrs? I'd say not, but see the smb.confs. > (This would

Release Announcements ===================== This is the first preview release of Samba 4.5. This is *not* intended for production environments and is designed for testing purposes only. Please report any defects via the Samba bug reporting system at https://bugzilla.samba.org/. Samba 4.5 will be the next version of the Samba suite. UPGRADING ========= NTLMv1 authentication disabled by

Release Announcements ===================== This is the first preview release of Samba 4.5. This is *not* intended for production environments and is designed for testing purposes only. Please report any defects via the Samba bug reporting system at https://bugzilla.samba.org/. Samba 4.5 will be the next version of the Samba suite. UPGRADING ========= NTLMv1 authentication disabled by

On Fri, 24 May 2024 23:38:03 +0200 Andrea Venturoli via samba <samba at lists.samba.org> wrote: > On 5/23/24 22:58, Andrew Bartlett wrote: > > > Can you post your smb.conf. > > Actually no, as I don't have *one* smb.conf. > I'll add three of them (the last three were I had this problem) at > the end of this email. > As you can see they are not exactly

Release Announcements ===================== This is the second release candidate of Samba 4.5. This is *not* intended for production environments and is designed for testing purposes only. Please report any defects via the Samba bug reporting system at https://bugzilla.samba.org/. Samba 4.5 will be the next version of the Samba suite. UPGRADING ========= NTLMv1 authentication disabled by