Hi folks
on Workstations version REFS file system working without having to use storage spaces etc.
Note though ==> BOOT disk can't use it.
Will test how this works compared to NTFS.
anyway format REFS is working -- should be mega good for those with RAID systems too.
cheers
jimbo
What distros are you trying. Just to test things try installing the latest build of Ubuntu 19.10 and install the Workstation bundle and download 5.3rc3 (or on Sunday probably rc4) and then run the Github patch. Should work without a problem.
Hi there
will try UBUNTU later -- was trying FEDORA 30 as it's nearest to CENTOS / REDHAT so I know all the commands etc .
BTW still 2 probs with file systems in this W10 release
1) REFS -- had to abandon it as Linux can't access system in WRITE Mode so no good if you want to say recover a backup or file (or set of files) from a Linux type NAS server.
2) STILL that bonkers 266 path / file name limit with Windows explorer etc . While you can set registry or Group policy editor to allow long file names there doesn't seem to be any software around that displays these properly.
I think all these things including EXPLORER ++ , COMMANDER etc must use the standard API like File explorer so you just see long file names truncated into the old DOS 8.3 display.
Anybody found a File explorer "Clone" or Windows GUI program that displays LONG file names properly.
Command line copy from Linux is fine as is some versions of ROBOCOPY - but then you get the problem when you want to display the files -- what software !!!!! does one use.
I'm going to see if I can find some sort of EXCEL VBA macro which might "sort of work" by traversing directories and inserting names into the worksheet -- gives me something to do today instead of "being dragged to the shops" !
Meanwhile does anybody have a "File explorer" type of program ON WINDOWS that can display long file names whether these files are on a NAS or on Windows itself.
Cheers
jimbo
Had some problems, reverted back to previous build!
Let's give it another go!
You have a lot more faith in the vast majority of people actually using Windows IP builds than the numbers suggest.
Sadly, this might be the best option M$ has, if they would revert to it it would likely solve a lot of the issues they have with the new way WU is working.
If it wasn't for the reports that even fresh new installs are not taking the updates correctly, I'd start pointing to clean installs (relatively recent ones at that) versus installs that have been undergoing the update process for a while (since, like, perhaps before the infamous 18h2 build was released).
Sadly, we don't have access to the metrics from M$ side, so we don't really know what is going on or why it is going on - unless we peruse the Feedback Hub. And that is sketchy on info, a lot of times, not many actually provide full details (including troubleshooting steps, diagnostic reports, etc.) in the reports there.
A lot of work in what I'm about to suggest, but have you tried making a full system image, then clean installing and updating all the hardware drivers, and seeing if it takes with limited apps installed? You can always restore the image later on so you don't actually lose any info, but it would easily rule out if any of your hardware might be causing the issue.
With software, it gets a lot harder to trace - because you not only have to track what you have installed now, but what you might have installed in the past and removed, only for any given software to leave crumbs in the registry or other places (ProgramData, etc.) in order to really troubleshoot - but the hardware side could probably be tested in a single day, of course allowing for having the resources to make said backup, before cleanly installing....
GL!
In order to give ReFS a fair test I'd need to break my current (and long standing) Linux software RAID device and I'm not really in a fired up mode to do that if the file system is not writable yet. I assume they are working on it. I was using Linux when ntfs-3g was still in development - an interesting but frustrating experience. XFS is doing a great job.
This "No network access" thing is getting complicated!
Today Windows decided to sign off from my network and now I can't sign back in, it says
wrong credential (or something like that).
I removed credential from Credentials Manager and created a new one but, the problem still exist, it won't let me in.
There are a lot of things to consider here in a situation like this. First and foremost, it would be wise to restore your system with a recent image taken when things were working fine. If not, try the steps in this article:This "No network access" thing is getting complicated!
Today Windows decided to sign off from my network and now I can't sign back in, it says
wrong credential (or something like that).
I removed credential from Credentials Manager and created a new one but, the problem still exist, it won't let me in.
Fix Unidentified Network and No Network Access in Windows 7/8/10:
Fix Unidentified Network and No Network Access in Windows 7/8/10
[Sigh] Many problems!
Microsoft, Microsoft, Microsoft, tsk, tsk, tsk! Why is this so hard!?!?!?
This isn't fun anymore!
You are telling me!. I have already rolled back three times to 1809 from 1903 due to many bugs. And I plan to stay there (1809) at least until 19H2 aka Service Pack (CU 19H2).
Welcome to the club!. BTW, you are the one who gave me the best laugh in this forum. I like the way you manifest your frustrations sometimes. LOL
Quote
