Page 1 of 1

debian 64 bit guest aborted

PostPosted: 29. May 2019, 13:21
by kidalabama
00:00:00.240186 File system of '/srv/dev-disk-by-label-1/vb/debian64_2/debian64_1_d_2.vdi' is ext4

00:00:00.240372 Console: VM runtime error: fatal=false, errorID=FatPartitionDetected message="The medium '/srv/dev-disk-by-label-1/vb/debian64_2/debian64_1_d_2.vdi' has a logical size of 10TB but the file system the medium is located on can only handle files up to 7TB in theory.

00:00:00.240374 We strongly recommend to put all your virtual disk images and the snapshot folder onto a proper file system (e.g. ext3) with a sufficient size"

00:00:00.262306 Shared clipboard service loaded

not fat partition but seeing fat partition why ? and why system aborted ?

debian64_1_d_2.vdi=10 TB
Virtualbox 5.2.24
host system openmediavault
Thank you.

Re: debian 64 bit guest aborted

PostPosted: 29. May 2019, 16:45
by mpack
Seems clearly wrong. I think you should raise a BugTracker ticket for this - but include a log file for version information - and hopefully that will not prove to be the Linux fork.

Re: debian 64 bit guest aborted

PostPosted: 29. May 2019, 18:05
by klaus
For some Linux filesystems the maximum file size is much less than the overall maximum filesystem size. Quick search found the following for ext4: file 16TiB, filesystem 1EiB. (Actually a little less, but that's not what counts).

Didn't find a commonly used filesystem which maxes out at a bit below 8T (which gives the rounding error talking about 7T), but VirtualBox simply asks the OS what the max file size limits are for a specific location on disk and therefore the checks in the code are likely to be correct.

We need a VBox.log file, it would show the filesystem type for all disk images.

Re: debian 64 bit guest aborted

PostPosted: 29. May 2019, 18:31
by mpack
Could this error have resulted from locating the VDI in a small partition? I'm guessing that the OS call you mention might return the smaller of (ext4_max_filesize, current_partition_size).

Re: debian 64 bit guest aborted

PostPosted: 29. May 2019, 19:43
by klaus
This would be a new kind of excessive cleverness not seen ever before... the sanity check leading to this error isn't meant to prevent the filesystem from filling up, it's meant to catch the very nasty "suddenly the file simply won't be able to grow any more" situation early, before it leads to data loss.