Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

WSL2 corrupting Git repositories and shell history

github.com

Post reply on HN
Print view View original

391–400 of 423 posts

Re: WSL2 corrupting Git repositories and shell history

#391

Post by jrockway »

AshamedCaptain wrote: post #385
smileybarry wrote: post #169

Earlier quoted context omitted.

Virtualization-based security -- a lighter mode of Hyper-V sans real VMs -- is enabled by default on new installs on recent-enough hardware: https://techcommunity.microsoft.com/t5/virtualization/virtua...

The link you posted only contains one device and it happens to be an ARM device. Seeing the impact it still has on battery life at least on x86, I really doubt they have enabled it by default. It was not enabled by default on x86 in 2020 at least.

Do you have a reference to the increased power consumption that running a hypervisor causes? This thread is the first I've heard about it, and I would like to learn more.

Re: WSL2 corrupting Git repositories and shell history

#393

Post by aksss »

lmz wrote: post #321
gavinray wrote: post #261

Earlier quoted context omitted.

Oh you need to fucking disable Window's Defender though, or add exclusions for your Linux distro/WSL2 folder, because when installing "node_modules" it will attempt to do realtime scans for threat-protection which absolutely cripples the speed. https://www.cicoria.com/improving-windows-subsystem-for-linu... https://www.reddit.com/r/bashonubuntuonwindows/comments/eok7... "I noticed a significant performance difference…

Surely this is only a problem if your files live in the Windows filesystem (i.e. inside /mnt/$drive on WSL2)? I can't imagine Windows Defender scanning inside a disk image (/home on WSL2).

I was wondering about the same thing.

Re: WSL2 corrupting Git repositories and shell history

#394

Post by aae42 »

noisem4ker wrote: post #283
dehrmann wrote: post #232

Earlier quoted context omitted.

After upgrading to WSL2, I started having issues with a Virtualbox VM. Turns out it didn't play nicely with HyperV. I went back to WSL1.

Newer VirtualBox releases can run virtual machines on top of Hyper-V as a virtualization engine. It is slower than VirtualBox' own engine, but overall it is still a better experience than Hyper-V Manager.

disagree, it's unusably slow... i had to move to hyper-v vagrant driver as vbox, while it would boot the VM, was so slow it defeated any purpose on speeding up development

Re: WSL2 corrupting Git repositories and shell history

#395

Post by aksss »

waheoo wrote: post #312
madeofpalk wrote: post #241

Earlier quoted context omitted.

Opposite anecdata - I got a gaming PC and i migrated all my development to it and WSL(2) has been a godsend. VS Code has a "WSL Remote" mode that works really well (where a vscode server runs in Linux and the windows GUI access it "remotely"). I even use the Windows Github app for the occasional GUI-assisted commit, and apart from being slow its fine. I've had only two problems with this set up: - Occasionally VS Cod…

I don't really know if you can call running a remote vs code setup on localhost as opposite anecdata. Isn't that just more of the same bullshit hoop jumping? Everytime I hear about how great someone's wsl setup is I roll my eyes because it inevitably involves some rediculously convoluted wrangling to the nth level for something that is relatively basic on native Linux. And these people rarely have an excuse for why t…

>> convoluted wrangling

With good humor, his describes my experience with Linux distros since I first started using them. Doing just about anything seems to require some convoluted wrangling. :)

Re: WSL2 corrupting Git repositories and shell history

#396

Post by cmurf »

Someone wrote: post #297
cmurf wrote: post #273

Earlier quoted context omitted.

There's no enough information to know if all the reported problems are the result of the same defect. But in: https://github.com/microsoft/WSL/issues/5895 The first instance of a problem is: [ 1.956835] JBD2: Invalid checksum recovering block 97441 in log And that's corruption that leads to log replay failing, i.e. rejecting it because honoring the replay in the face of checksum errors could make things much worse. S…

Thanks. That definitely is file system corruption. And that is very scary, as (assuming you have backups, which you should) losing files you’re working on is not the biggest problem you can have. That will lose you a few days at most. Silent corruption of parts of the disk that you rarely access but still want to keep is scarier (you might have rotating backups for months or years and still eventually lose data)

So long as the file system is fixed, it should be straightforward to fix the git repository. I'm no git expert but maybe 'git repair' can deal with it; and if not then 'rm -rf' and 'git clone'.

To avoid silent corruption requires full metadata and data checksumming, ala Btrfs or ZFS. In those cases, not only is corruption unambiguously detected, but it's not allowed to propagate.

Re: WSL2 corrupting Git repositories and shell history

#397

Post by aksss »

dlgeek wrote: post #163
chrisandchris wrote: post #139

Earlier quoted context omitted.

The web version does work until you need to sign into more than 2 accounts per day (1 in regular, 1 in private). If you need more than 2 accounts, it does not work anymore. Edit: it does work, but it will sign you out from all M365 services which requires a lot of logins for nothing.

Firefox container tabs are great for this sort of thing.

FF containers are great. Edge profiles do basically the same thing as well.

Re: WSL2 corrupting Git repositories and shell history

#398

Post by freeone3000 »

AshamedCaptain wrote: post #384
freeone3000 wrote: post #181

Earlier quoted context omitted.

WSL VMs are gen2 (fully paravirtual) hyper-v VMs, so use dynamic memory allocation. VirtualBox, even with Hyper-V as its engine, doesn't do this. I don't think any standalone Linux distros offer a standalone Hyper-V paravirtual image that is not a WSL2 image.

You don't need paravirtualization to do dynamic memory allocation -- all VMs do this.

No. Gen1 images use a fixed allocation pool instead of an oversubscription model. You need a gen2 image with a cooperative memory allocator on the guest in order for this to work properly.

Re: WSL2 corrupting Git repositories and shell history

#399

Post by wila »

nikanj wrote: post #376
wila wrote: post #223

Earlier quoted context omitted.

You can still use remote desktop for accessing remote VMs. You would be missing the remote power operations. FWIW, I am working on a product called Vimarun [0] that is aimed to replace most of that missing functionality over time. No remote power operations yet, but that will come. [0] https://vimarun.com

I'd also be missing the ability to plug in USB devices, which is very central to the work I do. RDP has some device passover support, but it's not even close to being able to replace vmware's USB support.

You are talking about redirecting USB via workstation as well? eg. connecting USB devices remotely to your VM? (asking as normal USB pass-through doesn't work for a shared VM, see [0])

I hadn't even considered that. Connecting USB devices remotely works well with vSphere, but never tried that with Workstation. They are going to completely removing the hostd engine from VMware Workstation. That would indeed also include that part and it is most likely not easy to get that working without hostd.

[0] http://kb.vmware.com/kb/2005585

Re: WSL2 corrupting Git repositories and shell history

#400

Post by Zardoz84 »

thethimble wrote: post #119
larrik wrote: post #104

Earlier quoted context omitted.

The web version of Outlook has come a long way, and in my opinion has become the superior product (for my use cases, at least).

You’re also missing Adobe products as well as most games. Using Linux without a reboot is an incredible convenience. Glossing over the value of proprietary software that only runs on Windows is narrow minded.

few games, not most games.
Post reply on HN