search for: dosstream

Am 5/30/20 um 8:00 PM schrieb Martin Steiner / 3MF GmbH via samba: > I changed the configuration and raised the log level, in my opion samba tries to access the non existent double files. > Samba is now probably writing the data in a netatalk compliant way in the extended attributes of the file but is not reading it. > > new configuration: > > [Global] > min protocol = SMB2

...s creation of large extended attributes (at least on ZFS volumes). I've personally added ones of up to 3MB in size, but have never actually tested the limits. For the fun of it I decided to run the following command from the CLI in FreeBSD "cat <large file> | setextattr -i user 'DosStream.User.SecretStream:$DATA' test.txt" This had the effect of creating something that samba should recognize as an ADS that is arbitrarily large. If I run the following powershell command from a Windows client "Get-Item -Path .\test.txt -stream *", I do not see the ADS listed unless...

...tested the limits. oh, really? Does it these day support the POSIX file IO API on xattrs like Solaris does? It didn't the last time I checked. > For the fun of it I decided to run the following command from the CLI in > FreeBSD "cat <large file> | setextattr -i user > 'DosStream.User.SecretStream:$DATA' test.txt" This had the effect of > creating something that samba should recognize as an ADS that is > arbitrarily large. > > If I run the following powershell command from a Windows client "Get-Item > -Path .\test.txt -stream *", I do not...

On Tue, Aug 15, 2017 at 07:08:40AM -0500, Andrew Walker via samba wrote: > On Wed, Aug 9, 2017 at 7:37 AM, Ralph Böhme <slow at samba.org> wrote: > > > On Mon, Aug 07, 2017 at 08:26:22PM -0500, Andrew Walker via samba wrote: > > > It's also interesting to note that ReFS in windows has a 128KB limit on > > the > > > size of alternate data streams. >

It's also interesting to note that ReFS in windows has a 128KB limit on the size of alternate data streams. When you try to write an overly large stream, the ReFS-backed server replies with "NT_STATUS_FILE_SYSTEM_LIMITATION" (0xc0000427) rather than "access denied". The windows client handles this more gracefully than a simple access denied message. It allows users to skip

On Wed, Aug 9, 2017 at 7:37 AM, Ralph Böhme <slow at samba.org> wrote: > On Mon, Aug 07, 2017 at 08:26:22PM -0500, Andrew Walker via samba wrote: > > It's also interesting to note that ReFS in windows has a 128KB limit on > the > > size of alternate data streams. > > > > When you try to write an overly large stream, the ReFS-backed server > > replies

On Mon, Aug 07, 2017 at 08:26:22PM -0500, Andrew Walker via samba wrote: > It's also interesting to note that ReFS in windows has a 128KB limit on the > size of alternate data streams. > > When you try to write an overly large stream, the ReFS-backed server > replies with "NT_STATUS_FILE_SYSTEM_LIMITATION" (0xc0000427) rather than > "access denied". The

...there it?s showing the tag for about one second but it?s disappearing afterwards. The attr binary shows the following output (seems to be written again in the extended attributes, but finder can?t read it): attr -l rwar Attribute "DOSATTRIB" has a 32 byte value for rwar Attribute "DosStream.AFP_AfpInfo:$DATA" has a 61 byte value for rwar Attribute "DosStream.com.apple.metadata:_kMDItemUserTags:$DATA" has a 52 byte value for rwar attr -g 'DosStream.com.apple.metadata:_kMDItemUserTags:$DATA' rwar Attribute "DosStream.com.apple.metadata:_kMDItemUserTags:$DATA...

...e if the problem persists. Martin > Am 05.06.2020 um 13:44 schrieb Ralph Boehme <slow at samba.org>: > > Am 6/5/20 um 1:37 PM schrieb Martin Steiner / 3MF GmbH: >> as i can see from the log files it is reading 60 bytes from the extended attributes but not from any other than DosStream.AFP_AfpInfo. >> All of the .com.apple.* attributes, especially DosStream.com.apple.metadata:_kMDItemUserTags are missing when listing the directory. >> And again - it tries to access a dotbar file which cannot exist with these settings. > > sure it can exist, for an optional res...

> > If you feel like it, you could write a VFS module that adds better support > for > this on FreeBSD, but what is the use case? > I've noticed in online forums that occasionally home NAS users will for various reasons have streams_xattr enabled and receive 'access denied' errors when trying to write files with large alternate datastreams. These are typically on media

