That's very good advice. In my specific case, I am looking at lowlevel setup of the NSDs in a SSD storage pool with metadata stored elsewhere (on another SSD system). I am wondering if stuff like SSD pagepool size comes into play or if I just look at the segment size from the storage enclosure RAID controller.
It sounds like SSDs should be used just like HDDs: group them into RAID6 LUNs. Write endurance is good enough now that longevity is not a problem and there are plenty of IOPs to do parity work. Does this sound right? Anyone doing anything else? Brian On Sun, Jul 17, 2016 at 9:05 AM, Oesterlin, Robert < [email protected]> wrote: > Thinly provisioned (compressed) metadata volumes is unsupported according > to IBM. See the GPFS FAQ here, question 4.12: > > > > "Placing GPFS metadata on an NSD backed by a thinly provisioned volume is > dangerous and unsupported." > > > > http://www.ibm.com/support/knowledgecenter/en/STXKQY/gpfsclustersfaq.html > > > > Bob Oesterlin > Sr Storage Engineer, Nuance HPC Grid > 507-269-0413 > > > > > > *From: *<[email protected]> on behalf of Brian > Marshall <[email protected]> > *Reply-To: *gpfsug main discussion list <[email protected]> > *Date: *Saturday, July 16, 2016 at 9:56 PM > *To: *"[email protected]" <[email protected] > > > *Subject: *[EXTERNAL] [gpfsug-discuss] SSD LUN setup > > > > I have read about other products doing RAID1 with deduplication and > compression to take less than the 50% capacity hit. > > _______________________________________________ > gpfsug-discuss mailing list > gpfsug-discuss at spectrumscale.org > http://gpfsug.org/mailman/listinfo/gpfsug-discuss > >
_______________________________________________ gpfsug-discuss mailing list gpfsug-discuss at spectrumscale.org http://gpfsug.org/mailman/listinfo/gpfsug-discuss
