Storage and updates
This page explains where your files stay, when they are saved, and how updates work.
Where your files live
NanumOS works on its files in memory first. The working copy must be written to the persist area on the disk, or it is gone after power off. The persist area depends on the device.
| Device | Persist area |
|---|---|
| NanumOS USB stick | The storage section on the stick |
| PC with NanumOS installed on the internal disk | One file (/zeusos/disk.img) inside the existing operating system's partition. The partitions are not changed. |
| QEMU test | A test disk image |
With no persist area, files live in memory only and disappear when you turn off. sync then says sync: no disk; files are in RAM only.
What the persist area holds
| Data | Place |
|---|---|
| Wi-Fi | One file per network under /etc/wifi. The password itself is not stored, only the connection key (PMK). Only root can read these files. |
/tmp, /proc and /bin are not saved. /tmp is empty at every start.
How saving works
On a disk marked for auto-save (the storage section of a NanumOS USB stick and the installed disk file) you do nothing.
- At start, the newest saved state is loaded.
- After you change a file and make no further change for 2 seconds, it is saved by itself. If you keep changing things, it is saved within 10 seconds of the first change at the latest.
- It also saves while the Zeus app or a long-running Terminal program is open. Then it saves at most once a minute, and closing the Zeus app saves at once.
syncsaves right now.reboot,poweroffandexit, and Restart, Shut Down and Log Out in the desktop power menu, save first and then finish.
A save writes a new copy in a different place and checks it before switching to it. If the power goes out during a save, you get the old state or the new state, never a mix.
A Save inside an app (for example Notepad) writes the file. Putting that file on the disk is the job of the auto-save above.
On a test disk where auto-save is off, you do it yourself.
| Command | What it does |
|---|---|
save | Writes all files to the disk now. |
load | Loads the newest saved copy from the disk. It refuses if files already exist (it never overwrites). |
sync | Saves if something changed. |
storage | Shows the mode (auto or manual), the last save number, and whether there are unsaved changes. |
storage auto | Marks the disk as an auto-save disk. It refuses if changed files were never saved. |
df | Shows the size and state of the persist area (saved, unsaved changes, FULL: next save fails, disk error). |
What is not saved (caches)
Things an app can download or make again are not put in the persist area. Like a sample on a shop shelf, the app puts it back when it is gone — so there is that much more room for your own documents and photos.
- files inside the
.cachefolder of your home (photo previews, news, weather)
After a restart the radio opens at once with its built-in list of 4,000 stations and downloads the full list in the background once the network is up.
What to do now: nothing.
How full is it
- Files shows it in its bottom line, e.g. "Storage 10% used, 25 MB free".
- Ask the assistant "check my computer": the 「저장 공간」 (storage) row says how full it is, the biggest things (e.g. Music 1.5 MB) and how much cache is not saved.
- Over 90 %, a notice "Storage is almost full" appears at the top right. If a save does not fit, "Storage is full" appears. Everything saved before is still there; only the newest changes are in memory.
What to do now: when a notice appears, delete big files in Files or move them to a USB stick. It saves again as soon as there is room.
Technical details: cat /proc/storage shows total_kb, used_kb, used_pct, cache_kb, state (saved, unsaved, nearly-full, full, error), last_error and big= lines. df shows the same numbers.
Space
Up to 256 entries (files and folders) are saved. One file can be up to 16 MiB. When the persist area is full, df says FULL: next save fails; auto-save reports it once and tries again after the next change. Delete files to make room. Writes are not blocked while you work, so it can fill up without being saved. Look at df now and then.
If the persist area is found damaged, that boot does not write to the disk and keeps files in memory only. sync then reports the error.
When saving stops for a moment
If the computer is very busy, the disk may not answer for a moment, like a crowded post office that sends letters late. What you saved before stays as it is; only your latest changes wait in memory. NanumOS saves again by itself after a few seconds, then a few tens of seconds. When it works again, a "works again" line is logged.
What to do now: leave the computer on and wait a minute or two. Ask the assistant to "check the computer": the Storage row says whether it is "saving again by itself".
Technical details: cat /proc/storage shows state=retrying, last_error=-5, io_fails and retry_in_s. When it works again: state=saved, last_error=0, and io_recoveries goes up by one. Retries come after 5, 15, 30 and 60 seconds, then every 2 minutes. The arm64 disk (virtio-blk) waits for a request that takes over 5 seconds, resets the device and sends the request again after 20 seconds, calls the disk broken only after three failed attempts, and tries to bring it back 30 seconds later. The BLOCK health line of block-info counts the slow requests. Before, one request over 5 seconds turned saving off until the next restart.
Updates
A NanumOS release is a read-only image. The USB stick has a separate update section with room for two releases (slots 1 and 2). A new release never overwrites the one that is running.
Use it from the console.
| Command | What it does |
|---|---|
zeus-update status | Shows the running release, the confirmed one, the pending one and the last result. |
zeus-update check | Looks for a newer release. |
zeus-update get | Downloads a new release, verifies it and writes it to a free slot. |
zeus-update rollback | Goes back to the previous release (root). |
An update goes like this.
- The signed list and the image are downloaded over HTTPS.
- The signature, "is it newer", and the image's sha256 are checked. The hash is checked twice: as received and again after reading it back from the slot. If anything is wrong, nothing changes.
- The new release is tried once, at the next start.
- If the new release reaches the command prompt, it becomes the confirmed release.
- If it does not (it hangs or resets), the next start goes back to the old release by itself.
Going back to the previous version
If a new release fails its start test, you do nothing. The next start is the old release.
If the new release starts but you do not like it, type zeus-update rollback as root. From the next start you are on the previous release. If there is none, you go back to the release that was on the stick from the beginning.
Updates keep your data
An update only touches the section that holds releases. It does not erase the persist area with your files. Writing a new release to a USB stick again also keeps the size and contents of the persist area. A release that changes the storage format ships only after the move from the old format to the new one has passed its test.
To empty the persist area on purpose, you have to pick the separate erase option in the stick tool. A normal update never does that.
Built-in sample files
On the first start, sample pictures, music, videos and documents go into your home folder (Pictures/샘플, Music/샘플, Movies, Documents/샘플). When a new version brings a new sample, only that file is added, once, at the next start — like a shop slipping one new sample into your drawer, never putting back one you threw away.
- A sample you deleted does not come back. If you deleted a whole sample folder, new samples for that folder are not added either.
- If a file of yours has the same name, your file stays as it is and the sample is not added.
- To bring deleted samples back, press Settings › Apps › Sample Files › "Add samples again".
- The document samples (a report PDF, a contract as .docx and .hwpx, a household ledger .xlsx) are all made by 나눔OS itself, pictures included. The old "샘플 문서" files (with an empty picture box) and anyone else's documents are no longer samples: an old copy you left untouched is removed on the next start; one you edited or renamed stays.
What to do now: open the PDF app — the five PDFs in Documents/샘플 are listed.
Not yet
- The update signing key for official images and the public address that holds updates are not decided yet. A build without a key refuses every update. Today
zeus-updateis confirmed in QEMU tests only. - The update section was confirmed on the USB stick only, not on the internal disk file of an installed PC.
- The desktop has no update screen. Updating is a console command.
- There is no way to take a snapshot of the whole system and roll it back. Only the release can be rolled back.
- Storage on the phone version (lite) is not covered here. See Phone version.
NanumOS 0.1.8349 · 2026-11-16