mirror of
https://github.com/linux-apfs/apfstests.git
synced 2026-05-01 15:01:44 -07:00
ext4: use mkfs.ext4 -F instead of piping in yes
Using "yes | mkfs.ext4 ..." results in the error message results in
the test failing, at least for some versions of e2fsprogs:
+yes: standard output: Broken pipe
+yes: write error
It better to use the -F option, which will eliminate the questions.
Signed-off-by: Theodore Ts'o <tytso@mit.edu>
Reviewed-by: Eryu Guan <eguan@redhat.com>
Signed-off-by: Dave Chinner <david@fromorbit.com>
This commit is contained in:
committed by
Dave Chinner
parent
4e2fa4d0db
commit
c50db10dfb
+1
-1
@@ -43,7 +43,7 @@ _require_ext4_bigalloc
|
||||
|
||||
rm -f $seqres.full
|
||||
|
||||
yes | $MKFS_EXT4_PROG -O bigalloc -C 65536 -g 256 $SCRATCH_DEV 512m \
|
||||
$MKFS_EXT4_PROG -F -O bigalloc -C 65536 -g 256 $SCRATCH_DEV 512m \
|
||||
>> $seqres.full 2>&1
|
||||
_scratch_mount || _fail "couldn't mount fs"
|
||||
|
||||
|
||||
+1
-1
@@ -48,7 +48,7 @@ _require_scratch
|
||||
rm -f $seqres.full
|
||||
|
||||
# Make a small ext4 fs with extents disabled & mount it
|
||||
yes | $MKFS_EXT4_PROG -O ^extents,^64bit $SCRATCH_DEV 512m >> $seqres.full 2>&1
|
||||
$MKFS_EXT4_PROG -F -O ^extents,^64bit $SCRATCH_DEV 512m >> $seqres.full 2>&1
|
||||
_scratch_mount || _fail "couldn't mount fs"
|
||||
|
||||
# Create a small non-extent-based file
|
||||
|
||||
Reference in New Issue
Block a user