Home
last modified time | relevance | path

Searched full:rebuild (Results 1 – 25 of 184) sorted by relevance

12345678

/kernel/linux/linux-5.10/scripts/
Dadjust_autoksyms.sh13 # file's timestamp is updated to force a rebuild of the affected source
15 # to be exec'd to trigger a rebuild of those files.
56 # needs to be rebuild. Let's guard against that by making sure our
72 # Then trigger a rebuild of affected source files
/kernel/linux/linux-5.10/tools/power/pm-graph/
Dbootgraph.8103 .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.
Dsleepgraph.8248 .SS "rebuild"
329 .SS "rebuild timeline from logs"
331 Rebuild the html from a previous run's logs, using the same options.
335 Rebuild the html with different options.
/kernel/linux/linux-5.10/fs/hmdfs/
Dhmdfs_dentryfile.h92 * need to rebuild.
95 * rebuild at the same time of the dentry inode ctime, maybe
98 * dcache rebuild may only has 1.jpg 2.jpg
102 /* The time of dcache rebuild */
106 /* The directory inode ctime when dcache rebuild */
/kernel/linux/linux-5.10/arch/x86/kernel/
Ditmt.c103 * held as we need to acquire the lock to rebuild sched domains
142 * held as we need to acquire the lock to rebuild sched domains
185 * No need to rebuild sched domain after updating
/kernel/linux/linux-5.10/arch/arm/boot/dts/
Dkirkwood-iomega_ix2_200.dts55 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 {
/kernel/linux/linux-5.10/drivers/scsi/
Dmyrs.c36 { MYRS_DEVICE_REBUILD, "Rebuild" },
695 { 0x0005, "P Automatic Rebuild Started" },
696 { 0x0006, "P Manual Rebuild Started" },
697 { 0x0007, "P Rebuild Completed" },
698 { 0x0008, "P Rebuild Cancelled" },
699 { 0x0009, "P Rebuild Failed for Unknown Reasons" },
700 { 0x000A, "P Rebuild Failed due to New Physical Device" },
701 { 0x000B, "P Rebuild Failed due to Logical Drive Failure" },
741 { 0x003A, "P Start Rebuild Failed due to Physical Drive Too Small" },
743 { 0x003D, "P Standby Rebuild Started" },
[all …]
D3w-xxxx.h66 [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 #",
Dmyrb.c432 * myrb_get_rbld_progress - get rebuild progress information
434 * Executes a type 3 command and returns the rebuild progress
467 * myrb_update_rbld_progress - updates the rebuild status
469 * Updates the rebuild status for the attached logical devices.
495 "Rebuild in Progress, %d%% completed\n", in myrb_update_rbld_progress()
501 "Rebuild Failed due to Logical Drive Failure\n"); in myrb_update_rbld_progress()
505 "Rebuild Failed due to Bad Blocks on Other Drives\n"); in myrb_update_rbld_progress()
509 "Rebuild Failed due to Failure of Drive Being Rebuilt\n"); in myrb_update_rbld_progress()
513 "Rebuild Completed Successfully\n"); in myrb_update_rbld_progress()
517 "Rebuild Successfully Terminated\n"); in myrb_update_rbld_progress()
[all …]
D3w-9xxx.h62 {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"},
/kernel/liteos_a/apps/mksh/
DMakefile41 ifneq ($(wildcard $(BUILD_DIR)/Rebuild.sh),)
43 $(HIDE)cd $(BUILD_DIR) && sh ./Rebuild.sh > $(BUILD_LOG) 2>&1
/kernel/linux/linux-5.10/tools/perf/util/
Dtrace-event-scripting.c39 " Install libpython and rebuild perf to enable it.\n" in print_python_unsupported_msg()
103 " Install libperl and rebuild perf to enable it.\n" in print_perl_unsupported_msg()
/kernel/linux/linux-5.10/Documentation/admin-guide/device-mapper/
Ddm-raid.rst90 [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)
/kernel/linux/linux-5.10/fs/hmdfs/comm/
Ddevice_node.c1185 rebuild_ok += node->stats.rebuild.total_ok; in peers_sum_attr_show()
1186 rebuild_fail += node->stats.rebuild.total_fail; in peers_sum_attr_show()
1187 rebuild_invalid += node->stats.rebuild.total_invalid; in peers_sum_attr_show()
1188 rebuild_time += node->stats.rebuild.time; in peers_sum_attr_show()
1590 peer->stats.rebuild.cur_ok, in rebuild_show()
1591 peer->stats.rebuild.cur_fail, in rebuild_show()
1592 peer->stats.rebuild.cur_invalid, in rebuild_show()
1593 peer->stats.rebuild.total_ok, in rebuild_show()
1594 peer->stats.rebuild.total_fail, in rebuild_show()
1595 peer->stats.rebuild.total_invalid, in rebuild_show()
[all …]
Dconnection.h136 /* rebuild statistics */
137 struct hmdfs_rebuild_statistics rebuild; member
/kernel/linux/linux-5.10/scripts/basic/
Dfixdep.c22 * 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
/kernel/linux/linux-5.10/fs/xfs/scrub/
Drepair.c154 * Does the given AG have enough space to rebuild a btree? Neither AG
171 * worst case estimate for the number of blocks we'd need to rebuild one of
242 * Figure out how many blocks we'd need worst case to rebuild in xrep_calc_ag_resblks()
243 * each type of btree. Note that we can only rebuild the in xrep_calc_ag_resblks()
261 * Guess how many blocks we need to rebuild the rmapbt. in xrep_calc_ag_resblks()
420 * the btree we're trying to rebuild and the block is indeed owned by another
426 * The caller is responsible for locking the AG headers for the entire rebuild
629 * If the AGF or AGI become slightly corrupted, it may be necessary to rebuild
/kernel/linux/linux-5.10/drivers/md/
Ddm-raid.c216 /* Array elements of 64 bit needed for rebuild/failed disk bits */
327 { CTR_FLAG_REBUILD, "rebuild"},
823 int rebuild = 0; in parse_dev_params() local
873 rs->ti->error = "Drive designated for rebuild not specified"; in parse_dev_params()
899 rebuild++; in parse_dev_params()
909 } else if (rebuild && !rs->md.recovery_cp) { in parse_dev_params()
913 * it is impossible to rebuild a drive. in parse_dev_params()
921 rs->ti->error = "Unable to rebuild drive while array is not in-sync"; in parse_dev_params()
1038 * It is possible to have a higher rebuild count for RAID10, in validate_raid_redundancy()
1108 * [rebuild <idx>] Rebuild the drive indicated by the index
[all …]
/kernel/linux/linux-5.10/kernel/bpf/preload/iterators/
DREADME2 If you change "iterators.bpf.c" do "make -j" in this directory to rebuild "iterators.skel.h".
/kernel/linux/linux-5.10/arch/powerpc/kernel/
Dcacheinfo.h9 /* Allow migration/suspend to tear down and rebuild the hierarchy. */
/kernel/linux/linux-5.10/lib/raid6/
Drecov.c118 /* P+Q failure. Just rebuild the syndrome. */ in raid6_dual_recov()
122 then rebuild syndrome. */ in raid6_dual_recov()
/kernel/linux/linux-5.10/arch/nds32/kernel/vdso/
Dgen_vdso_offsets.sh8 # causing Kbuild to rebuild the vdso-offsets header file every time.
/kernel/linux/linux-5.10/arch/arm64/kernel/vdso/
Dgen_vdso_offsets.sh9 # causing Kbuild to rebuild the vdso-offsets header file every time.
/kernel/linux/linux-5.10/Documentation/driver-api/firmware/
Dbuilt-in-fw.rst27 a complete kernel rebuild.
/kernel/linux/linux-5.10/Documentation/networking/device_drivers/atm/
Diphase.rst60 3. Rebuild kernel with ABR support
66 d. Rebuild the kernel, loadable modules and the atm tools.

12345678