Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Description of problem:
After enabling case-insensitive for virtiofs service, md5sum or notepad cmd still fail to open the file with uppercase/lowercase letter.
Version-Release number of selected component (if applicable):
qemu-kvm-7.2.0-8.el9.x86_64
kernel-5.14.0-252.el9.x86_64
edk2-ovmf-20221207gitfff6d81270b5-5.el9.noarch
virtio-win-prewhql-0.1-234
How reproducible:
100%
Steps to Reproduce:
1.start virtiofs daemon
# /usr/libexec/virtiofsd --shared-dir /home/test --socket-path /tmp/sock1 -d
2.boot up win2022 guest
-chardev socket,id=char_virtiofs_fs,path=/tmp/sock1 \
-device vhost-user-fs-pci,id=vufs_virtiofs_fs,chardev=char_virtiofs_fs,tag=myfs,queue-size=1024,bus=pcie-root-port-3,addr=0x0 \
3.start virtiofs service and enable case-insensitive
z:\>sc create VirtioFsSvc binpath=virtiofs.exe start=auto depend="WinFsp.Launcher/VirtioFsDrv" DisplayName="Virtio FS Service"
z:\>reg add HKLM\Software\VirtIO-FS /v CaseInsensitive /d 1 /t REG_DWORD
4. reboot guest
5. login guest and create a file on the shared dir, and create a file, try to get md5 checksum for the file.
M:\>type file.txt
hello
M:\>type FILE.txt
"hello"
M:\>md5sum file.txt
c4a246e402c50cd67617e59affd536b1 *file.txt
M:\>md5sum FILE.txt
No such file: FILE.txt
5. Try to repeat step 4 on the file on C: volume.
C:\>md5sum test.txt
6dd4566eb245627b49f3abb7e4502dd6 *test.txt
C:\>md5sum TEST.txt
6dd4566eb245627b49f3abb7e4502dd6 *test.txt
Actual results:
After step4, md5sum can't get the file with uppercase letter, it's sensitive to uppercase and lowercase letters.
Expected results:
For virtiofs volume,md5sum is insensitive with uppercase and lowercase letters as it does in C:
Additional info:
Notepad, type, dir, etc are insensitive with case letter.
Hi,
what kind of md5sum are you using? My md5sum is working in the case-insensitive way.
Z:\>md5sum --version
md5sum (GNU coreutils) 8.32
Z:\>cat file.txt
hello
Z:\>cat File.txt
hello
Z:\>md5sum file.txt
6dd4566eb245627b49f3abb7e4502dd6 *file.txt
Z:\>md5sum FILE.TXT
6dd4566eb245627b49f3abb7e4502dd6 *FILE.TXT
M:\>c:\"program files"\git\usr\bin\md5sum.exe --version
md5sum (GNU coreutils) 8.32
M:\>c:\"program files"\git\usr\bin\md5sum.exe TEST
5c9597f3c8245907ea71a89d9d39d08e *TEST
It works with the newer md5sum, so I will close this bug.
Btw, for the md5sum tool for windows, I searched online for times, but I'm only able to get it from the git bash.
Hi Viktor, do you have a better way to get it? Thanks in advance.
Comment 4Yvugenfi@redhat.com
2023-02-27 08:09:59 UTC
Keeping open in order to investigate root cause with the old version in order not to skip the bug on our side.
(In reply to Viktor Prutyanov from comment #6)
> Hi Xiaoling,
>
> What was the old version of md5sum that you used? How to obtain it?
The version is 1.22, it's an older one and I don't know how to obtain it, it existed in our test tool for a long time.
C:\>md5sum.exe --version
md5sum (PCP patchlevel 2) (GNU textutils) 1.22
Comment 10Viktor Prutyanov
2023-03-16 13:56:25 UTC
Yan, Viktor, do you plan to have this bug fixed in 9.2.Z? And could you help update the 'Internal Target Release' field?
Thanks.
Comment 13Yvugenfi@redhat.com
2023-05-04 06:40:28 UTC
(In reply to xiagao from comment #12)
> Yan, Viktor, do you plan to have this bug fixed in 9.2.Z? And could you help
> update the 'Internal Target Release' field?
> Thanks.
Hi, this bug is still under investigation. No plans for Z stream.
Comment 14Viktor Prutyanov
2023-07-02 18:17:11 UTC
Hi Xiaoling,
Could you please reproduce the issue on latest virtio-win by running virtiofs from command-line with '-i' argument?
(In reply to Viktor Prutyanov from comment #14)
> Hi Xiaoling,
>
> Could you please reproduce the issue on latest virtio-win by running
> virtiofs from command-line with '-i' argument?
Sure, I have the result with prewhql-238 version.
Unfortunately, it still doesn't work.
Z:\>md5sum tEsT.txt
c9331b63c28e9028bdffd1643a430877 *tEsT.txt
Z:\>md5sum test.txt
No such file: test.txt
Z:\>type test.txt
SFADFASDFDSFDSFSAFDASFDASFD
Comment 16Viktor Prutyanov
2023-07-03 07:59:34 UTC
Could you please enable debug logging (-d -1 -D ...), perform the same things and share the log with me?
Comment 17Viktor Prutyanov
2023-07-03 08:35:31 UTC
(In reply to Viktor Prutyanov from comment #20)
> I can't reproduce the issue on both Win2019 and Win2022 with WinFsp
> 1.12.22339, so please share the virtiofs debug logs and daemon logs.
The log is in comment18 for win10 guest, do you want the log for win2019 or win2022?
Comment 22Yvugenfi@redhat.com
2023-07-17 07:08:38 UTC
Description of problem: After enabling case-insensitive for virtiofs service, md5sum or notepad cmd still fail to open the file with uppercase/lowercase letter. Version-Release number of selected component (if applicable): qemu-kvm-7.2.0-8.el9.x86_64 kernel-5.14.0-252.el9.x86_64 edk2-ovmf-20221207gitfff6d81270b5-5.el9.noarch virtio-win-prewhql-0.1-234 How reproducible: 100% Steps to Reproduce: 1.start virtiofs daemon # /usr/libexec/virtiofsd --shared-dir /home/test --socket-path /tmp/sock1 -d 2.boot up win2022 guest -chardev socket,id=char_virtiofs_fs,path=/tmp/sock1 \ -device vhost-user-fs-pci,id=vufs_virtiofs_fs,chardev=char_virtiofs_fs,tag=myfs,queue-size=1024,bus=pcie-root-port-3,addr=0x0 \ 3.start virtiofs service and enable case-insensitive z:\>sc create VirtioFsSvc binpath=virtiofs.exe start=auto depend="WinFsp.Launcher/VirtioFsDrv" DisplayName="Virtio FS Service" z:\>reg add HKLM\Software\VirtIO-FS /v CaseInsensitive /d 1 /t REG_DWORD 4. reboot guest 5. login guest and create a file on the shared dir, and create a file, try to get md5 checksum for the file. M:\>type file.txt hello M:\>type FILE.txt "hello" M:\>md5sum file.txt c4a246e402c50cd67617e59affd536b1 *file.txt M:\>md5sum FILE.txt No such file: FILE.txt 5. Try to repeat step 4 on the file on C: volume. C:\>md5sum test.txt 6dd4566eb245627b49f3abb7e4502dd6 *test.txt C:\>md5sum TEST.txt 6dd4566eb245627b49f3abb7e4502dd6 *test.txt Actual results: After step4, md5sum can't get the file with uppercase letter, it's sensitive to uppercase and lowercase letters. Expected results: For virtiofs volume,md5sum is insensitive with uppercase and lowercase letters as it does in C: Additional info: Notepad, type, dir, etc are insensitive with case letter.