...ut one second but it?s disappearing afterwards. > > The attr binary shows the following output (seems to be written again in the extended attributes, > but finder can?t read it): > > attr -l rwar > Attribute "DOSATTRIB" has a 32 byte value for rwar > Attribute "DosStream.AFP_AfpInfo:$DATA" has a 61 byte value for rwar > Attribute "DosStream.com.apple.metadata:_kMDItemUserTags:$DATA" has a 52 byte value for rwar > > attr -g 'DosStream.com.apple.metadata:_kMDItemUserTags:$DATA' rwar > Attribute "DosStream.com.apple.metadata:_k...

as i can see from the log files it is reading 60 bytes from the extended attributes but not from any other than DosStream.AFP_AfpInfo. All of the .com.apple.* attributes, especially DosStream.com.apple.metadata:_kMDItemUserTags are missing when listing the directory. And again - it tries to access a dotbar file which cannot exist with these settings. BTW, accessing kMDItemFinderComment works without any issue - i ca...

...d attribute is wrong. % lsextattr user ICONandEA.txt ICONandEA.txt netatalk.Metadata com.apple.TextEncoding com.apple.metadata:kMDItemFinderComment "netatalk.Metadata" is incompatible to Netatalk. The first atom "org." is removed. source3/include/smb.h: /* Prefix for DosStreams in the vfs_streams_xattr module */ #define SAMBA_XATTR_DOSSTREAM_PREFIX “user.DosStream.” There is always "user.". vfs_streams_xattr seems to eliminate the first atom, in case of FreeBSD or Solaris. source3/modules/vfs_fruit.c: #if defined(HAVE_ATTROPEN) || defined(FREEBSD) #define AFP...

Am 6/5/20 um 1:37 PM schrieb Martin Steiner / 3MF GmbH: > as i can see from the log files it is reading 60 bytes from the extended attributes but not from any other than DosStream.AFP_AfpInfo. > All of the .com.apple.* attributes, especially DosStream.com.apple.metadata:_kMDItemUserTags are missing when listing the directory. > And again - it tries to access a dotbar file which cannot exist with these settings. sure it can exist, for an optional resource fork. >...

these lines were an option before but have already been marked as comments in my config. same behaviour as before, color tag shows for round about a second and disappears suddenly. Martin > Am 05.06.2020 um 09:23 schrieb Ralph Boehme via samba <samba at lists.samba.org>: > > Am 6/5/20 um 8:33 AM schrieb Martin Steiner / 3MF GmbH: >> Any more ideas? It?s not displaying

Hi list, we have migrated a single node Samba server from Ubuntu Trusty to a 3-node CTDB Cluster on Debian Bullseye with Sernet packages. Storage is CephFS. We are running Samba in Standalone Mode with LDAP Backend. Samba Version: sernet-samba 99:4.18.2-2debian11 I don't know if it is relevant here's how we have mounted CephFS on the samba nodes: (fstab):/samba /srv/samba ceph

...seen from the Mac ... me at mymac:/Volumes/xattr ls -ld@ untitled\ folder/ drwx------@ 1 thomi staff 16384 Aug 7 17:34 untitled folder// com.apple.FinderInfo 32 com.apple.metadata:_kMDItemUserTags 50 ... or directly on the samba server: root at ubuntu:/data/xattr# xattr -pl 'user.DosStream.com.apple.metadata_kMDItemUserTags:$DATA' untitled\ folder/ user.DosStream.com.apple.metadata_kMDItemUserTags:$DATA: 0000 62 70 6C 69 73 74 30 30 A1 01 55 52 65 64 0A 36 bplist00..URed.6 0010 08 0A 00 00 00 00 00 00 01 01 00 00 00 00 00 00 ................ 0020 00 02 00 00 00 00 0...

Hi all, We use the vfs_fruit module and lately we have experienced that random files copied with Finder are being grayed out. We think this is probably due to the extended attribute "user.DosStream.AFP_AfpInfo:$DATA" not being updated/removed after the file is copied. If we manually remove the xattr in question with the command setfattr -d 'user.DosStream.AFP_AfpInfo:$DATA', the file becomes 'available' to macOS users. All data in the file is ok, the problem is solely the...

...fruit:encoding = native streams_xattr:prefix = user. streams_xattr:store_stream_type = no ------------------------- https://www.samba.org/samba/docs/current/man-html/vfs_streams_xattr.8.html streams_xattr:prefix = STRING Name prefix used when storing an ADS in an xattr, defaults to user.DosStream.. Changing this will also expose ADS over the SMB extended attributes interface so the defaults are not suiteable? ------------------------- hell, what is the way to go switch all clients using samba without lose data like old fonts which have important data in the resource fork *without* create...

since "ea = samba" was only added to very recent netatalk versions and so don't apply to files with a history of many years what is the way to go get rid of netatalk these days? is there still no tool to read/write the existing netatalk appladouble extended attributes which are *not* compatible with samba and write them back in the new format? afp.conf: appledouble = ea ea = samba