I have an AXT1800 and when an external memory card is plugged-in it gets auto mounted at a mount point inside /tmp. Is it OK to keep it like that and use it to store permanent files? Won’t the system periodically clean the /tmp directory?
I would not trust /tmp as mount point. Even if it works fine, it could lead to data loss in future.
See Filesystem Hierarchy Standard - Wikipedia als reference.
The right point would be /media for dynamic mounts or /mnt for permanent mounts. You could use /mnt/tmp do be safe.
@LupusE Agreed.
@One
That strikes me as wrong, if not dangerous for data. I’d jump into LuCI & check or adjust that mount point.
The GL GUI supports exFAT, FAT, NTFS for file systems OOTB but they’re not the only options… there’s better ones to prolong flash/read-write lifetime if you intend to keep the storage device permanently attached to the Slate AX (eg: F2FS).
GL GUI → System → Advanced Setting → LuCI → System → Mount Points
LuCI’s password is the same as GL GUI.
Otherwise pull the card/drive fr the Slate AX, format in exFAT & reinsert; GL’s GUI should be more ‘sane’ that.
I did a Google search for it and all the results are about GL.iNet. It seems its a default mount point used by GL.iNet. I wonder why, hopefully a staff member can clarify.
They’ll want to know what version of the firmware you’re running. The latest stable build for the Slate AX is 4.4.6… (showing as release1 on my Flint/GL-AX1800).
They’ll probably want to know what FS is on the card, too.
GL GUI → System → Upgrade
Device: GL-AXT1800
Firmware Version: OpenWrt 21.02-SNAPSHOT r16399+159-c67509efd7 / LuCI openwrt-22.03 branch git-21.284.67084-e4d24f0
Kernel Version: 4.4.60
Yes, it’s the default on latest, this is common in most embedded Linux, a failed mounting attempt would lead to writing to memory, crash and restart… instead of onboard flash which can soft brick the device when apps want to write lockfiles on next start due to storage being full.
Could mount /mnt
as tmpfs
considering that the router has the ability to install third party that can manipulate /tmp
area, but otherwise it’s unnecessary outside desktop Linux.
So would it be fair to suspect the external storage device is failing (eg. bad blocks/sectors)?
@One
I really would run a couple full overwrites on that card & just dump exFAT on it to test it. That’s just me, though.