16 Dec
2022
16 Dec
'22
2:43 p.m.
Hi Linus,
Last time I set it up it was on NT but I just checked
and I think it may still
be an option. looks like It's even supporting v4.1 in 2022 if I read this
right.
[ https://learn.microsoft.com/en-us/windows-server/storage/nfs/nfs-overview |
https://learn.microsoft.com/en-us/windows-server/storage/nfs/nfs-overview ]
As I recall and that's a real wildcard it doesn't matter what the server
filesystem is, if it has an NFS driver it's a network file system and all
translation, rights mappings etc. etc. is handled by the linux driver or
windows MMC plug-in so everybody sees it their way. Think you can even run like
2, 3 and 4 at the same time while migrating or waiting for vendor catch-up.
Interesting ... So NFSv4 is a drop-in replacement for DFS? That would be good news. The
DFS filesystem namespace aggregation works well, but I never got the replication working
well; "writes" would unpredictably fail and I think I had other problems but I
simply stopped using the replication feature and did daily backups instead. In my mind
there is a lot of room for improvement in DFS but it never occurred to me to look for a
replacement.
I don't know if DFS is the "freelancer" in my observation or the
"Off-line" files is, and it is not enough of a problem for me to undertake the
effort to run experiments to find out, although it sounds like I could drop NFSv4 into the
role I have for DFS and not be any worse off. Or I could go take a nap.
--
Chris.
V:916.799.9461
F:916.974.0428
A: Because we read from top to bottom, left to right.
Q: > Why should I start my reply below the quoted text?