So I have minReleaseLevel 4.1.1.0 Is that to old?
On 12/28/16 11:50 AM, Aaron Knister wrote: > Hey Matt, > > We ran into a similar thing and if I recall correctly a mmchconfig > --release=LATEST was required to get LROC working which, of course, > would boot your 3.5.0.7 client from the cluster. > > -Aaron > > On 12/28/16 11:44 AM, Matt Weil wrote: >> This is enabled on this node but mmdiag it does not seem to show it >> caching. Did I miss something? I do have one file system in the >> cluster that is running 3.5.0.7 wondering if that is causing this. >>> [root@ces1 ~]# mmdiag --lroc >>> >>> === mmdiag: lroc === >>> LROC Device(s): 'NULL' status Idle >>> Cache inodes 1 dirs 1 data 1 Config: maxFile 1073741824 stubFile >>> 1073741824 >>> Max capacity: 0 MB, currently in use: 0 MB >>> Statistics from: Tue Dec 27 11:21:14 2016 >>> >>> Total objects stored 0 (0 MB) recalled 0 (0 MB) >>> objects failed to store 0 failed to recall 0 failed to inval 0 >>> objects queried 0 (0 MB) not found 0 = 0.00 % >>> objects invalidated 0 (0 MB) >> >> _______________________________________________ >> 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