I have noticed that hAP and some other products now have FLASH as their MAIN SYSTEM DISKS.
I use logging for most of my devices, and the most important information that often is needed for bug/fault search if something doesnt work as expected I store on the DISK of the unit.
I use the Logging function, where I create a LogAction with type “disk” for those log-actions that need log to be persistent even after reboot, and this has worked fine since I started using MT.
However if I do this on these new flash based units, the file seems to be deleted on every reboot of the device, and new empty file created after boot, wich makes it useless for the intended purpose of retaining the info even after a reboot.
If I wanted this kind of log behaviour I would simply have chosen MEMORY as log type! 
Same happens if I hit BACKUP in filemenu, the backup is created and I can copy it to PC. However after first reboot it dissappears from disk. This is also a bit annoying since I always make a backup of the last working config of each unit, that stays on the disk in case I at some point need to revert to last working config for some reason.
If the files just dissappear on each reboot, then its kinda wasted to store to disk…
Is it just me who has missed some new genious command to make it store it directly on the flash “permanent”, or is this a BUG or even intended operation???