/openbmc/linux/fs/xfs/scrub/ |
H A D | scrub.c | 212 .repair = xrep_probe, 218 .repair = xrep_superblock, 224 .repair = xrep_agf, 230 .repair = xrep_agfl, 236 .repair = xrep_agi, 242 .repair = xrep_notsupported, 248 .repair = xrep_notsupported, 254 .repair = xrep_notsupported, 261 .repair = xrep_notsupported, 268 .repair = xrep_notsupported, [all …]
|
H A D | scrub.h | 43 int (*repair)(struct xfs_scrub *); member
|
H A D | repair.c | 55 ASSERT(sc->ops->repair); in xrep_attempt() 58 error = sc->ops->repair(sc); in xrep_attempt()
|
/openbmc/linux/Documentation/filesystems/ |
H A D | xfs-online-fsck-design.rst | 47 then present case studies of how each repair function actually works. 109 `kernel changes <https://git.kernel.org/pub/scm/linux/kernel/git/djwong/xfs-linux.git/log/?h=repair… 111 …ges <https://git.kernel.org/pub/scm/linux/kernel/git/djwong/xfstests-dev.git/log/?h=repair-dirs>`_. 112 Each kernel patchset adding an online repair function will use the same branch 119 XFS (on Linux) to check and repair filesystems. 125 metadata, though it lacks any ability to repair what it finds. 126 Due to its high memory requirements and inability to repair things, this 176 metadata, an in-kernel facility to repair metadata, and a userspace driver 192 | "online repair". | 209 metadata to enable targeted checking and repair operations while the system [all …]
|
H A D | btrfs.rst | 8 features while focusing on fault tolerance, repair and easy administration.
|
H A D | gfs2.rst | 46 fsck.gfs2 to repair a filesystem
|
/openbmc/openbmc/meta-openembedded/meta-filesystems/recipes-utils/fatcat/ |
H A D | fatcat_1.1.1.bb | 1 SUMMARY = "FAT filesystems explore, extract, repair, and forensic tool" 3 explore, extract, repair, recover and forensic them. It currently supports \
|
/openbmc/openbmc/meta-openembedded/meta-filesystems/recipes-utils/xfsprogs/ |
H A D | xfsprogs_6.6.0.bb | 19 PACKAGES =+ "${PN}-fsck ${PN}-mkfs ${PN}-repair libhandle" 23 RDEPENDS:${PN} = "${PN}-fsck ${PN}-mkfs ${PN}-repair" 27 FILES:${PN}-repair = "${base_sbindir}/xfs_repair"
|
/openbmc/linux/tools/testing/selftests/bpf/prog_tests/ |
H A D | sockmap_basic.c | 32 int s, repair, err; in connected_socket_v4() local 38 repair = TCP_REPAIR_ON; in connected_socket_v4() 39 err = setsockopt(s, SOL_TCP, TCP_REPAIR, &repair, sizeof(repair)); in connected_socket_v4() 47 repair = TCP_REPAIR_OFF_NO_WP; in connected_socket_v4() 48 err = setsockopt(s, SOL_TCP, TCP_REPAIR, &repair, sizeof(repair)); in connected_socket_v4()
|
/openbmc/linux/drivers/ras/ |
H A D | Kconfig | 13 enhanced by features that help to avoid, detect and repair hardware 21 which a system can be repaired or maintained; if the time to repair
|
/openbmc/qemu/tests/qemu-iotests/tests/ |
H A D | parallels-checks.out | 21 == repair image == 49 == repair image == 88 == check the first cluster with self-repair == 120 == repair image ==
|
/openbmc/openbmc/meta-openembedded/meta-oe/dynamic-layers/meta-python/recipes-connectivity/lirc/lirc/ |
H A D | 0001-Unbolt-ubuntu-hack.patch | 21 dnl Ubuntu's systemd pkg-config seems broken beyond repair. So:
|
/openbmc/qemu/tests/qemu-iotests/ |
H A D | 039.out | 41 == Data should still be accessible after repair == 45 == Opening a dirty image read/write should repair it ==
|
/openbmc/linux/net/ipv4/ |
H A D | tcp.c | 1076 !tp->repair) { in tcp_sendmsg_locked() 1099 if (unlikely(tp->repair)) { in tcp_sendmsg_locked() 1171 if (tp->repair) in tcp_sendmsg_locked() 1285 if (skb->len < size_goal || (flags & MSG_OOB) || unlikely(tp->repair)) in tcp_sendmsg_locked() 2370 if (unlikely(tp->repair)) { in tcp_recvmsg_locked() 2828 if (unlikely(tcp_sk(sk)->repair)) { in __tcp_close() 3022 } else if (unlikely(tp->repair)) { in tcp_disconnect() 3150 if (!tp->repair) in tcp_repair_set_window() 3575 tp->repair = 1; in do_tcp_setsockopt() 3579 tp->repair = 0; in do_tcp_setsockopt() [all …]
|
/openbmc/openbmc/meta-openembedded/meta-oe/recipes-support/monit/ |
H A D | monit_5.34.4.bb | 3 Monit conducts automatic maintenance and repair and can execute meaningful \
|
/openbmc/openbmc/meta-openembedded/meta-filesystems/recipes-utils/xfsprogs/files/ |
H A D | 0005-Replace-off64_t-stat64-with-off_t-stat.patch | 38 repair/prefetch.c | 2 +- 658 diff --git a/repair/prefetch.c b/repair/prefetch.c 660 --- a/repair/prefetch.c 661 +++ b/repair/prefetch.c
|
/openbmc/openbmc/poky/meta/files/common-licenses/ |
H A D | Bahyph | 7 …ility of such damages. If any such situation arises, you responsible for repair. Use of this softw…
|
H A D | SAX-PD | 10 …. Should SAX prove defective, you assume the cost of all necessary servicing, repair or correction.
|
/openbmc/qemu/block/ |
H A D | qcow2-snapshot.c | 81 int qcow2_do_read_snapshots(BlockDriverState *bs, bool repair, in qcow2_do_read_snapshots() argument 132 if (!repair) { in qcow2_do_read_snapshots() 221 if (!repair) { in qcow2_do_read_snapshots() 228 if (!repair) { in qcow2_do_read_snapshots()
|
/openbmc/linux/Documentation/admin-guide/device-mapper/ |
H A D | thin-provisioning.rst | 144 until the pool is taken offline and repair is performed to 1) fix any 145 potential inconsistencies and 2) clear the flag that imposes repair. 148 is flagged as needing repair, the pool's data and metadata devices 149 cannot be resized until repair is performed. It should also be noted 154 (e.g. fsck) be performed on those layers when repair of the pool is
|
H A D | dm-raid.rst | 287 'sync_action' is "check" or "repair", then the process 309 repair 340 "repair" Initiate a repair of the array.
|
/openbmc/openbmc/poky/meta/recipes-devtools/btrfs-tools/ |
H A D | btrfs-tools_6.12.bb | 3 implementing advanced features while focusing on fault tolerance, repair and \
|
/openbmc/openbmc/meta-openembedded/meta-oe/recipes-support/lvm2/ |
H A D | lvm2.inc | 58 --with-thin-repair=${sbindir}/thin_repair \
|
/openbmc/linux/fs/xfs/ |
H A D | Makefile | 185 repair.o \
|
/openbmc/docs/designs/ |
H A D | hw-fault-monitor.md | 24 criteria trigger repair actions in the host BIOS or kernel. In addition, the 25 hardware fault monitor could receive repair action requests via Redfish from 165 of any repair actions that need to be triggered based on the latest fault
|