Use or access large NTFS cluster sizes (e.g. 2048 kb / 2049 kb / 2M or 2MB) in an Android (or Linux) OS?

I have an external media storage drive where I (*believe that I*) have formatted the partitions as 2048 kb (or 2,048 kb for any Googlers searching) cluster sizes and there are a couple of smaller clustered partitions on the same USB drive. This might be termed as 2049 kb or 2,049 kb ( or 2M / 2 M / 2MB / 2 MB ) in some places, but 2048 is the number that Windows provides when you format. I'm pretty sure that is the number that I chose when I formatted them. However, the actual number in the cluster report is 2097152 or 2,097,152 from this command: fsutil fsinfo ntfsinfo [drive] **However, whenever the physical device is correctly recognised by Android operating systems, it will not recognise the large cluster partitions. Is this an Android-specific fault, or is it working as designed, and wasn't ever supposed to read clusters / file allocations of that size?** I have (I believe exhaustively) searched for answers on this (at 2048 and 2049), but as you can appreciate, I get a lot of unrelated stuff. I'm aware of how to Google well (quotes, brackets, intitles, etc), and have searched this network, too, and have not found a solution. This is a bit of a pain, is all, as it means that my drive can essentially only be used on my Windows computers, and then (I think) only a couple of them. On Android, I've tried ES File Explorer on a Shield, and CX on a Galaxy Tab S4. I can't afford the NTFS plugin for Total Commander, but I would guess it's an OS restriction, not an App one. KODI doesn't see the partitions, and I'm not sure where to go next, to be honest. I mention Linux in the title because my router (stock TP-Link Archer C1200 v2) also won't recognise the large clustered drives. I'll be testing on a Pi, later, to see if that gives me any joy, and a Mint box at my parents, when I can. Windows 10 devices have no issues with the drive, I have a VISTA box that I can test, but I have a feeling that it won't recognise the drive as I may have tested it months ago. (This post has been in draft for a *long* time. ;-) With the greatest respect (and I think Stack avoids this well, but still) let's not delve into *why* I chose NTFS or these cluster / file allocation sizes. ---------- 2 *LARGE* File size drives at this configuration *NOT* seen by Android devices: Bytes Per Sector : 512 Bytes Per Physical Sector : 4096 Bytes Per Cluster : 2097152 Bytes Per FileRecord Segment : 1024 1 *SMALLER* File size drives at this configuration *ARE* seen by Android devices: Bytes Per Sector : 512 Bytes Per Physical Sector : 4096 Bytes Per Cluster : 32768 Bytes Per FileRecord Segment : 1024 2 *EVEN SMALLER* File size drives at this configuration *ARE* seen by Android devices: Bytes Per Sector : 512 Bytes Per Physical Sector : 4096 Bytes Per Cluster : 4096 Bytes Per FileRecord Segment : 1024