Re: [gpfsug-discuss] gpfsug-discuss Digest, Vol 62, Issue 33

*drags out soapbox* Sorry in advance for the rant, this is one of my huge pet peeves :) There are some serious blockers for GNR adoption in my environment. It drives me up a wall that the only way to get end to end checksums in GPFS is with vendor hardware lock-in. I find it infuriating. Lustre

Re: [gpfsug-discuss] gpfsug-discuss Digest, Vol 62, Issue 33

>>For me it's the protection against bitrot and added protection against silent data corruption GNR has this functionality. Right now that is available through ESS though. Not yet as software only. Steve Duersch Spectrum Scale 845-433-7902 IBM Poughkeepsie, New York

Re: [gpfsug-discuss] Running multiple mmrestripefs in a singlecluster?

You can control the load of mmrestripefs (and all maintenance commands) on your system using mmchqos ... From: "Olaf Weiser" To: gpfsug main discussion list Date: 03/15/2017 04:04 PM Subject:Re: [gpfsug-discuss]

Re: [gpfsug-discuss] Running multiple mmrestripefs in a single cluster?

yes.. and please be carefully about the number of nodes , doing the job because of multiple PIT worker hammering against your data if you limit the restripe to 2 nodes  (-N ..)   of adjust the PITworker down to 8 or even 4  ... you can run multiple restripes.. without hurting the application

Re: [gpfsug-discuss] default inode size - remarks

You can set inode size to any one of 512, 1024, 2048 or 4096 when you mmcrfs. Try it on a test system. You want all the metadata of a file to fit into the inode. Also small files, and small directories, can be stored in their inodes. On a test file system you can examine how much of an inode

[gpfsug-discuss] Running multiple mmrestripefs in a single cluster?

I’m looking at migrating multiple file systems from one set of NSDs to another. Assuming I put aside any potential IO bottlenecks, has anyone tried running multiple “mmrestripefs” commands in a single cluster? Bob Oesterlin Sr Principal Storage Engineer, Nuance 507-269-0413

Re: [gpfsug-discuss] mmcrfs issue

Hi All, Since I started this thread I guess I should chime in, too … for us it was simply that we were testing a device that did not have hardware RAID controllers and we were wanting to implement something roughly equivalent to RAID 6 LUNs. Kevin > On Mar 14, 2017, at 5:16 PM, Aaron Knister

Re: [gpfsug-discuss] default inode size

Another thing to consider is how many disk block pointers you have room for in the inode, and when you'll need to add additional indirect blocks. Ref: http://files.gpfsug.org/presentations/2016/south-bank/ D2_P2_A_spectrum_scale_metadata_dark_V2a.pdf If I understand that presentation correctly..

Re: [gpfsug-discuss] default inode size

I'm not sure because I've not tried it but if you chose an inode size less than 4K does the FS still show as being 4K aligned? If it doesn't this could prevent you from expanding the metadata capacity of the FS in the future because in a non 4k aligned fs GPFS won't let you add 4K sector size

Re: [gpfsug-discuss] default inode size

> On Mar 15, 2017, at 8:37 AM, Lukas Hejtmanek wrote: > > On Wed, Mar 15, 2017 at 08:22:22AM -0400, Stephen Ulmer wrote: >> You need 4K nodes to store encryption keys. You can also put other useful >> things in there, like extended attributes and (possibly) the entire

Re: [gpfsug-discuss] default inode size

On Wed, Mar 15, 2017 at 01:12:44PM +, GORECKI, DIETER wrote: > One other thing to consider is the storage of data inside the inode itself > for very small files. GPFS has the ability to use the remaining [kilo]bytes > of the inode to store the data of the file whenever the file is small

Re: [gpfsug-discuss] default inode size

Hello, On Wed, Mar 15, 2017 at 01:09:07PM +, Luis Bolinches wrote: >My 2 cents. Before even thinking too much on that path I would check the >following >  >- What the is physical size on those SSD if they are already 4K you won't >"save" anything size of what? >- Do

Re: [gpfsug-discuss] default inode size

Hi   My 2 cents. Before even thinking too much on that path I would check the following   - What the is physical size on those SSD if they are already 4K you won't "save" anything - Do you use small (>3.5Kb) files? If so I would still keep 4K inodes - Check if 512 can hold NSDv2 format, from top

Re: [gpfsug-discuss] default inode size

On Wed, Mar 15, 2017 at 08:22:22AM -0400, Stephen Ulmer wrote: > You need 4K nodes to store encryption keys. You can also put other useful > things in there, like extended attributes and (possibly) the entire file. > > Are you worried about wasting space? well, I have 1PB of capacity for data

Re: [gpfsug-discuss] default inode size

You need 4K nodes to store encryption keys. You can also put other useful things in there, like extended attributes and (possibly) the entire file. Are you worried about wasting space? -- Stephen > On Mar 15, 2017, at 5:50 AM, Lukas Hejtmanek