Hai Patrick,> -----Oorspronkelijk bericht----- > Van: samba [mailto:samba-bounces at lists.samba.org] Namens > Patrick Goetz via samba > Verzonden: woensdag 6 oktober 2021 14:13 > Aan: samba at lists.samba.org > Onderwerp: Re: [Samba] Samba 4.14 upgrade schema to 2012_R2 error > > Hi Louis - > > On 10/6/21 06:37, L. van Belle via samba wrote: > > Hai, > > > > Thanks for reporting this people. > > I'll add the patch package to the samba in the next > 4.14/4.15 packages > > > > On below, i have the same in the 4.14 packages and if i > recall correctly, > > Its not available atm in 4.14.x > > > > I "thought" its ready in 4.15 but i havent tested/checked it yet. > > > > And a small reminder for the people that already start > upgrading there > > servers.. > > I use this for a reason, most know my policy with the > packages and version > > numbering. > > > > .0 is a test server. > > .1 is preffered an auth only server. > > .2 is the first member server with shares/printing. > > .3 is the first AD-DC. > > > > Follow this path and your pretty safe with upgrades and > things "not" working > > suddenly. > > Only if a .0 tests are ok, then i repeat is like its a .1 > release and so on. > > > > I can tell you folks, that, in that last 4 years, > > only 2 or 1 X.XX.0 release made it to DC upgrade. > > > > It sounds like you are telling us to NOT use 4.15.0 for a DC > installation? > > Since 4.14 was just patched to 4.14.8, this might be a safer > choice all around. Does anyone know what features one will > be missing out on by sticking to 4.14.x for now?Changelog ;-) that tell's what you miss. ;-) And no, what im saying is to test before you roll out a new major release to "any" production server. I only got to testing on a test server atm, because im having back problems, an old injury is bugging me because of that so im less behind pc. What i showed is the general path i follow, i use it for years now and i concider that safe, but im not you, My network is different, so setup a way that fits your environment. Im eager to goto 4.15 also because it has things i need, just.. The bigger the changes compaired to previous version, the better you should test. Thats all i can say. +, 4.14.8 is building currenlty, i just uploaded Ubuntu Focal Fossa. Buster 4.14.8 will be online later today, thats currently building the last arch. Bullseye 4.14.8 will be online tomorrow, So far, Greetz, Louis
On 10/6/21 07:49, L. van Belle via samba wrote:> Hai Patrick, > >> -----Oorspronkelijk bericht----- >> Van: samba [mailto:samba-bounces at lists.samba.org] Namens >> Patrick Goetz via samba >> Verzonden: woensdag 6 oktober 2021 14:13 >> Aan: samba at lists.samba.org >> Onderwerp: Re: [Samba] Samba 4.14 upgrade schema to 2012_R2 error >> >> Hi Louis - >> >> On 10/6/21 06:37, L. van Belle via samba wrote: >>> Hai, >>> >>> Thanks for reporting this people. >>> I'll add the patch package to the samba in the next >> 4.14/4.15 packages >>> >>> On below, i have the same in the 4.14 packages and if i >> recall correctly, >>> Its not available atm in 4.14.x >>> >>> I "thought" its ready in 4.15 but i havent tested/checked it yet. >>> >>> And a small reminder for the people that already start >> upgrading there >>> servers.. >>> I use this for a reason, most know my policy with the >> packages and version >>> numbering. >>> >>> .0 is a test server. >>> .1 is preffered an auth only server. >>> .2 is the first member server with shares/printing. >>> .3 is the first AD-DC. >>> >>> Follow this path and your pretty safe with upgrades and >> things "not" working >>> suddenly. >>> Only if a .0 tests are ok, then i repeat is like its a .1 >> release and so on. >>> >>> I can tell you folks, that, in that last 4 years, >>> only 2 or 1 X.XX.0 release made it to DC upgrade. >>> >> >> It sounds like you are telling us to NOT use 4.15.0 for a DC >> installation? >> >> Since 4.14 was just patched to 4.14.8, this might be a safer >> choice all around. Does anyone know what features one will >> be missing out on by sticking to 4.14.x for now? > > Changelog ;-) that tell's what you miss. ;-) > > And no, what im saying is to test before you roll out a new > major release to "any" production server. I only got to testing > on a test server atm, because im having back problems, > an old injury is bugging me because of that so im less behind pc. > > What i showed is the general path i follow, > i use it for years now and i concider that safe, but im not you, > My network is different, so setup a way that fits your environment. > > Im eager to goto 4.15 also because it has things i need, just.. > The bigger the changes compaired to previous version, the better > you should test. Thats all i can say. >I read through the change log for 4.15.0 and aside from the VFS updates, which are likely entirely opaque unless one looks at the source code, the main thing that popped out was this: "server multi channel support" is enabled by default. Whenever possible I always set up 802.3ad bonding on network ports, but I'm still trying to wrap my brain around how this can work without cooperation from the network stack. It looks like you have to assign different IP addresses to 2 or more NICs on the same network, but then why doesn't the routing software overrule which interface the SMB3 packets use? Color me confused.> +, 4.14.8 is building currenlty, i just uploaded Ubuntu Focal Fossa. > Buster 4.14.8 will be online later today, thats currently building the last > arch. > Bullseye 4.14.8 will be online tomorrow, > > > So far, > > Greetz, > > Louis > > > >
....> > > > Changelog ;-) that tell's what you miss. ;-) > > > > And no, what im saying is to test before you roll out a new > > major release to "any" production server. I only got to testing > > on a test server atm, because im having back problems, > > an old injury is bugging me because of that so im less behind pc. > > > > What i showed is the general path i follow, > > i use it for years now and i concider that safe, but im not you, > > My network is different, so setup a way that fits your environment. > > > > Im eager to goto 4.15 also because it has things i need, just.. > > The bigger the changes compaired to previous version, the better > > you should test. Thats all i can say. > > > > > I read through the change log for 4.15.0 and aside from the > VFS updates, > which are likely entirely opaque unless one looks at the source code, > the main thing that popped out was this: > > "server multi channel support" is enabled by default. > > Whenever possible I always set up 802.3ad bonding on network > ports, but > I'm still trying to wrap my brain around how this can work without > cooperation from the network stack. It looks like you have to assign > different IP addresses to 2 or more NICs on the same network, > but then > why doesn't the routing software overrule which interface the SMB3 > packets use? Color me confused. >Same here, but this one might help us.. ;-) https://docs.microsoft.com/en-us/archive/blogs/josebda/the-basics-of-smb-multichannel-a-feature-of-windows-server-2012-and-smb-3-0 And https://blog.chaospixel.com/linux/2016/09/samba-enable-smb-multichannel-support-on-linux.html But.. 17:00 here.. I'm off, i want my couch.. Greetz, Louis