/openbmc/openbmc/meta-openembedded/meta-python/recipes-extended/python-blivet/python3-blivet/ |
H A D | 0009-invoking-fsck-with-infinite-timeout.patch | 4 Subject: [PATCH 09/11] invoking fsck with infinite timeout 13 blivet/tasks/fsck.py | 2 +- 16 diff --git a/blivet/tasks/fsck.py b/blivet/tasks/fsck.py 18 --- a/blivet/tasks/fsck.py 19 +++ b/blivet/tasks/fsck.py
|
/openbmc/openbmc/meta-openembedded/meta-filesystems/recipes-utils/overlayfs/overlayfs-tools/ |
H A D | 0002-Change-program_name-to-have-const-attribute.patch | 14 fsck.c | 2 +- 31 diff --git a/fsck.c b/fsck.c 33 --- a/fsck.c 34 +++ b/fsck.c
|
/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" 25 FILES:${PN}-fsck = "${base_sbindir}/fsck.xfs"
|
/openbmc/linux/Documentation/admin-guide/device-mapper/ |
H A D | log-writes.rst | 80 For example say you want to fsck a file system after every 82 we're fsck'ing something reasonable, you would do something like 90 then replay from that point on doing the fsck check in the 141 --fsck "btrfsck /dev/sdb" --check fua 143 And that will replay the log until it sees a FUA request, run the fsck command 144 and if the fsck passes it will replay to the next FUA, until it is completed or 145 the fsck command exists abnormally.
|
/openbmc/openbmc/meta-phosphor/recipes-phosphor/initrdscripts/files/ |
H A D | obmc-init.sh | 206 fsckbase=/sbin/fsck. 207 fsck=$fsckbase$rwfst 371 fsck=$fsckbase$rwfst 414 if test -x "$rodir$fsck" 420 chroot $rodir "$fsck" $fsckopts "$rwdev" 432 echo "No '$fsck' in read only fs, skipping fsck."
|
/openbmc/openbmc/meta-hpe/meta-common/recipes-phosphor/initrdscripts/files/ |
H A D | gxp-obmc-init.sh | 216 fsckbase=/sbin/fsck. 217 fsck=$fsckbase$rwfst 359 fsck=$fsckbase$rwfst 402 if test -x "$rodir$fsck" 408 chroot $rodir "$fsck" $fsckopts "$rwdev" 420 echo "No '$fsck' in read only fs, skipping fsck."
|
/openbmc/openbmc/poky/meta/recipes-devtools/e2fsprogs/ |
H A D | e2fsprogs_1.47.1.bb | 41 rm -f ${D}${base_sbindir}/fsck 92 FILES:e2fsprogs-e2fsck = "${base_sbindir}/e2fsck ${base_sbindir}/fsck.ext*" 110 ALTERNATIVE:${PN}-doc = "fsck.8" 111 ALTERNATIVE_LINK_NAME[fsck.8] = "${mandir}/man8/fsck.8"
|
/openbmc/linux/Documentation/power/ |
H A D | tricks.rst | 14 * use ext2. At least it has working fsck. [If something seems to go 15 wrong, force fsck when you have a chance]
|
/openbmc/openbmc/poky/meta/recipes-core/busybox/files/ |
H A D | rcS.default | 18 # Whether to fsck root on boot 20 # Set FSCKFIX to "yes" if you want to add "-y" to the fsck at startup.
|
/openbmc/openbmc/poky/meta/recipes-core/sysvinit/sysvinit/ |
H A D | rcS-default | 18 # Whether to fsck root on boot 20 # Set FSCKFIX to "yes" if you want to add "-y" to the fsck at startup.
|
/openbmc/linux/Documentation/filesystems/ |
H A D | xfs-online-fsck-design.rst | 25 - To help kernel distributors understand exactly what the XFS online fsck 34 As the online fsck code is merged, the links in this document to topic branches 41 Part 1 defines what fsck tools are and the motivations for writing a new one. 42 Parts 2 and 3 present a high level overview of how online fsck process works 49 might be built atop online fsck. 76 The filesystem check (fsck) tool examines all the metadata in a filesystem 78 In addition to looking for obvious metadata corruptions, fsck also 81 People do not like losing data, so most fsck tools also contains some ability 83 As a word of caution -- the primary goal of most Linux fsck tools is to restore 89 format, which means that fsck can only respond to errors by erasing files until [all …]
|
H A D | index.rst | 127 xfs-online-fsck-design
|
/openbmc/openbmc/poky/meta/recipes-core/initscripts/initscripts-1.0/ |
H A D | checkfs.sh | 40 fsck $spinner -R -A $fix $force
|
H A D | checkroot.sh | 109 fsck $spinner $force $fix /
|
/openbmc/linux/Documentation/filesystems/ext4/ |
H A D | mmp.rst | 8 simultaneously. When a filesystem is opened (for mounting, or fsck, 12 fsck is (hopefully) running, and open fails immediately. Otherwise, the
|
/openbmc/linux/Documentation/watchdog/ |
H A D | pcwd-watchdog.rst | 27 I suggest putting a "watchdog -d" before the beginning of an fsck, and 28 a "watchdog -e -t 1" immediately after the end of an fsck. (Remember
|
/openbmc/openbmc/poky/meta/recipes-core/util-linux/ |
H A D | util-linux_2.40.2.bb | 70 --enable-fsck --enable-kill --enable-last --enable-mesg \ 183 …sbinprogs_a="pivot_root hwclock mkswap losetup swapon swapoff fdisk fsck blkid blockdev fstrim sul… 262 ALTERNATIVE_LINK_NAME[fsck] = "${base_sbindir}/fsck" 311 blkid.8 eject.1 findfs.8 fsck.8 kill.1 last.1 lastb.1 libblkid.3 logger.1 mesg.1 \ 322 ALTERNATIVE_LINK_NAME[fsck.8] = "${mandir}/man8/fsck.8"
|
/openbmc/phosphor-bmc-code-mgmt/bmc/mmc/ |
H A D | obmc-flash-mmc-mount.service.in | 11 ExecStart=-/sbin/fsck.ext4 -p /dev/disk/by-partlabel/hostfw
|
/openbmc/openbmc/meta-openembedded/meta-python/recipes-extended/python-blivet/ |
H A D | python3-blivet_3.9.2.bb | 15 file://0009-invoking-fsck-with-infinite-timeout.patch \
|
/openbmc/openbmc/meta-openembedded/meta-filesystems/recipes-filesystems/logfsprogs/logfsprogs/ |
H A D | 0001-Add-LDFLAGS-to-linker-cmdline.patch | 43 logfsck: fsck.o lib.o journal.o super.o
|
/openbmc/openbmc/meta-security/recipes-security/cryptmount/ |
H A D | cryptmount_6.2.0.bb | 11 EXTRA_OECONF = " --enable-cswap --enable-fsck --enable-argv0switch"
|
/openbmc/openbmc/meta-openembedded/meta-filesystems/recipes-filesystems/logfsprogs/ |
H A D | logfsprogs_git.bb | 11 LIC_FILES_CHKSUM = "file://fsck.c;md5=3859dc73da97909ff1d0125e88a27e02"
|
/openbmc/openbmc/meta-phosphor/recipes-phosphor/initrdscripts/phosphor-mmc-init/ |
H A D | mmc-init.sh | 101 fsck.ext4 -p "${rwfsdev}"
|
/openbmc/openbmc/meta-security/recipes-ids/tripwire/files/ |
H A D | twpol-yocto.txt | 205 /sbin/fsck -> $(SEC_CRIT) ; 206 /sbin/fsck.ext2 -> $(SEC_CRIT) ; 207 /sbin/fsck.ext3 -> $(SEC_CRIT) ; 208 /sbin/fsck.minix -> $(SEC_CRIT) ; 209 /sbin/fsck.msdos -> $(SEC_CRIT) ; 210 /sbin/fsck.vfat -> $(SEC_CRIT) ; 633 /sbin/fsck.reiserfs -> $(SEC_CRIT) ;
|
/openbmc/linux/fs/reiserfs/ |
H A D | README | 54 it is for users to get their fsck and mkreiserfs out of sync with the 57 recompile and reinstall fsck and mkreiserfs with every update of 146 Vitaly Fertman is doing fsck.
|