| /Linux-v5.10/fs/xfs/scrub/ |
| D | scrub.c | 192 .repair = xrep_probe,
198 .repair = xrep_superblock,
204 .repair = xrep_agf,
210 .repair = xrep_agfl,
216 .repair = xrep_agi,
222 .repair = xrep_notsupported,
228 .repair = xrep_notsupported,
234 .repair = xrep_notsupported,
241 .repair = xrep_notsupported,
248 .repair = xrep_notsupported,
[all …]
|
| D | scrub.h | 28 int (*repair)(struct xfs_scrub *); member
|
| D | repair.c | 50 ASSERT(sc->ops->repair); in xrep_attempt()
51 error = sc->ops->repair(sc); in xrep_attempt()
|
| /Linux-v5.10/tools/testing/selftests/bpf/prog_tests/ |
| D | sockmap_basic.c | 24 int s, repair, err; in connected_socket_v4() local
30 repair = TCP_REPAIR_ON; in connected_socket_v4()
31 err = setsockopt(s, SOL_TCP, TCP_REPAIR, &repair, sizeof(repair)); in connected_socket_v4()
39 repair = TCP_REPAIR_OFF_NO_WP; in connected_socket_v4()
40 err = setsockopt(s, SOL_TCP, TCP_REPAIR, &repair, sizeof(repair)); in connected_socket_v4()
|
| /Linux-v5.10/drivers/ras/ |
| 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-v5.10/net/ipv4/ |
| D | tcp.c | 1217 !tp->repair) { in tcp_sendmsg_locked()
1240 if (unlikely(tp->repair)) { in tcp_sendmsg_locked()
1310 if (tp->repair) in tcp_sendmsg_locked()
1388 if (skb->len < size_goal || (flags & MSG_OOB) || unlikely(tp->repair)) in tcp_sendmsg_locked()
2052 if (unlikely(tp->repair)) { in tcp_recvmsg()
2452 if (unlikely(tcp_sk(sk)->repair)) { in tcp_close()
2645 } else if (unlikely(tp->repair)) { in tcp_disconnect()
2775 if (!tp->repair) in tcp_repair_set_window()
3141 tp->repair = 1; in do_tcp_setsockopt()
3145 tp->repair = 0; in do_tcp_setsockopt()
[all …]
|
| D | tcp_output.c | 2622 if (unlikely(tp->repair) && tp->repair_queue == TCP_SEND_QUEUE) { in tcp_write_xmit()
2627 goto repair; /* Skip network transmission */ in tcp_write_xmit()
2688 repair: in tcp_write_xmit()
3701 if (likely(!tp->repair)) in tcp_connect_init()
3834 if (unlikely(tp->repair)) { in tcp_connect()
|
| D | tcp_ipv4.c | 165 if (likely(!tp->repair)) { in tcp_twsk_unique()
256 if (likely(!tp->repair)) in tcp_v4_connect()
293 if (likely(!tp->repair)) { in tcp_v4_connect()
|
| /Linux-v5.10/Documentation/filesystems/ |
| D | btrfs.rst | 8 features while focusing on fault tolerance, repair and easy administration.
|
| D | gfs2.rst | 47 fsck.gfs2 to repair a filesystem
|
| D | ocfs2-online-filecheck.rst | 37 may end up with more damage than before the repair attempt. So, this has to
|
| 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
316 * repair
|
| D | xfs-self-describing-metadata.rst | 76 metadata object at runtime, during forensic analysis or repair.
352 repair will probably complain about it - but it needs to be fixed.
|
| D | affs.rst | 191 restore or repair your RDB. So please do make a backup copy of it
|
| /Linux-v5.10/fs/xfs/ |
| D | Makefile | 165 repair.o \
|
| D | Kconfig | 114 bool "XFS online metadata repair support"
118 If you say Y here you will be able to repair metadata on a
|
| /Linux-v5.10/Documentation/admin-guide/device-mapper/ |
| 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
|
| 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-v5.10/fs/btrfs/ |
| D | Kconfig | 25 features focused on fault tolerance, repair and easy administration.
|
| /Linux-v5.10/Documentation/admin-guide/ |
| 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-v5.10/include/linux/ |
| D | tcp.h | 240 repair : 1, member
|
| /Linux-v5.10/fs/reiserfs/ |
| D | README | 122 Igor Krasheninnikov was wonderful at hardware procurement, repair, and
|
| /Linux-v5.10/Documentation/ |
| D | Changes | 193 and repair a JFS formatted partition.
|
| /Linux-v5.10/Documentation/process/ |
| D | changes.rst | 193 and repair a JFS formatted partition.
|
| /Linux-v5.10/Documentation/driver-api/mtd/ |
| 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.
|
