On Wed, May 21, 2025 at 10:11:33PM +0100, Tim Woodall wrote: > > when doing rm of a very large file (or possibly just a file whose block > extends past 2^32-1) it fails with > > FUSE2FS-remove_inode: put ino=12 links=1 > fuse: bad error value: 75 > unique: 16, error: -34 (Numerical result out of range), outsize: 16 > rm: cannot remove 'mount/filler': Numerical result out of range > > rm in debugfs does work. Attached patch replaces the deallocate block > logic with that from debugfs. > > This possibly points to a bug in the underlying ext2_punch routine that > fuse2fs is using but I haven't tried to investigate further. This > function is also called from punch_helper so I suspect that using > fallocate to punch holes might also have problems.
Tim, Thanks for sending this bug report. As it turns out, Darrick has been doing a huge amount of work fixing a large number of bugs in fuse2fs by running it through fstests. He's also done some great work improving the perforance of fuse2fs. I don't *think* your bug report has been addressed by the patches Darrck has sent me, either the ones which I've already accepted into the e2fsprgs git repo, or the 90 patches that just showed up in my inbox this morning. :-) But perhaps I missed something, or it might be one of the patches that Darrck has queed up but which he hasn't sent upstream yet. Darrick, does this report ring a bell? Tim's proposed patches and reprducer can be found at: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1106241 Thanks, - Ted
