aboutsummaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorDenis 'GNUtoo' Carikli <GNUtoo@cyberdimension.org>2021-10-08 17:38:38 +0200
committerDenis 'GNUtoo' Carikli <GNUtoo@cyberdimension.org>2021-10-08 17:40:01 +0200
commitde2c1f0a761aa60751ffc047ecb4f31695cc8c9d (patch)
tree924527302f5c10ec643b8b83ae6ec6afc11077cf
parent92b01f201e923c912c240c08637286131b0d229d (diff)
downloaddevice_samsung_i9100-de2c1f0a761aa60751ffc047ecb4f31695cc8c9d.tar.gz
device_samsung_i9100-de2c1f0a761aa60751ffc047ecb4f31695cc8c9d.tar.bz2
device_samsung_i9100-de2c1f0a761aa60751ffc047ecb4f31695cc8c9d.zip
Fix /cache mount
Without that fix, on a GT-I9300, the mount fails and we have the following in dmesg: EXT4-fs (mmcblk2p8): can't mount with journal_async_commit in data=ordered mode So we are likely to have exactly the same issue on the GT-I9305 as the /data entry in the fstab is the same. Signed-off-by: Denis 'GNUtoo' Carikli <GNUtoo@cyberdimension.org>
-rw-r--r--fstab.smdk4x122
1 files changed, 1 insertions, 1 deletions
diff --git a/fstab.smdk4x12 b/fstab.smdk4x12
index 122f752..0198384 100644
--- a/fstab.smdk4x12
+++ b/fstab.smdk4x12
@@ -15,7 +15,7 @@
#
/dev/block/platform/soc/12550000.mmc/by-name/SYSTEM / ext4 ro,noatime wait
-/dev/block/platform/soc/12550000.mmc/by-name/CACHE /cache ext4 rw,noatime,nosuid,nodev,journal_async_commit,errors=panic wait
+/dev/block/platform/soc/12550000.mmc/by-name/CACHE /cache ext4 rw,noatime,nosuid,nodev,errors=panic wait
/dev/block/platform/soc/12550000.mmc/by-name/USERDATA /data ext4 rw,noatime wait
# Recovery