Lines Matching full:update
9 * Jan 2007: Alexander Schmidt, hacked per-volume update.
13 * This file contains implementation of the volume update and atomic LEB change
16 * The update operation is based on the per-volume update marker which is
17 * stored in the volume table. The update marker is set before the update
18 * starts, and removed after the update has been finished. So if the update was
19 * interrupted by an unclean re-boot or due to some other reasons, the update
21 * device next time. If the update marker is set for a volume, the volume is
22 * treated as damaged and most I/O operations are prohibited. Only a new update
25 * Note, in general it is possible to implement the update operation as a
41 * set_update_marker - set update marker.
45 * This function sets the update marker flag for volume @vol. Returns zero
53 dbg_gen("set update marker for volume %d", vol->vol_id); in set_update_marker()
72 * clear_update_marker - clear update marker.
77 * This function clears the update marker for volume @vol, sets new volume
87 dbg_gen("clear update marker for volume %d", vol->vol_id); in clear_update_marker()
112 * ubi_start_update - start volume update.
115 * @bytes: update bytes
117 * This function starts volume update operation. If @bytes is zero, the volume
126 dbg_gen("start update of volume %d, %llu bytes", vol->vol_id, bytes); in ubi_start_update()
198 * write_leb - write update data.
207 * This function writes update data to corresponding logical eraseblock. In
217 * space is writable after the update.
260 * ubi_more_update_data - write more update data.
267 * be called arbitrary number of times until all the update data arriveis. This
269 * last call if the whole volume update has been successfully finished, and a
299 * copy the data to our update buffer and wait for more data or in ubi_more_update_data()
300 * flush it if the whole eraseblock is written or the update in ubi_more_update_data()
366 /* The update is finished, clear the update marker */ in ubi_more_update_data()