[Samba] Help with archive bit request

[Noel Kelly]

John,

Did you ever get an answer to this ?  I think we are experiencing something
similar although the problem seems to be only with files we have bought over
from our Novell shares.  We are running RH6.2 (2.2.20 kernel with ACLs) and
Samba 2.2.3a.

The backup software (Novanet 8 Alliance SP5A running on NT) backs up
everything up fine on full (of course) but using differential it simply does
not recognise the archive bit.

The reason I am a little confused is that new files created on the Samba
share are backed up correctly using differential and in the Novanet software
these new files do have a distinct 'A' attribute under the file listings.
This does not seem to correspond to the owner's execute bit - if I toggle it
on and off on the Samba share there is no change from Novanet.  There must
be another flag attached to these files which I cannot see inside
Samba/Linux.

Is your backup software (?) having problems with all files or does it work
with ones created on the Samba share ?

I have emailed Novanet Support on this and hopefully they can give me some
insight as to what is going on.  I'll post their reply if it might help you
out.

Noel

-----Original Message-----
From: Gilbert, John [mailto:jgilbert at eosbiotech.com]
Sent: 19 February 2002 23:11
To: 'samba at lists.samba.org'
Subject: [Samba] Help with archive bit request


Hello,
What would be the best way to get an archive bit issue resolved. I've
already posted twice on this list, and issued a bug report, but without
any feedback what-so-ever. I'm wondering if there is some other way to
resolve
this issue. I've run across at least five other people reporting similar
problems
with samba and how it relates to NT space backups without any acceptable
answers. I'm including a few examples to back me up. See my previous posts
for details on how to replicate the problem.

http://samba.cadcamlab.org/lists/samba-ntdom/Jun2000/00137.html
	note: using smbclient and setmode does not fix backup issues,
	the backup software needs to change the archive bit itself.

http://samba.cadcamlab.org/listproc/samba/September1999/0000.html
	note: this looks like the exact same problem I'm seeing with
	2.2.3a

http://lists.samba.org/pipermail/samba/1999-April/041097.html
	This is a different but somewhat related problem that I have seen,
it
	can be fixed by creating a c$ share for backup-exec to try to use. I
	also hit this problem before the archive bit issue but the samba
	logs had enough information to figure it out.

Thanks in advance for any help resolving this.
John Gilbert
jgilbert at eosbiotech.com

-- 
To unsubscribe from this list go to the following URL and read the
instructions:  http://lists.samba.org/mailman/listinfo/samba