222 lines · plain
1What: /sys/class/ubi/2Date: July 20063KernelVersion: 2.6.224Contact: Artem Bityutskiy <dedekind@infradead.org>5Description:6 The ubi/ class sub-directory belongs to the UBI subsystem and7 provides general UBI information, per-UBI device information8 and per-UBI volume information.9 10What: /sys/class/ubi/version11Date: July 200612KernelVersion: 2.6.2213Contact: Artem Bityutskiy <dedekind@infradead.org>14Description:15 This file contains version of the latest supported UBI on-media16 format. Currently it is 1, and there is no plan to change this.17 However, if in the future UBI needs on-flash format changes18 which cannot be done in a compatible manner, a new format19 version will be added. So this is a mechanism for possible20 future backward-compatible (but forward-incompatible)21 improvements.22 23What: /sys/class/ubiX/24Date: July 200625KernelVersion: 2.6.2226Contact: Artem Bityutskiy <dedekind@infradead.org>27Description:28 The /sys/class/ubi0, /sys/class/ubi1, etc directories describe29 UBI devices (UBI device 0, 1, etc). They contain general UBI30 device information and per UBI volume information (each UBI31 device may have many UBI volumes)32 33What: /sys/class/ubi/ubiX/avail_eraseblocks34Date: July 200635KernelVersion: 2.6.2236Contact: Artem Bityutskiy <dedekind@infradead.org>37Description:38 Amount of available logical eraseblock. For example, one may39 create a new UBI volume which has this amount of logical40 eraseblocks.41 42What: /sys/class/ubi/ubiX/bad_peb_count43Date: July 200644KernelVersion: 2.6.2245Contact: Artem Bityutskiy <dedekind@infradead.org>46Description:47 Count of bad physical eraseblocks on the underlying MTD device.48 49What: /sys/class/ubi/ubiX/bgt_enabled50Date: July 200651KernelVersion: 2.6.2252Contact: Artem Bityutskiy <dedekind@infradead.org>53Description:54 Contains ASCII "0\n" if the UBI background thread is disabled,55 and ASCII "1\n" if it is enabled.56 57What: /sys/class/ubi/ubiX/dev58Date: July 200659KernelVersion: 2.6.2260Contact: Artem Bityutskiy <dedekind@infradead.org>61Description:62 Major and minor numbers of the character device corresponding63 to this UBI device (in <major>:<minor> format).64 65What: /sys/class/ubi/ubiX/eraseblock_size66Date: July 200667KernelVersion: 2.6.2268Contact: Artem Bityutskiy <dedekind@infradead.org>69Description:70 Maximum logical eraseblock size this UBI device may provide. UBI71 volumes may have smaller logical eraseblock size because of their72 alignment.73 74What: /sys/class/ubi/ubiX/max_ec75Date: July 200676KernelVersion: 2.6.2277Contact: Artem Bityutskiy <dedekind@infradead.org>78Description:79 Maximum physical eraseblock erase counter value.80 81What: /sys/class/ubi/ubiX/max_vol_count82Date: July 200683KernelVersion: 2.6.2284Contact: Artem Bityutskiy <dedekind@infradead.org>85Description:86 Maximum number of volumes which this UBI device may have.87 88What: /sys/class/ubi/ubiX/min_io_size89Date: July 200690KernelVersion: 2.6.2291Contact: Artem Bityutskiy <dedekind@infradead.org>92Description:93 Minimum input/output unit size. All the I/O may only be done94 in fractions of the contained number.95 96What: /sys/class/ubi/ubiX/mtd_num97Date: January 200898KernelVersion: 2.6.2599Contact: Artem Bityutskiy <dedekind@infradead.org>100Description:101 Number of the underlying MTD device.102 103What: /sys/class/ubi/ubiX/reserved_for_bad104Date: July 2006105KernelVersion: 2.6.22106Contact: Artem Bityutskiy <dedekind@infradead.org>107Description:108 Number of physical eraseblocks reserved for bad block handling.109 110What: /sys/class/ubi/ubiX/ro_mode111Date: April 2016112KernelVersion: 4.7113Contact: linux-mtd@lists.infradead.org114Description:115 Contains ASCII "1\n" if the read-only flag is set on this116 device, and "0\n" if it is cleared. UBI devices mark themselves117 as read-only when they detect an unrecoverable error.118 119What: /sys/class/ubi/ubiX/total_eraseblocks120Date: July 2006121KernelVersion: 2.6.22122Contact: Artem Bityutskiy <dedekind@infradead.org>123Description:124 Total number of good (not marked as bad) physical eraseblocks on125 the underlying MTD device.126 127What: /sys/class/ubi/ubiX/volumes_count128Date: July 2006129KernelVersion: 2.6.22130Contact: Artem Bityutskiy <dedekind@infradead.org>131Description:132 Count of volumes on this UBI device.133 134What: /sys/class/ubi/ubiX/ubiX_Y/135Date: July 2006136KernelVersion: 2.6.22137Contact: Artem Bityutskiy <dedekind@infradead.org>138Description:139 The /sys/class/ubi/ubiX/ubiX_0/, /sys/class/ubi/ubiX/ubiX_1/,140 etc directories describe UBI volumes on UBI device X (volumes141 0, 1, etc).142 143What: /sys/class/ubi/ubiX/ubiX_Y/alignment144Date: July 2006145KernelVersion: 2.6.22146Contact: Artem Bityutskiy <dedekind@infradead.org>147Description:148 Volume alignment - the value the logical eraseblock size of149 this volume has to be aligned on. For example, 2048 means that150 logical eraseblock size is multiple of 2048. In other words,151 volume logical eraseblock size is UBI device logical eraseblock152 size aligned to the alignment value.153 154What: /sys/class/ubi/ubiX/ubiX_Y/corrupted155Date: July 2006156KernelVersion: 2.6.22157Contact: Artem Bityutskiy <dedekind@infradead.org>158Description:159 Contains ASCII "0\n" if the UBI volume is OK, and ASCII "1\n"160 if it is corrupted (e.g., due to an interrupted volume update).161 162What: /sys/class/ubi/ubiX/ubiX_Y/data_bytes163Date: July 2006164KernelVersion: 2.6.22165Contact: Artem Bityutskiy <dedekind@infradead.org>166Description:167 The amount of data this volume contains. This value makes sense168 only for static volumes, and for dynamic volume it equivalent169 to the total volume size in bytes.170 171What: /sys/class/ubi/ubiX/ubiX_Y/dev172Date: July 2006173KernelVersion: 2.6.22174Contact: Artem Bityutskiy <dedekind@infradead.org>175Description:176 Major and minor numbers of the character device corresponding177 to this UBI volume (in <major>:<minor> format).178 179What: /sys/class/ubi/ubiX/ubiX_Y/name180Date: July 2006181KernelVersion: 2.6.22182Contact: Artem Bityutskiy <dedekind@infradead.org>183Description:184 Volume name.185 186What: /sys/class/ubi/ubiX/ubiX_Y/reserved_ebs187Date: July 2006188KernelVersion: 2.6.22189Contact: Artem Bityutskiy <dedekind@infradead.org>190Description:191 Count of physical eraseblock reserved for this volume.192 Equivalent to the volume size in logical eraseblocks.193 194What: /sys/class/ubi/ubiX/ubiX_Y/type195Date: July 2006196KernelVersion: 2.6.22197Contact: Artem Bityutskiy <dedekind@infradead.org>198Description:199 Volume type. Contains ASCII "dynamic\n" for dynamic volumes and200 "static\n" for static volumes.201 202What: /sys/class/ubi/ubiX/ubiX_Y/upd_marker203Date: July 2006204KernelVersion: 2.6.22205Contact: Artem Bityutskiy <dedekind@infradead.org>206Description:207 Contains ASCII "0\n" if the update marker is not set for this208 volume, and "1\n" if it is set. The update marker is set when209 volume update starts, and cleaned when it ends. So the presence210 of the update marker indicates that the volume is being updated211 at the moment of the update was interrupted. The later may be212 checked using the "corrupted" sysfs file.213 214What: /sys/class/ubi/ubiX/ubiX_Y/usable_eb_size215Date: July 2006216KernelVersion: 2.6.22217Contact: Artem Bityutskiy <dedekind@infradead.org>218Description:219 Logical eraseblock size of this volume. Equivalent to logical220 eraseblock size of the device aligned on the volume alignment221 value.222