Currently, systemd uses 90s as the default mount unit timeout,
in some cases, although it works well in 1st kernel, it's not
enough under kdump and results in mount timeout, further results
in kdump dumping failure.
We've met several such issues, we decided to enlarge this default
value a little for kdump.
We finalize "x-systemd.device-timeout=300" as the default timeout
to the mount options if there is no "x-systemd.device-timeout=X"
specified. It can be overridden by /etc/fstab mount options,etc,
so that users can specify other timeout values if they want to.
Note: this is different from rd.timeout which was introduced by
dracut initqueue.
Signed-off-by: Xunlei Pang <xlpang(a)redhat.com>
---
v1->v2:
-Use 300s other than 600s as the default value.
mkdumprd | 6 ++++++
1 file changed, 6 insertions(+)
diff --git a/mkdumprd b/mkdumprd
index d3ecbd6..29e51a9 100644
--- a/mkdumprd
+++ b/mkdumprd
@@ -104,6 +104,12 @@ to_mount() {
_options=$(echo $_options | sed 's/noauto//')
_options=${_options/#ro/rw} #mount fs target as rw in 2nd kernel
+ # kdump turns out to require longer default systemd mount timeout
+ # than 1st kernel(90s by default), we choose 300s for kdump.
+ if ! strstr $_options "x-systemd.device-timeout"; then
+ _options="$_options,x-systemd.device-timeout=300"
+ fi
+
_mntopts="$_target $_fstype $_options"
#for non-nfs _dev converting to use udev persistent name
if [ -b "$_source" ]; then
--
1.8.3.1
Show replies by date