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.

0
U

Property:ubifs

From BoxMatrix
(Redirected from ubifs)


BoxMatrix >> System >> ubifs @ 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-Filesystem

Goto:   Dependencies   -   Model-Matrix   -   Missing Supportdata   -   SMW-Browser

Details

ubifs is a filesystem running on top of the UBI volume manager.
It is used in FRITZ!OS to mount read / write volumes like the avm_userdata volume.

7520 fw 7.29:

avm_userdata is mounted to /var/media/ftp using ubifs:

root@fritz:/var/mod/root# mount | grep ubifs

/dev/ubi0_3 on /var/media/ftp type ubifs (rw,sync,relatime)

ubifs] creates a background thread for each mounted partition:

root@fritz:/var/mod/root# ps | grep ubifs

1789 root         0 SW   [ubifs_bgt0_3]

An UBI volume is a logical part of the ubi partition, which is attached at boot time to the UBI manager:.

root@fritz:/var/mod/root# dmesg | grep ubi | head -n 3

[    1.779041] 0x000001300000-0x000008000000 : "ubi"
[    1.893466] [mtd_add_handler] UBI on MTD ubi
[    4.303419] ubi0: attaching mtd4

The UBI manager creates the device ubi0 for the attached mtd partition, and ubi0_0++ for each volume on it.
Let's see all volumes:

root@fritz1:/var/mod/root# ubinfo -a | grep Name

Name:        avm_filesys_0
Name:        avm_filesys_1
Name:        avm_config
Name:        avm_userdata

The raw size of the device ubi0_3 is 12.4 MB, this would be what dd could read from it:

root@fritz1:/var/mod/root# ubinfo -d 0 -N avm_userdata

Volume ID:   3 (on ubi0)
Type:        dynamic
Alignment:   1
Size:        103 LEBs (13078528 bytes, 12.4 MiB)
State:       OK
Name:        avm_userdata
Character device major/minor: 245:4

The bootlog shows this raw size results in 11 MB filesystem, nearly 1 MB journal and 248 kB loss:

root@fritz:/var/mod/root# dmesg | grep 'FS size'

[   18.809300] UBIFS (ubi0:3): FS size: 11808768 bytes (11 MiB, 93 LEBs), journal size 1015809 bytes (0 MiB, 6 LEBs)

The size usable by the system is even smaller - 9.7 MB which is 78% of the raw size:

root@fritz1:/var/mod/root# df -h | grep ubi

/dev/ubi0_3               9.7M      1.4M      7.8M  15% /var/media/ftp

root@fritz1:/var/mod/root# df | grep ubi

/dev/ubi0_3               9976      1416      8016  15% /var/media/ftp

Dependencies

Daily updated index of all dependencies of this filesystem. 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 filesystem

Model-Matrix

Daily updated index of the presence, path and size of this filesystem for each model. Last update: 2024-04-18 06:30 GMT.
Showing all models using this filesystem. 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.

SMW-Browser

Information is currently being retrieved from the backend.