weird updatedb locate problem and DRVFS

[0wwafa]

I have these mounts:

C:\ on /mnt/c type drvfs (rw,noatime,uid=1000,gid=1000,case=off)
D:\ on /mnt/d type drvfs (rw,noatime,uid=1000,gid=1000,case=off)
F:\ on /mnt/f type drvfs (rw,noatime,uid=1000,gid=1000,case=off)
G:\ on /mnt/g type drvfs (rw,noatime,uid=1000,gid=1000,case=off)
H:\ on /mnt/h type drvfs (rw,noatime,uid=1000,gid=1000,case=off)
I:\ on /mnt/i type drvfs (rw,noatime,uid=1000,gid=1000,case=off)
J:\ on /mnt/j type drvfs (rw,noatime,uid=1000,gid=1000,case=off)
K:\ on /mnt/k type drvfs (rw,noatime,uid=1000,gid=1000,case=off)

For some unknow reason, all drives are indexed except drive "j".
(there is no rule to not index J... I even tried removing everything from /etc/updatedb.conf.

Drive J is EXFAT formatted Western Digital MY Book USB drive (14 TB).
It works correctly in windows, and in WSL1 I can access it, read and write to it.

It must have something to do with DRVFS because another weird thing happens:
if I do: sudo touch /mnt/* all dates of the mountpoints change but I get an error at J:

$ sudo touch /mnt/*
touch: setting times of '/mnt/j': Invalid argument

this is crazy weird, because /mnt/j is a mountpoint. if I unmount the drive (sudo umount /mnt/j) then I can "touch /mnt/j" but as I mount it I get that error and only on J.

I hope this helps you understanding what is going on.

[github-actions]

Logs are required for review from WSL team

If this a feature request, please reply with '/feature'. If this is a question, reply with '/question'.
Otherwise please attach logs by following the instructions below, your issue will not be reviewed unless they are added. These logs will help us understand what is going on in your machine.

How to collect WSL logs

Download and execute collect-wsl-logs.ps1 in an administrative powershell prompt:

Invoke-WebRequest -UseBasicParsing "https://raw.githubusercontent.com/microsoft/WSL/master/diagnostics/collect-wsl-logs.ps1" -OutFile collect-wsl-logs.ps1
Set-ExecutionPolicy Bypass -Scope Process -Force
.\collect-wsl-logs.ps1

The script will output the path of the log file once done.

If this is a networking issue, please use collect-networking-logs.ps1, following the instructions here

Once completed please upload the output files to this Github issue.

Click here for more info on logging
If you choose to email these logs instead of attaching to the bug, please send them to wsl-gh-logs@microsoft.com with the number of the github issue in the subject, and in the message a link to your comment in the github issue and reply with '/emailed-logs'.

[0wwafa]

@bterlson @kant @gaia @abergs

I don't think the extensive logs you are asking will help you in this.