Searched full:checkpoint (Results 1 – 25 of 99) sorted by relevance
1234
20 * struct nilfs_cpinfo - checkpoint information23 * @ci_cno: checkpoint number25 * @ci_nblk_inc: number of blocks incremented by this checkpoint28 * @ci_next: next checkpoint number in snapshot list41 /* checkpoint flags */143 * struct nilfs_cpmode - change checkpoint mode structure144 * @cm_cno: checkpoint number145 * @cm_mode: mode of checkpoint171 * struct nilfs_period - period of checkpoint numbers172 * @p_start: start checkpoint number (inclusive)[all …]
82 * @sr_cpfile: checkpoint file inode162 __le64 s_last_cno; /* Last checkpoint number */187 __le16 s_checkpoint_size; /* Size of a checkpoint */240 #define NILFS_CPFILE_INO 4 /* checkpoint file */339 * @fi_cno: checkpoint number396 * @ss_cno: checkpoint number469 * @de_start: start checkpoint number470 * @de_end: end checkpoint number484 * @ssl_next: next checkpoint number on snapshot list485 * @ssl_prev: previous checkpoint number on snapshot list[all …]
308 size of a checkpoint to be slightly less than a half the log.310 Apart from this size requirement, a checkpoint transaction looks no different313 perspective, the checkpoint transaction is also no different - just a lot317 Because the checkpoint is just another transaction and all the changes to log320 minimise the time we hold the CIL locked while writing the checkpoint324 per-checkpoint context that travels through the log write process through to325 checkpoint completion.327 Hence a checkpoint has a context that tracks the state of the current328 checkpoint from initiation to checkpoint completion. A new context is initiated329 at the same time a checkpoint transaction is started. That is, when we remove[all …]
61 cp=n Specify the checkpoint-number of the snapshot to be68 checkpoint if no metadata update is going. This mode100 NILFS_IOCTL_CHANGE_CPMODE Change mode of given checkpoint between101 checkpoint and snapshot state. This ioctl is104 NILFS_IOCTL_DELETE_CHECKPOINT Remove checkpoint from NILFS2 file system.143 NILFS_IOCTL_SYNC Make a checkpoint. This ioctl is used in170 mkcp make a checkpoint or a snapshot.171 chcp change an existing checkpoint to a snapshot or vice versa.172 rmcp invalidate specified checkpoint(s).179 where <cno> is the checkpoint number of the snapshot.[all …]
52 the upper index structures such as inode, inode map, and checkpoint block are162 data_flush Enable data flushing before checkpoint in order to234 checkpoint=%s[:%u[%]] Set to "disable" to turn off checkpointing. Set to "enable"239 While mounting with checkpoint=disabled, the filesystem must246 with checkpoint=disable:100% would always succeed, but it may249 This space is reclaimed once checkpoint=enable.429 | Superblock | Checkpoint | Info. | Address | Summary | Main |449 - Checkpoint (CP)480 mount time, F2FS first tries to find the last valid checkpoint data by scanning
3 * cpfile.c - NILFS checkpoint file.147 * @start_cno: start checkpoint number (inclusive)148 * @end_cno: end checkpoint number (inclusive)149 * @cnop: place to store the next checkpoint number190 * nilfs_cpfile_get_checkpoint - get a checkpoint191 * @cpfile: inode of checkpoint file192 * @cno: checkpoint number194 * @cpp: pointer to a checkpoint197 * Description: nilfs_cpfile_get_checkpoint() acquires the checkpoint198 * specified by @cno. A new checkpoint will be created if @cno is the current[all …]
53 * @ns_cno: next checkpoint number60 * @ns_last_cno: checkpoint number of the latest segment66 * @ns_cpfile: checkpoint file inode78 * @ns_interval: checkpoint creation interval105 * - loading the latest checkpoint exclusively.152 /* Checkpoint tree */227 * @cno: checkpoint number253 /* Special checkpoint number */
25 * @ri_ri_cno: Number of the last checkpoint101 * @sc_cno: checkpoint number of current log185 * checkpoint188 * Next checkpoint will have update of files
184 * nilfs_ioctl_change_cpmode - change checkpoint mode (checkpoint/snapshot)191 * given checkpoint between checkpoint and snapshot state. This ioctl194 * Return Value: On success, 0 is returned and mode of a checkpoint is200 * %-EFAULT - Failure during checkpoint mode changing.238 * nilfs_ioctl_delete_checkpoint - remove checkpoint245 * checkpoint from NILFS2 file system. This ioctl is used in rmcp248 * Return Value: On success, 0 is returned and a checkpoint is254 * %-EFAULT - Failure during checkpoint removing.290 * @posp: pointer on array of checkpoint's numbers291 * @flags: checkpoint mode (checkpoint or snapshot)[all …]
322 * the same checkpoint. in nilfs_cleanup_super()524 goto reuse; /* already attached checkpoint */ in nilfs_attach_checkpoint()533 "Invalid checkpoint (checkpoint number=%llu)", in nilfs_attach_checkpoint()960 "The specified checkpoint is not a snapshot (checkpoint number=%llu)", in nilfs_attach_snapshot()969 "error %d while loading snapshot (checkpoint number=%llu)", in nilfs_attach_snapshot()981 * nilfs_tree_is_busy() - try to shrink dentries of a checkpoint1066 "error %d while loading last checkpoint (checkpoint number=%llu)", in nilfs_fill_super()1209 msg = "too large checkpoint number"; in nilfs_parse_snapshot_option()1214 msg = "invalid checkpoint number 0"; in nilfs_parse_snapshot_option()
11 * @cno: checkpoint number
3 * linux/fs/jbd2/checkpoint.c9 * Checkpoint routines for the generic filesystem journaling code.26 * Unlink a buffer from a transaction checkpoint list.44 * Unlink a buffer from a transaction checkpoint(io) list.61 * Move a buffer from the checkpoint list to the checkpoint io list96 JBUFFER_TRACE(jh, "remove from checkpoint list"); in __try_to_free_cp_buf()106 * for a checkpoint to free up some space in the log.122 * were waiting for the checkpoint lock. If there are no in __jbd2_log_wait_for_space()199 * Perform an actual checkpoint. We take the first transaction on the214 jbd_debug(1, "Start checkpoint\n"); in jbd2_log_do_checkpoint()[all …]
8 jbd2-objs := transaction.o commit.o recovery.o checkpoint.o revoke.o journal.o
10 * Output commit property is commonly used by applications using checkpoint11 * based fault-tolerance to ensure that the checkpoint from which a system15 * wherein a VM is checkpointed, say every 50ms. The checkpoint is replicated22 * 2.1 Stop VM and take checkpoint(i).25 * checkpoint(i) to backup host.76 * issued after committing a checkpoint at the target.82 * be released (committed checkpoint).
225 * passed to the iclog for checkpoint post-commit processing. After being227 * next set of transactions to be aggregated into a checkpoint.253 * This structure tracks the list of committing checkpoint contexts so255 * flush until we have a the commit record LSN of the checkpoint. We can258 * checkpoint is still in the process of committing, we can block waiting for285 * track both space consumed and the number of vectors in the checkpoint296 * logged in order to prevent checkpoint ticket overruns.307 * space needed by the checkpoint transaction. This means that we never need to308 * specifically reserve space for the CIL checkpoint transaction, nor do we309 * need to regrant space once the checkpoint completes. This also means the[all …]
53 * initialise the first CIL checkpoint context.262 * tell in future commits whether this is the first checkpoint in xfs_cil_prepare_item()380 * consumed by the item. Add the space to the checkpoint ticket and calculate382 * as well. Remove the amount of space we added to the checkpoint ticket from401 * We can do this safely because the context can't checkpoint until we in xlog_cil_insert_items()419 * for the checkpoint. The context ticket is special - the unit in xlog_cil_insert_items()763 * For example, if we get an EFI in one checkpoint and the EFD in the in xlog_cil_push_work()764 * next (e.g. due to log forces), we do not want the checkpoint with in xlog_cil_push_work()765 * the EFD to be committed before the checkpoint with the EFI. Hence in xlog_cil_push_work()767 * that: a) the checkpoint callbacks are attached to the iclogs in the in xlog_cil_push_work()[all …]
37 over total volume size, f2fs tries to conduct checkpoint to99 checkpoint is triggered, and issued during the checkpoint.156 Description: Controls the checkpoint timing, set to 60 seconds by default.195 ratio exceeds configured threshold, checkpoint will277 Description: If checkpoint=disable, it displays the number of blocks that279 If checkpoint=enable it displays the enumber of blocks that280 would be unusable if checkpoint=disable were to be set.296 Description: Number of checkpoint operations performed on demand. Available when302 Description: Number of checkpoint operations performed in the background to
109 Show checkpoint number of the latest segment.141 Show next checkpoint number.230 Show checkpoint number of the latest segment.236 Show next checkpoint number.
29 * written to the checkpoint as is, so changing this structure will30 * break checkpoint compatibility.
20 /* Used to determine what checkpoint state to get and set. */91 /* VMCICptBufInfo: Used to set/get current context's checkpoint state. */
3 * fs/f2fs/checkpoint.c911 /* The second checkpoint pack should start at the next segment */ in f2fs_get_valid_checkpoint()938 /* Sanity checking of checkpoint */ in f2fs_get_valid_checkpoint()1166 * Freeze all the FS-operations for checkpoint.1249 * dirty node blocks and some checkpoint values by block allocation. in block_operations()1384 /* submit checkpoint (with barrier if NOBARRIER is not set) */ in commit_checkpoint()1406 /* start to update checkpoint, cp ver is already updated previously */ in do_checkpoint()1448 /* update ckpt flag for checkpoint */ in do_checkpoint()1476 /* write out checkpoint buffer at block 0 */ in do_checkpoint()1520 /* barrier and flush checkpoint cp pack 2 page if it can */ in do_checkpoint()[all …]
5 f2fs-y += checkpoint.o gc.o data.o node.o segment.o recovery.o
89 __le32 segment_count_ckpt; /* # of segments for checkpoint */95 __le32 cp_blkaddr; /* start block address of checkpoint */123 * For checkpoint141 #define F2FS_CP_PACKS 2 /* # of checkpoint packs */144 __le64 checkpoint_ver; /* checkpoint block version number */174 #define CP_CHKSUM_OFFSET 4092 /* default chksum offset in checkpoint */306 __le64 cp_ver; /* checkpoint version */
170 __u32 cp_events_hi; /* 9 high-order of checkpoint update count */171 __u32 cp_events_lo; /* 10 low-order of checkpoint update count */175 __u32 cp_events_lo; /* 9 low-order of checkpoint update count */176 __u32 cp_events_hi; /* 10 high-order of checkpoint update count */180 __u32 recovery_cp; /* 11 recovery checkpoint sector count */
35 checkpoint section in Messages78 - Send a checkpoint message to the era target