Hi, I've run into an issue when trying to use fsck with an ext4 image when it has '=' in its name. Repro steps: 1. fallocate -l 1G test=.img 2. mkfs.ext4 test=.img 3. fsck test=.img Response: 'fsck.ext4: Unable to resolve '<path>/test=.img' Expected: fsck to do it's thing. Observations: Originally I wasn't sure what the source was, I thought that maybe mkfs wasn't creating the image appropriately. However, I've tried: - renaming the image - creating a hard-link to the image Running fsck on either the renamed image, or the hard-link, works as expected. Kernel version: Linux version 4.19.251-13516-ga0bcf8d80077 Environment: Running on a Chromebook Kind regards, Daniel
