Details
-
Bug
-
Resolution: Fixed
-
Critical
-
Lustre 2.10.0
-
None
-
Lustre: Build Version: 2.10.0_5_gbb3c407
-
3
-
9223372036854775807
Description
When mount -t lustre ... has failed to actually mount a target, the exit code of mount does not reflect this:
# mount -t lustre zfs_pool_scsi0QEMU_QEMU_HARDDISK_disk13/MGS /mnt/MGS e2label: No such file or directory while trying to open zfs_pool_scsi0QEMU_QEMU_HARDDISK_disk13/MGS Couldn't find valid filesystem superblock. # echo $? 0
This of course wreaks havoc on systems such as IML which rely on the exit code of one step in the process of starting a filesystem to decide if it should continue with subsequent steps.
Attachments
Issue Links
- is duplicated by
-
LU-9853 mount.lustre noisy on mount
-
- Resolved
-
Activity
Link | Original: This issue is related to JFC-21 [ JFC-21 ] |
Labels | Original: LTS |
Link | New: This issue is related to JFC-21 [ JFC-21 ] |
Fix Version/s | New: Lustre 2.10.1 [ 13090 ] |
Fix Version/s | New: Lustre 2.11.0 [ 13091 ] | |
Resolution | New: Fixed [ 1 ] | |
Status | Original: In Progress [ 3 ] | New: Resolved [ 5 ] |
Status | Original: Open [ 1 ] | New: In Progress [ 3 ] |
Labels | New: LTS |
Assignee | Original: WC Triage [ wc-triage ] | New: Nathaniel Clark [ utopiabound ] |
Comment |
[ Is the problem here that {{readcmd()}} in {{lustre/utils/mount_utils_ldiskfs.c}} is not analysing/propagating any failure exit code from {{cmd}} back up to the caller and so when the {{e2label}} given to {{readcmd()}} in the below code (from {{ldiskfs_read_ldd}}): {noformat} snprintf(cmd, sizeof(cmd), E2LABEL" %s", dev); ret = readcmd(cmd, mo_ldd->ldd_svname, sizeof(mo_ldd->ldd_svname) - 1); return ret; {noformat} is given a {{dev}} that doesn't exist, and errors out, that is not being handled and propagated? ] |