similar to: vfs_shadow_copy2 cannot read/find snapshots

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

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

The gluster side looks like this: root at B741:~# gluster volume get glvol_samba features.show-snapshot-directory features.show-snapshot-directory???????? on root at B741:~# gluster volume get glvol_samba features.uss features.uss???????????????????????????? enable I found an error when the samba client is mounting the gluster volume in the gluster logs

On Wed, 2023-05-24 at 14:38 +0200, Sebastian Neustein via samba wrote: > > In addition to that there will be a log file corresponding to the > > FUSE mount of GlusterFS volume under /var/log/glusterfs with mount > > point as log file name? Please check if there are any warning/error > > entries while trying to list previous versions from windows. > Yes, there is a file

I?ve never had such situation and I don?t recall someone sharing something similar. Most probably it?s easier to remove the node from the TSP and re-add it.Of course , test the case in VMs just to validate that it?s possible to add a mode to a cluster with snapshots. I have a vague feeling that you will need to delete all snapshots. Best Regards,Strahil Nikolov? On Thursday, August 10, 2023, 4:36

> Does it make a difference if you re-mount the volume without 'acl' > option? Even otherwise can you try listing the snapshot contents from > the server as a user(and not super user) who in reality tries to list > previous versions from Windows? I feel like it has something to do with > permissions setup for the user accessing the share. It does make a difference! First

22 May 2023 8:11:33 pm Sebastian Neustein via samba <samba at lists.samba.org>: > I found an error when the samba client is mounting the gluster volume in the gluster logs (/var/log/glusterfs/snaps/glvol_samba/snapd.log) > [2023-05-22 12:52:09.438169 +0000] E [server-handshake.c:156:server_first_lookup] 0-snapd-glvol_samba: lookup on root failed: argument is not valid > (the last

On Mon, May 22, 2023 at 9:32?AM Sebastian Neustein via samba <samba at lists.samba.org> wrote: > > 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] >

On Thu, 2023-05-25 at 16:45 +0200, Sebastian Neustein wrote: > > Does it make a difference if you re-mount the volume without 'acl' > > option? Even otherwise can you try listing the snapshot contents > > from the server as a user(and not super user) who in reality tries > > to list previous versions from Windows? I feel like it has > > something to do with

Hi Due to an outage of one node, after bringing it up again, the node has some orphaned snapshosts, which are already deleted on the other nodes. How can I delete these orphaned snapshots? Trying the normal way produceses these errors: |[2023-08-08 19:34:03.667109 +0000] E [MSGID: 106115] [glusterd-mgmt.c:118:gd_mgmt_v3_collate_errors] 0-management: Pre Validation failed on B742. Please

Hi I am having a problem deleting snapshots, gluster is failing to unmount them. I am running centos 7.3 with gluster-3.10.2-1 here is some log output: [2017-05-31 09:21:39.961371] W [MSGID: 106057] [glusterd-snapshot-utils.c:410:glusterd_snap_volinfo_find] 0-management: Snap volume 331ec972f90d494d8a86dd4f69d718b7.glust01-li.run-gluster-snaps-331ec972f90d494d8a86dd4f69d718b7-brick1-b not found

On 8/18/23 09:55, Sebastian Neustein via samba wrote: > With the default settings of vfs_acl_xattr samba takes posix acls into > account when delivering data - how can I activate > "acl_xattr:ignore system acls = yes" > without loosing the information saved in posix acls? Background: our > future file system won't be able to support acls. Sorry, but this is

Does you filesystem support extended attributes? What does "|getfattr -n security.NTACL |filename" return?|| On 30.01.2024 16:13, Peter Milesson wrote: > Hi folks, > > It seems that the setting acl_xattr:ignore system acls = yes reduces > Windows compatibility when defined for a share. In all attempts I have > used Windows tools (except editing smb.conf) > > Assume

Hi folks, It seems that the setting acl_xattr:ignore system acls = yes reduces Windows compatibility when defined for a share. In all attempts I have used Windows tools (except editing smb.conf) Assume there is a share, where the files and folders in the share root should at least be readable by anybody having access to the share. For the sake of simplicity the following permissions apply on

Hi, I have replications problems on one of my server. Replication was working since month and yet stopped working. on the remote server: islad01:~ # samba-tool drs showrepl | more Default-First-Site-Name\ISLAD01 DSA Options: 0x00000001 DSA object GUID: 3fe6bc7c-1116-4344-96a6-c58c43bc217f DSA invocationId: 89351eec-7207-45f5-b6b9-cebfcacfd0e3 ==== INBOUND NEIGHBORS ====

Hi Ralph > On 8/18/23 09:55, Sebastian Neustein via samba wrote: >> With the default settings of vfs_acl_xattr samba takes posix acls >> into account when delivering data - how can I activate >> "acl_xattr:ignore system acls = yes" >> without loosing the information saved in posix acls? Background: our >> future file system won't be able to support

Hello. After fresh install. Samba and ldap seems to run normally ( I can join win2k workstation to linux samba pdc ). Using yast I create a system group named domadmin But I am unable to map "Domain Admins" to domadmin I am unable to map "Domain Admins" to existing ntadmin group I am unable to mofify mapping "Domain Admins" to domadmin group Thank you for

Hi list, hi John, having seen last week a post (see http://marc.theaimsgroup.com/?m=107341768923846) that remind me some quirks I encountered, I'd like to see a preamble added to the chapter 12 of the howto. It concerns the diffent types of admin you will need in a PDC setup. I say preamble, but it could be found anywhere else, as long as it could be found (I have lost long hours

Hi I've been running Samba 2.x for years but decided to move up to 3.0.2. I've set up a new samba server with a workgroup NEWBIOSS and netbios name PARETO. Im having problems setting up my domain admins. I used 'net groupmap modify "Domain Admins" unixgroup=domadmin' my 'net groupmap list' shows : System Operators (S-1-5-32-549) -> -1 Replicators

Dear Samba Friends, I've a problem to join with Windows2000-Clients a Samba-PDC. When I join the samba-pdc with a WinNT4.0-Client it is no problem, first I create a machine-account for the machine: 1. in /etc/group exists the group: machines:x:515: 2. useradd -g machines -d /dev/null -c nickname -s /bin/false neuch205$ 3. pdbedit -a -m -u neuch205 In this way, it isn't a problem to join