gpfsug main discussion list <gpfsug-discuss@spectrumscale.org>
Date: 10/13/2016 06:46 AM
Subject: Re: [gpfsug-discuss] Hardware refresh -
Sent by:gpfsug-discuss-boun...@spectrumscale.org
Please note - though one of the supported use case of AFM is such
migration scen
,
migrate data from an old FS to a new FS
then delete nodes and disks that are no longer needed...
From: Stephen Ulmer <ul...@ulmer.org>
To: gpfsug main discussion list <gpfsug-discuss@spectrumscale.org>
Date: 10/11/2016 09:30 PM
Subject: Re: [gpfsug-discuss] Hardware
11, 2016 at 2:58 PM
> To: gpfsug main discussion list <gpfsug-discuss@spectrumscale.org
> <mailto:gpfsug-discuss@spectrumscale.org>>
> Subject: Re: [gpfsug-discuss] Hardware refresh
>
> New FS? Yes there are some good reasons.
> New cluster? I did not see a compelling ar
scale.org>
Date: Tuesday, October 11, 2016 at 2:58 PM
To: gpfsug main discussion list <gpfsug-discuss@spectrumscale.org>
Subject: Re: [gpfsug-discuss] Hardware refresh
New FS? Yes there are some good reasons.
New cluster? I did not see a compelling argument either way.
From:"mar
cale.org>,
Date: 10/10/2016 04:45 PM
Subject: Re: [gpfsug-discuss] Hardware refresh
Sent by: gpfsug-discuss-boun...@spectrumscale.org
Can one format NSDv2 NSDs and put them in a filesystem with NSDv1 NSD's?
-Aaron
O
Aaron
From: Aaron Knister <aaron.s.knis...@nasa.gov>
To: <gpfsug-discuss@spectrumscale.org>,
Date: 10/10/2016 04:45 PM
Subject: Re: [gpfsug-discuss] Hardware refresh
Sent by: gpfsug-discuss-boun...@spectrumscale.org
Can one format NSDv2 NSDs and put the
boun...@spectrumscale.org> on behalf of Yuri L
Volobuev <volob...@us.ibm.com>
Reply-To: gpfsug main discussion list <gpfsug-discuss@spectrumscale.org>
Date: Tuesday, October 11, 2016 at 12:22 PM
To: gpfsug main discussion list <gpfsug-discuss@spectrumscale.org>
Subject: Re: [g
n discussion list <gpfsug-discuss@spectrumscale.org>
Date: Tuesday, October 11, 2016 at 12:22 PM
To: gpfsug main discussion list <gpfsug-discuss@spectrumscale.org>
Subject: Re: [gpfsug-discuss] Hardware refresh
This depends on the committed cluster version level (minReleaseLevel) and fi
