From: Piotr R. K. <pio...@mo...> - 2016-06-09 11:19:33
|
Dear MooseFS Users, after some notifications from Users about incompatibility of 3.0.x Mounts with 2.0.x Master Servers, we decided to rollback default "stable" symlink in our repository structure to 2.0.89. It doesn't mean, that MooseFS 3.0.77 is not stable! We did it only to prevent compatibility issues of 3.0.x Mounts with 2.0.x Masters in Users' MooseFS instances. We still recommend and encourage you to upgrade to 3.0.77. It can be done by typing explicite "3.0.75" instead of "stable" in repo URL (as I mentioned in my previous mail in reply to Steven's mail - attaching in quote). Tomorrow we are going to propose a better repository URLs structure. Please watch the mailing list and our website <https://moosefs.com/download.html> tomorrow. Best regards, Peter -- <https://moosefs.com/> Piotr Robert Konopelko MooseFS Technical Support Engineer e-mail : pio...@mo... <mailto:pio...@mo...> www : https://moosefs.com <https://moosefs.com/> <https://twitter.com/MooseFS> <https://www.facebook.com/moosefs> <https://www.linkedin.com/company/moosefs> <https://github.com/moosefs> This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received it by mistake, please let us know by e-mail reply and delete it from your system; you may not copy this message or disclose its contents to anyone. Finally, the recipient should check this email and any attachments for the presence of viruses. Core Technology accepts no liability for any damage caused by any virus transmitted by this email. > On 08 Jun 2016, at 6:14 PM, Piotr Robert Konopelko <pio...@mo...> wrote: > > Dear Steven, > > thank you very much for your remark. I'd like to let you (and the rest of MooseFS-Users) know, that it is possible to "control" the version of MooseFS on moosefs.list repo sources file. It's described on MooseFS Download page <https://moosefs.com/download.html>. Let me quote some essentials: > > There is also a possibility to use version number instead of "branch" if you want to decide exactly which version of MooseFS you want to upgrade to (e.g. 3.0.75-1): > > http://ppa.moosefs.com/3.0.75/[rest <http://ppa.moosefs.com/3.0.75/[rest> of url] > If you want to use this option, please remember you need to manually change version number on each server to newer one before doing an upgrade. > > > So it is possible to set up your MooseFS repository in a "controlled way". In such case, just put in /etc/apt/sources.list.d/moosefs.list (or equivalent in other OS) the following entry: > > deb http://ppa.moosefs.com/ <http://ppa.moosefs.com/>2.0.89/apt/ubuntu/trusty trusty main > > Then, when your upgrade is planned, before starting it, just change it to: > > deb http://ppa.moosefs.com/ <http://ppa.moosefs.com/>3.0.77/apt/ubuntu/trusty trusty main > > > This is a very good way to control MooseFS upgrades, since e.g. MooseFS Master Server upgrade usually has to be planned in production environments. The only con of this way is that you have to check manually if there's a newer version of MooseFS available. > > > Best regards, > > -- > > <Mail Attachment.png> <https://moosefs.com/> > > Piotr Robert Konopelko > MooseFS Technical Support Engineer > e-mail : pio...@mo... <mailto:pio...@mo...> > www : https://moosefs.com <https://moosefs.com/> > > <Mail Attachment.png> <https://twitter.com/MooseFS><Mail Attachment.png> <https://www.facebook.com/moosefs><Mail Attachment.png> <https://www.linkedin.com/company/moosefs><Mail Attachment.png> <https://github.com/moosefs> > This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received it by mistake, please let us know by e-mail reply and delete it from your system; you may not copy this message or disclose its contents to anyone. Finally, the recipient should check this email and any attachments for the presence of viruses. Core Technology accepts no liability for any damage caused by any virus transmitted by this email. > > >> On 08 Jun 2016, at 4:24 PM, Wilson, Steven M <st...@pu... <mailto:st...@pu...>> wrote: >> >> That's great news... thanks! >> >> One warning to other users: Now that v. 3.0.x is the stable version, any package upgrade you perform will automatically pull in this version. I was reminded of this today when I had to take down one of my MooseFS master servers to replace its UPS. Since I was rebooting the master server, I decided to perform a full package upgrade on it (Ubuntu: apt-get dist-upgrade). That, of course, upgraded all MooseFS components to 3.0.77 from 2.0.89. But I have numerous MooseFS master servers still running 2.0.89 and the new mfsmount won't mount these older (2.0.x) MooseFS file systems. I will probably mark as held the moosefs-client package on all my workstations until I have upgraded all MooseFS master servers to 3.0.x. I hope this helps prevent an unexpected surprise to some other user! >> >> Best regards, >> Steve |