| /linux/tools/power/pm-graph/ |
| H A D | bootgraph.8 | 103 .SS "rebuild"
158 .SS "rebuild timeline from logs"
160 Rebuild the html from a previous run's logs, using the same options.
164 Rebuild the html with different options.
|
| /linux/drivers/md/dm-vdo/indexer/ |
| H A D | index-session.h | 59 /* The index is attempting to suspend a rebuild. */
61 /* An index rebuild has been suspended. */
63 /* An index rebuild is being stopped in order to shut down. */
|
| H A D | index-session.c | 26 * a rebuild. Depending on the size of the index, a rebuild may take a significant amount of time,
27 * so UDS allows the rebuild to be paused in order to suspend the session in a timely manner. When
28 * the index session is resumed, the rebuild can continue from where it left off. If the index
29 * session is shut down with a suspended rebuild, the rebuild progress is abandoned and the rebuild
31 * the index_load_context are used to record the state of any interrupted rebuild.
522 /* There is no index rebuild to resume. */ in uds_resume_index_session()
650 /* Tell the index to terminate the rebuild. */ in uds_destroy_index_session()
|
| /linux/arch/arm/boot/dts/marvell/ |
| H A D | kirkwood-iomega_ix2_200.dts | 55 pmx_led_rebuild: pmx-led-rebuild {
95 pmx_led_rebuild_brt_ctrl_1: pmx-led-rebuild-brt-ctrl-1 {
99 pmx_led_rebuild_brt_ctrl_2: pmx-led-rebuild-brt-ctrl-2 {
135 led-rebuild-led {
|
| /linux/kernel/bpf/preload/iterators/ |
| H A D | README | 3 rebuild "iterators.lskel-little-endian.h". Then, on a big-endian
4 machine, do "make -j big" in this directory to rebuild
|
| /linux/arch/x86/kernel/ |
| H A D | itmt.c | 96 * held as we need to acquire the lock to rebuild sched domains
143 * held as we need to acquire the lock to rebuild sched domains
183 * No need to rebuild sched domain after updating
|
| /linux/drivers/md/dm-vdo/ |
| H A D | repair.c | 77 * The highest sequence number of the journal. During recovery (vs read-only rebuild), not
119 /* These fields are only used during read-only rebuild */
128 * read-only rebuild, for rebuilding the reference counts from the block map.
269 vdo_log_info("Read-only rebuild complete"); in finish_repair()
275 vdo_log_info("Rebuild complete"); in finish_repair()
295 vdo_log_info("Read-only rebuild aborted"); in abort_repair()
463 * rebuild_reference_counts_from_page() - Rebuild reference counts from a block map page.
539 * Return true if the rebuild is complete
566 * rebuild_from_leaves() - Rebuild reference counts from the leaf block map pages.
596 * The rebuild has already moved on, so it isn't safe nor is there a need in rebuild_from_leaves()
[all …]
|
| /linux/drivers/scsi/ |
| H A D | 3w-xxxx.h | 66 [0x004] = "ERROR: Rebuild failed: Unit #",
67 [0x005] = "INFO: Rebuild complete: Unit #",
73 [0x00B] = "INFO: Rebuild started: Unit #",
88 [0x02C] = "WARNING: Overwrote bad sector during rebuild: Port #",
89 [0x02D] = "ERROR: Encountered bad sector during rebuild: Port #",
|
| H A D | 3w-9xxx.h | 62 {0x0004, "Background rebuild failed"},
63 {0x0005, "Background rebuild done"},
69 {0x000B, "Rebuild started"},
100 {0x002C, "Bad sector overwritten during rebuild"},
101 {0x002D, "Background rebuild error on source drive"},
115 {0x003B, "Background rebuild paused"},
|
| /linux/tools/testing/selftests/net/rds/ |
| H A D | run.sh | 85 "\"tools/testing/selftests/net/rds/config.sh -g\" and rebuild the kernel"
97 echo "Please run tools/testing/selftests/net/rds/config.sh and rebuild the kernel"
104 echo "Please run tools/testing/selftests/net/rds/config.sh and rebuild the kernel"
|
| /linux/Documentation/admin-guide/device-mapper/ |
| H A D | dm-raid.rst | 90 [rebuild <idx>]
91 Rebuild drive number 'idx' (first drive is 0).
384 1.3.1 Allow device replacement/rebuild for RAID 10
418 specific devices are requested via rebuild. Fix RAID leg
419 rebuild errors.
422 1.15.1 Fix argument count and arguments for rebuild/write_mostly/journal_(dev|mode)
|
| /linux/fs/xfs/scrub/ |
| H A D | ialloc_repair.c | 74 * So what's the rebuild algorithm?
87 * btree roots and reload the btrees. We rebuild both inode trees at the same
89 * figure out if the other tree isn't in need of a rebuild and which OWN_INOBT
93 * We use the prefix 'xrep_ibt' because we rebuild both inode btrees at once.
804 /* We require the rmapbt to rebuild anything. */ in xrep_iallocbt()
813 /* We rebuild both inode btrees. */ in xrep_iallocbt()
833 /* Rebuild the inode indexes. */ in xrep_iallocbt()
|
| H A D | rtsummary_repair.c | 117 /* We require the rmapbt to rebuild anything. */ in xrep_rtsummary()
120 /* We require atomic file exchange range to rebuild anything. */ in xrep_rtsummary()
|
| H A D | repair.c | 260 * Does the given AG have enough space to rebuild a btree? Neither AG
277 * worst case estimate for the number of blocks we'd need to rebuild one of
347 * Figure out how many blocks we'd need worst case to rebuild in xrep_calc_ag_resblks()
348 * each type of btree. Note that we can only rebuild the in xrep_calc_ag_resblks()
366 * Guess how many blocks we need to rebuild the rmapbt. in xrep_calc_ag_resblks()
392 * the worst case estimate for the number of blocks we'd need to rebuild one of
470 * If the AGF or AGI become slightly corrupted, it may be necessary to rebuild
1108 /* Userspace asked us to rebuild the structure regardless. */ in xrep_will_attempt()
|
| /linux/drivers/md/ |
| H A D | dm-raid.c | 218 /* Array elements of 64 bit needed for rebuild/failed disk bits */
329 { CTR_FLAG_REBUILD, "rebuild"},
829 int rebuild = 0; in parse_dev_params() local
879 rs->ti->error = "Drive designated for rebuild not specified"; in parse_dev_params()
905 rebuild++; in parse_dev_params()
915 } else if (rebuild && !rs->md.resync_offset) { in parse_dev_params()
919 * it is impossible to rebuild a drive. in parse_dev_params()
927 rs->ti->error = "Unable to rebuild drive while array is not in-sync"; in parse_dev_params()
1044 * It is possible to have a higher rebuild count for RAID10, in validate_raid_redundancy()
1114 * [rebuild <idx>] Rebuild the drive indicated by the index
[all …]
|
| /linux/scripts/basic/ |
| H A D | fixdep.c | 22 * regenerated. make notices that and will rebuild every file which
43 * o if any of the files the compiler read changed, we need to rebuild
45 * better rebuild as well.
84 * we cannot miss a rebuild. Since people tend to not mention totally
|
| /linux/fs/btrfs/ |
| H A D | raid56.h | 62 * Set if we're doing a parity rebuild for a read from higher up, which
63 * is handled differently from a parity rebuild as part of RMW.
|
| /linux/lib/raid6/ |
| H A D | recov.c | 117 /* P+Q failure. Just rebuild the syndrome. */ in raid6_dual_recov()
121 then rebuild syndrome. */ in raid6_dual_recov()
|
| /linux/arch/powerpc/kernel/ |
| H A D | cacheinfo.h | 9 /* Allow migration/suspend to tear down and rebuild the hierarchy. */
|
| /linux/arch/parisc/kernel/vdso64/ |
| H A D | gen_vdso_offsets.sh | 9 # causing Kbuild to rebuild the vdso-offsets header file every time.
|
| /linux/arch/parisc/kernel/vdso32/ |
| H A D | gen_vdso_offsets.sh | 9 # causing Kbuild to rebuild the vdso-offsets header file every time.
|
| /linux/arch/s390/kernel/vdso32/ |
| H A D | gen_vdso_offsets.sh | 9 # causing Kbuild to rebuild the vdso-offsets header file every time.
|
| /linux/arch/s390/kernel/vdso64/ |
| H A D | gen_vdso_offsets.sh | 9 # causing Kbuild to rebuild the vdso-offsets header file every time.
|
| /linux/arch/powerpc/kernel/vdso/ |
| H A D | gen_vdso64_offsets.sh | 9 # causing Kbuild to rebuild the vdso-offsets header file every time.
|
| /linux/arch/arm64/kernel/vdso/ |
| H A D | gen_vdso_offsets.sh | 9 # causing Kbuild to rebuild the vdso-offsets header file every time.
|