FAT: Renaming folder after huge file move causes KDL

[mbrumbelow]

Version: hrev58097
CPU: 8 Processor Intel Core i5-8279U @ 2.40 Ghz
Memory: 16226 MiB Memory

1. Create 1TB binary file
   
2. Copy file to an external USB SSD drive formatted FAT32
3. Place the file in a newly created directory with any name
4. Rename the new folder and hit enter or click away
5. KDL (See attached)

[mbrumbelow]

KDL Image

[Jim906]

mbrumbelow, thank you for reporting this. Could you tell me the total capacity (including used space and free space) of the FAT32 partition on this USB SSD drive? If might also be informative if you could run driveinfo in a terminal and post the output (you may need to unmount the partition first):

~> driveinfo [partition name]

How was this FAT32 partition mounted (automatically at boot, in DriveSetup, mount command in a terminal...)?

The FAT driver is currently configured to force read-only status when mounting a partition large enough to hold a 1 TB file (this is meant to be a temporary limitation until the revised driver undergoes more testing). That this didn't happen suggests that maybe the driver made a mistake in determining the size of the partition at mount time. Later, when you tried to work with a file, the crash might have been caused by the driver working with this incorrect size information.

[Jim906]

The "max 204799" in the panic message makes me think there was an overflow of sector count. A patch that should fix this is under review (​https://review.haiku-os.org/c/haiku/+/8426). I am not set up to reproduce this bug on my system for testing though.

I still don't understand why the partition was not mounted read-only based on its size, since at the time the ticket was submitted, the limit for mounting read-write was below 1 TB (the limit has since been increased to 2 TB in the master branch). Maybe the user built the installation file from source and had turned off the code to force read-only mounting.

[waddlesplash]

Fix merged in hrev58183.