Upgrading from S4-alpha12

titantoppler at gmail.com titantoppler at gmail.com
Wed Mar 7 00:49:05 MST 2012

Hi Mathieu,

What exactly does this patch do?

This might be relevant - due to a poor design decision at the start, I'm
using the posix:eadb option in my smb.conf, which IIRC stores the ACLs in a
file. Does that change things materially?


On Wed, Mar 7, 2012 at 1:46 PM, Matthieu Patou <mat at samba.org> wrote:

> On 03/06/2012 10:13 AM, titantoppler at gmail.com wrote:
>> Hi list,
>> I'm attempting to upgrade from my (very old) installation of S4 alpha 12,
>> to the current build of S4.
>> After pulling down the latest source and compiling+installing, I'm doing
>> the 'upgradeprovision --full' step to upgrade the database.
>> However, I'm running out of space. Upon further investigation, I realised
>> that this step seemed to be copying the 'sysvol' folder to a
>> /usr/local/samba/private/**backupprovision(some-random-**letters). Since
>> my
>> users' data files are really huge, doing so fills out my hard disk really
>> quickly.
>> Why is this happening (meaning the need to copy the files) - I had thought
>> the provisioning step would be upgrading the database only, without
>> touching my files? Is there a way around that?
> Because upgradeprovision is also changing acl on the sysvol part as they
> used to be very broken.
> Try the attached patch and run with --db_backup_only, it should do just
> the backup of the DBs, If you have still issues try with --nontaclfix.
> Matthieu
> --
> Matthieu Patou
> Samba Team
> http://samba.org

More information about the samba-technical mailing list