/linux/fs/xfs/scrub/ |
H A D | scrub.c | 267 .repair = xrep_probe, 273 .repair = xrep_superblock, 279 .repair = xrep_agf, 285 .repair = xrep_agfl, 291 .repair = xrep_agi, 297 .repair = xrep_allocbt, 304 .repair = xrep_allocbt, 311 .repair = xrep_iallocbt, 319 .repair = xrep_iallocbt, 327 .repair = xrep_rmapbt, [all …]
|
H A D | scrub.h | 86 int (*repair)(struct xfs_scrub *); member
|
H A D | repair.c | 66 ASSERT(sc->ops->repair); in xrep_attempt() 69 error = sc->ops->repair(sc); in xrep_attempt() 1029 error = sub->sc.ops->repair(&sub->sc); in xrep_metadata_inode_subtype()
|
/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()
|
/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
|
/linux/tools/testing/selftests/net/tcp_ao/ |
H A D | Makefile | 35 LIBSRC += proc.c repair.c setup.c sock.c utils.c
|
/linux/drivers/md/dm-vdo/ |
H A D | Makefile | 33 repair.o \
|
/linux/Documentation/filesystems/ |
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
|
H A D | ocfs2-online-filecheck.rst | 37 may end up with more damage than before the repair attempt. So, this has to
|
H A D | zonefs.rst | 279 | repair | read-only | as is yes no yes no | 301 * The repair mount option triggers only the minimal set of I/O error recovery 323 * repair
|
H A D | affs.rst | 191 restore or repair your RDB. So please do make a backup copy of it
|
/linux/net/ipv4/ |
H A D | tcp.c | 1089 !tp->repair) { in tcp_sendmsg_locked() 1112 if (unlikely(tp->repair)) { in tcp_sendmsg_locked() 1184 if (tp->repair) in tcp_sendmsg_locked() 1298 if (skb->len < size_goal || (flags & MSG_OOB) || unlikely(tp->repair)) in tcp_sendmsg_locked() 2587 if (unlikely(tp->repair)) { in tcp_recvmsg_locked() 3087 if (unlikely(tcp_sk(sk)->repair)) { in __tcp_close() 3284 } else if (unlikely(tp->repair)) { in tcp_disconnect() 3416 if (!tp->repair) in tcp_repair_set_window() 3841 tp->repair = 1; in do_tcp_setsockopt() 3845 tp->repair = 0; in do_tcp_setsockopt() [all …]
|
H A D | tcp_output.c | 2762 if (unlikely(tp->repair) && tp->repair_queue == TCP_SEND_QUEUE) { in tcp_write_xmit() 2768 goto repair; /* Skip network transmission */ in tcp_write_xmit() 2830 repair: in tcp_write_xmit() 3936 if (likely(!tp->repair)) in tcp_connect_init() 4125 if (unlikely(tp->repair)) { in tcp_connect()
|
H A D | tcp_ipv4.c | 185 if (likely(!tp->repair)) { in tcp_twsk_unique() 284 if (likely(!tp->repair)) in tcp_v4_connect() 322 if (likely(!tp->repair)) { in tcp_v4_connect()
|
/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.
|
/linux/fs/btrfs/ |
H A D | Kconfig | 26 features focused on fault tolerance, repair and easy administration.
|
/linux/fs/xfs/ |
H A D | Makefile | 221 repair.o \
|
H A D | Kconfig | 176 bool "XFS online metadata repair support" 181 If you say Y here you will be able to repair metadata on a
|
/linux/Documentation/admin-guide/ |
H A D | md.rst | 634 them. A repair may also happen for some raid 637 repair 638 A full check and repair is happening. This is 654 ``check`` and ``repair`` will start the appropriate process 672 When performing ``check`` and ``repair``, and possibly when 724 within the array where ``check``/``repair`` will operate. Must be
|
/linux/Documentation/networking/net_cachelines/ |
H A D | tcp_sock.rst | 59 u8:1 repair read_mostly - tcp_w…
|
/linux/include/linux/ |
H A D | tcp.h | 226 repair : 1, member
|
/linux/Documentation/filesystems/xfs/ |
H A D | xfs-self-describing-metadata.rst | 77 metadata object at runtime, during forensic analysis or repair. 353 repair will probably complain about it - but it needs to be fixed.
|
/linux/Documentation/driver-api/mtd/ |
H A D | nand_ecc.rst | 736 introduced by this is about a factor 2 on my system when a repair had to 737 be done, and 1% or so if no repair had to be done.
|