If you like BoxMatrix then please contribute Supportdata, Supportdata2, Firmware and/or Hardware (get in touch).
My metamonk@yahoo.com is not reachable by me since years. Please use hippie2000@webnmail.de instead.
Property:filesystem
| BoxMatrix >> System >> filesystem | @ BoxMatrix - IRC-Chat - Translate: de es fr it nl pl |
| News | Selectors | Models | Accessories | Components | Environment | Config | Commands | System | Webif | Software | Develop | Lexicon | Community | Project | Media |
| Devices | Filesystems | Partitions | Sockets | Netlink | Pipes | Interfaces | Bridges | Ports | Events | Sources | Sinks | AVMIPC | Processes | Watchdogs | Memory | Slab | Vmalloc | ProcFS | SysFS | Research |
Linux-Partition
| Partition: | filesystem - type Part, Vol | Wiki | Freetz | IPPF | whmf | AVM | Web |
| Location: | System >> Linux-Partitions - Origin: AVM | ||||||
| Device: | mtdblock0, mtdblock1, mtdblock3, mtdblock4, mtdblock6, mtdblock7, ubi0_x | ||||||
| Properties: | Firmware: 4.31 - 7.57 | ||||||
| Function: | The currently active rootfs partition or volume for some models. | ||||||
Goto: Dependencies - Model-Matrix - Missing Supportdata - SMW-Browser
Details
filesystem is the currently active rootfs partition or volume for some models.
For Dual-Boot models the inactive counterpart is the reserved-filesystem partition or volume.
On AR7 models with ohio_flash driver this partition contains rootfs + jffs2 without a counterpart.
For other single boot models without a counterpart this is named rootfs.
On non UBI Dual-Boot models filesystem and reserved-filesystem are logical names honoring the linux_fs_start variable:
7490 fw 7.29 - linux_fs_start = 0:
fritz3:/var/mod/root $ grep filesystem /proc/mtd mtd1: 03000000 00020000 "filesystem" mtd3: 03000000 00020000 "reserved-filesystem" mtd5: 19600000 00020000 "nand-filesystem"
7490 fw 7.29 - linux_fs_start = 1:
fritz3:/var/mod/root $ grep filesystem /proc/mtd mtd1: 03000000 00020000 "reserved-filesystem" mtd3: 03000000 00020000 "filesystem" mtd5: 19600000 00020000 "nand-filesystem"
On some CONFIG_UBI models this is the avm_filesys_0 or avm_filesys_1 volume.
Both get a device and are renamed before they get entries in /proc/mtd.
7530 fw 7.39:
root@fritz:/var/mod/root# grep filesystem /proc/mtd mtd5: 02c14000 0001f000 "filesystem" mtd6: 02c14000 0001f000 "reserved-filesystem" mtd8: 00c79000 0001f000 "nand-filesystem" root@fritz:/var/mod/root# ubinfo -a | grep filesys Name: avm_filesys_0 Name: avm_filesys_1 root@fritz:/var/mod/root# blkid /dev/ubi0_3: UUID="xxxx" TYPE="ubifs" /dev/ubi0_1: TYPE="squashfs" /dev/ubi0_0: TYPE="squashfs" /dev/mtdblock4: UUID="xxxx" TYPE="ubi" /dev/mtdblock5: TYPE="squashfs" /dev/mtdblock6: TYPE="squashfs"
The devices always use the sequential UBI volume order, regardless of the linux_fs_start variable.
Just the mtd partition names are renamed different depending on this variable.
With linux_fs_start = 0:
mtd5: 02c14000 0001f000 "filesystem" mtd6: 02c14000 0001f000 "reserved-filesystem"
With linux_fs_start = 1:
mtd5: 02c14000 0001f000 "reserved-filesystem" mtd6: 02c14000 0001f000 "filesystem"
Dependencies
Daily updated index of all dependencies of this partition. Last update: GMT.
A * in the Mod column marks info from Supportdata-Probes, which will always stay incomplete.
A ** in the Mod column marks info from Supportdata2 probes, which by their nature will stay way more incomplete.
A - in the Mod column marks manual research, the Firmware then shows where the item occurs, not the Relation.
| Relation | Typ | Object | Mod | Firmware | Info | Origin |
|---|---|---|---|---|---|---|
| 0 dependencies for this partition | ||||||
Model-Matrix
Daily updated index of the presence, path and size of this partition for each model. Last update: 2024-04-19 06:37 GMT.
Showing all models using this partition. Click any column header (click-wait-click) to sort the list by the respective data.
The (main/scrpn/boot/arm/prx/atom) label in the Model column shows which CPU is meant for models with multiple Linux instances.
Note that this list comes from Supportdata-Probes, which can have arbitrary settings and come from different firmware versions.
It doesn't say much if a model is not listed here. It may be a missing supportdata file or just a disabled feature.
Missing Supportdata
The data in this article is incomplete due to missing Supportdata-Probes for the models listed below.
If you own any of these models and would like to help then please get in touch.
