Lines Matching full:volume

30 /* Volume identifier header magic number (ASCII "UBI!") */
34 * Volume type constants used in the volume identifier header.
36 * @UBI_VID_DYNAMIC: dynamic volume
37 * @UBI_VID_STATIC: static volume
45 * Volume flags used in the volume table record.
47 * @UBI_VTBL_AUTORESIZE_FLG: auto-resize this volume
48 * @UBI_VTBL_SKIP_CRC_CHECK_FLG: skip the CRC check done on a static volume at
54 * %UBI_VTBL_AUTORESIZE_FLG flag can be set only for one volume in the volume
55 * table. UBI automatically re-sizes the volume which has this flag and makes
56 * the volume to be of largest possible size. This means that if after the
58 * present on the device, it automatically appends all of them to the volume
60 * reserved physical eraseblocks are not taken). So, if there is a volume with
63 * reserved for this volume. Note, the %UBI_VTBL_AUTORESIZE_FLG bit is cleared
64 * after the volume had been initialized.
73 * number is required to calculate the volume sized and put them to the volume
79 * eraseblock handling, and then re-sizes the volume, not vice-versa. This
90 * @UBI_COMPAT_DELETE: delete this internal volume before anything is written
93 * @UBI_COMPAT_PRESERVE: preserve this internal volume - do not touch its
131 * is changed radically. This field is duplicated in the volume identifier
135 * volume identifier header and user data, relative to the beginning of the
160 * struct ubi_vid_hdr - on-flash UBI volume identifier header.
161 * @magic: volume identifier header magic number (%UBI_VID_HDR_MAGIC)
164 * @vol_type: volume type (%UBI_VID_DYNAMIC or %UBI_VID_STATIC)
167 * @compat: compatibility of this volume (%0, %UBI_COMPAT_DELETE,
169 * @vol_id: ID of this volume
173 * @used_ebs: total number of used logical eraseblocks in this volume
180 * @hdr_crc: volume identifier header CRC checksum
192 * and @lnum values in the volume identifier header. Suppose we have a logical
229 * UBI purposes. In this implementation there is only one internal volume - the
230 * layout volume. Internal volumes are the main mechanism of UBI extensions.
231 * For example, in future one may introduce a journal internal volume. Internal
239 * journal volume. And in this case, older UBI binaries, which know nothing
240 * about the journal volume, would just delete this volume and work perfectly
245 * eraseblock if this is a static volume. In case of dynamic volumes, it does
260 * eraseblocks the data of the volume takes. For dynamic volumes this field is
265 * eraseblocks of this volume. This is very handy when one uses block-oriented
266 * software (say, cramfs) on top of the UBI volume.
296 /* The layout volume contains the volume table */
302 #define UBI_LAYOUT_VOLUME_NAME "layout volume"
308 /* The maximum volume name length */
311 /* Size of the volume table record */
314 /* Size of the volume table record without the ending CRC */
318 * struct ubi_vtbl_record - a record in the volume table.
319 * @reserved_pebs: how many physical eraseblocks are reserved for this volume
320 * @alignment: volume alignment
323 * @vol_type: volume type (%UBI_DYNAMIC_VOLUME or %UBI_STATIC_VOLUME)
324 * @upd_marker: if volume update was started but not finished
325 * @name_len: volume name length
326 * @name: the volume name
327 * @flags: volume flags (%UBI_VTBL_AUTORESIZE_FLG)
331 * The volume table records are stored in the volume table, which is stored in
332 * the layout volume. The layout volume consists of 2 logical eraseblock, each
333 * of which contains a copy of the volume table (i.e., the volume table is
334 * duplicated). The volume table is an array of &struct ubi_vtbl_record
335 * objects indexed by the volume ID.
338 * %UBI_MAX_VOLUMES records, the volume table contains %UBI_MAX_VOLUMES
342 * The @upd_marker flag is used to implement volume update. It is set to %1
344 * interrupted, UBI knows that the volume is corrupted.
346 * The @alignment field is specified when the volume is created and cannot be
470 * struct ubi_fm_volhdr - Fastmap volume header
472 * @magic: Fastmap volume header magic number (%UBI_FM_VHDR_MAGIC)
473 * @vol_id: volume id of the fastmapped volume
474 * @vol_type: type of the fastmapped volume
475 * @data_pad: data_pad value of the fastmapped volume
476 * @used_ebs: number of used LEBs within this volume