search for: upgradeable

Your answer has nothing to do with the original question which is related to upgrade method and not condition for reinstalling without loosing data. Sometimes you need to keep your configuration and want to avoid reconfiguring everything, and reimaging your computer keeping /home is not an option. Of course having all user files on a separate filesystem helps when reimaging the OS (that what I do

Hi, is there a recommended way to upgrade Gluster cluster when upgrading to newer revision? I experienced filesystem corruption on several but not all VMs (KVM, FUSE) stored on Gluster during Gluster upgrade. After upgrading one of two nodes, I checked peer status and volume heal info, everything seemed fine so I upgraded second node and then two VMs remounted root as read-only and dmesg

Greetings, I've been trying to upgrade R packages on my Debian Etch (whose other upgrades I have been cheerfully going along with as they occur). When I did, just now: sudo apt-get dist-upgrade I got: Reading package lists... Done Building dependency tree... Done Calculating upgrade... Done The following packages have been kept back: r-base-core r-cran-boot r-cran-cluster

I'm pretty new to the task of upgrading CentOS or RedHat o.s.'s. I'm more familiar with upgrading Debian based o.s.'s. Here are my questions: 1) will yum ever upgrade the major version? I understand that there is no upgrade path from v5.x to v6.x, but is that always the case? e.g. was there an upgrade path from v4.x -> v5.x? If yum is capable of doing so, what are the

Hi all, I'm currently in process of upgrading a replicated cluster (1 x 4) from 3.6.3 to 3.10.5. The nodes run CentOS 6. However after upgrading the first node, the said node fails to connect to other peers (as seen via 'gluster peer status'), but somehow other non-upgraded peers can still see the upgraded peer as connected. Writes to the Gluster volume via local mounts of

I've read all docs on upgrades, from wiki to Louis notes, and i think i'm ready to upgrade. First step, move from stretch to jessie, and from 4.5 to 4.8, upgrade in place. But having a domain with 6 DCs, i'm a bit scared to upgrade all DC in one turn, and i'm think about something like: a) upgrade DC with FSMO roles, then wait 1-2 day to spot troubles b) then upgrade all DC in

Just so I am clear the upgrade process will be as follows: upgrade all clients to 4.0 rolling upgrade all servers to 4.0 (with GD1) kill all GD1 daemons on all servers and run upgrade script (new clients unable to connect at this point) start GD2 ( necessary or does the upgrade script do this?) I assume that once the cluster had been migrated to GD2 the glusterd startup script will be smart

I think this is obvious. but for some reason I''m not getting it. Models: Bicycles, Accessories Join Model: Upgrades The idea is that you can upgrade your bike by adding an accessory, and the upgrade price is often less than the accessory price would normally be. So the Upgrades table has id, bicycle_id, accessory_id, and price. class Bicycle has_many :upgrades has_many

Hi, so here is finally my upgrade report for my testsystem. I tried to upgrade to xen3 while xen2 (hypervisor, dom0 kernel + 1 domU) was running: 1) if xen2 (adams latest packages in this case) were installed and we would release our package as it is, we would generate the following enviorment: # apt-get upgrade -u Reading package lists... Done Building dependency tree... Done The following

I upgraded from 3.8.12 to 3.8.13 without issues. Two replicated volumes with online update, upgraded clients first and followed by servers upgrade, "stop glusterd, pkill gluster*, update gluster*, start glusterd, monitor healing process and logs, after completion proceed to the other node" check gluster logs for more information. -- Respectfully Mahdi A. Mahdi

Please forgive me if I missed something, but I've searched all over in hopes of finding something documented on a procedure to upgrade a Centos 3.4 system to the beta. I've got the DVD burned and am testing the process on VMWare. All I could figure out how to do was install over the existing partition without formatting, but this was quasi-disastrous so I 'reverted' my

Hi Diego, Just to clarify, so did you do an offline upgrade with an existing cluster (3.6.x => 3.10.x)? Thanks. On Fri, Aug 25, 2017 at 8:42 PM, Diego Remolina <dijuremo at gmail.com> wrote: > I was never able to go from 3.6.x to 3.7.x without downtime. Then > 3.7.x did not work well for me, so I stuck with 3.6.x until recently. > I went from 3.6.x to 3.10.x but downtime was

On Fri, Nov 3, 2017 at 8:50 PM, Alastair Neil <ajneil.tech at gmail.com> wrote: > Just so I am clear the upgrade process will be as follows: > > upgrade all clients to 4.0 > > rolling upgrade all servers to 4.0 (with GD1) > > kill all GD1 daemons on all servers and run upgrade script (new clients > unable to connect at this point) > > start GD2 ( necessary or

> -----Oorspronkelijk bericht----- > Van: samba [mailto:samba-bounces at lists.samba.org] Namens > Stefan G. Weichinger via samba > Verzonden: vrijdag 6 maart 2020 10:41 > Aan: samba at lists.samba.org > Onderwerp: Re: [Samba] DCs from 4.10.x to 4.11.x > > Am 06.03.20 um 10:11 schrieb L.P.H. van Belle via samba: > > After upgrade indexing is done as far i know.

greetings - I'm trying to upgrade a centos 3.6 box to version 4. I tried to do an upgrade using yum but that failed and now the Cd installer is not letting me upgrade either. Here's what I did: following the howto, I tried to do the upgrade using yum. I installed the GPG key and upgraded the centos-release and the centos-yumconf packages. When I tried to upgrade yum package I ran

On Thu, Nov 2, 2017 at 7:53 PM, Darrell Budic <budic at onholyground.com> wrote: > Will the various client packages (centos in my case) be able to > automatically handle the upgrade vs new install decision, or will we be > required to do something manually to determine that? We should be able to do this with CentOS (and other RPM based distros) which have well split glusterfs

We're fast approaching the time for Gluster-4.0. And we would like to set out the expected upgrade strategy and try to polish it to be as user friendly as possible. We're getting this out here now, because there was quite a bit of concern and confusion regarding the upgrades between 3.x and 4.0+. --- ## Background Gluster-4.0 will bring a newer management daemon, GlusterD-2.0 (GD2),

On Mon, Jul 10, 2017 at 10:33 PM, Mahdi Adnan <mahdi.adnan at outlook.com> wrote: > I upgraded from 3.8.12 to 3.8.13 without issues. > > Two replicated volumes with online update, upgraded clients first and > followed by servers upgrade, "stop glusterd, pkill gluster*, update > gluster*, start glusterd, monitor healing process and logs, after > completion proceed to

I made note the following in the 4.0.3 release notes about upgrades: o For more details concerning the ACL problem with delegation of privileges and deletion of accounts over LDAP interface (bugs #8909 and #9267) regarding upgrades from older 4.0.x versions, please see http://wiki.samba.org/index.php/Samba_AD_DC_HOWTO#Upgrading which will be filled with details once we have

https://bugs.freedesktop.org/show_bug.cgi?id=109558 Bug ID: 109558 Summary: Plasma locks up after splash screen Product: Mesa Version: 18.3 Hardware: x86-64 (AMD64) OS: Linux (All) Status: NEW Severity: major Priority: medium Component: Drivers/DRI/nouveau Assignee: nouveau at