worthy lodge
https://kb.netapp.com/on-prem/ontap/OHW/OHW-KBs/What_impact_if_we_Modify_the_Vserver_to_use_64_bit_NFSv3_and_NFSv4_x_identifiers -- I'm creating a new Flexgroup on an existing vserver and it currently is not set to 64-bit NFS IDs.
Best practice is to have 64-bit IDs to support the file counts you could have with Flexgroups.
But... is this file ID count scoped per-volume or are FSIDs shared across the whole vserver? I'd think per-volume because the FSIDs are per-filesystem.
I'm in a sticky situation where we need this setup "yesterday" but it really should be in this existing vserver.
And I don't want to reconnect all... 524 connections currently on the vserver. We'll have scheduled downtime in a couple weeks where we can do it, but not right now.
gray galleon
If you enable 64bit identifiers, you must remount all NFS clients. Otherwise you will get "stale file handle" errors. No way around this I'm afraid.
As for whether it can wait a few weeks or not, that highly depends on the number of files in your FlexGroup. If you're nowhere close to 2 billion it will probably not be a problem until then
worthy lodge
The latter is what I was thinking. No, AFAIK it won't be anywhere near that many
So I think I can wait for maintenance when those existing clients will be down/can-be-restarted anyway
Thanks, @gray galleon !
I went ahead and made the flexgroup for now. We can afford to roll the dice a little that the user won't come up with >2B files
peak narwhal
not sure. This setting is on by default for NFSv4 and off by default for NFS3 (for backwards compatibility...older clients dont know how to handle 64-bit file handles).
Whenever I create a vserver, I always go to advanced mode and specify "-v3-64 enable" to enable the feature