https://jira.whamcloud.com This file is an XML representation of an issue en-us 9.4.14 940014 05-12-2023 https://jira.whamcloud.com/browse/LU-2732 Lustre <p>After upgrade the whole system from 2.1.4 to 2.4, then downgrade to 2.1.4 again, cannot mount MDS, got following error messages:</p> <div class="preformatted panel" style="border-width: 1px;"><div class="preformattedContent panelContent"> <pre>[root@fat-amd-1 ~]# mount -t lustre -o acl,user_xattr /dev/sdb1 /mnt/mds1 LDISKFS-fs warning (device sdb1): ldiskfs_fill_super: extents feature not enabled on this filesystem, use tune2fs. LDISKFS-fs (sdb1): couldn't mount RDWR because of unsupported optional features (100) LustreError: 8077:0:(obd_mount.c:1360:server_kernel_mount()) premount /dev/sdb1:0x0 ldiskfs failed: -22 Is the ldiskfs module available? LustreError: 8077:0:(obd_mount.c:1700:server_fill_super()) Unable to mount device /dev/sdb1: -22 LustreError: 8077:0:(obd_mount.c:2198:lustre_fill_super()) Unable to mount (-22) mount.lustre: mount /dev/sdb1 at /mnt/mds1 failed: Invalid argument This may have multiple causes. Are the mount options correct? Check the syslog for more info. </pre> </div></div> before upgrade client and server: 2.1.4 RHEL6<br/> after upgrade client and server: lustre-master build #1194 RHEL6 LU-2732

LDISKFS-fs (sdb1): couldn't mount RDWR because of unsupported optional features (100)

Bug Major Resolved Done Hongchao Zhang Sarah Liu Thu, 31 Jan 2013 21:07:20 +0000 Mon, 11 Jan 2016 18:24:23 +0000 Mon, 11 Jan 2016 18:24:23 +0000 Lustre 2.4.0 0 7 <p>The 0x100 is quota feature, you'd disable the ext4 quota feature by 'tune2fs -O ^quota' before downgrade.</p> <p>Hi, <br/> During update&amp;downgrade, are you using same linux distro? this error is about quota feature<br/> in "ldiskfs/ldiskfs/ldiskfs.h"<br/> ...<br/> #define LDISKFS_FEATURE_RO_COMPAT_QUOTA 0x0100<br/> ...</p> <p>this feature isn't defined in some Linux Distro. e.g. it is defined in RHEL6 but is not in RHEL5.</p> <p>Sarah, can you please put the test configuration (client/server distro versions and exact 2.4 version) into the "Environment" section of the ticket.</p> <p>There was a patch landed on master (<a href="http://review.whamcloud.com/4968" class="external-link" target="_blank" rel="nofollow noopener">http://review.whamcloud.com/4968</a>) about quieting quota messages, and I <em>think</em> that RO_COMPAT_QUOTA is no longer enabled by default for an upgrade. Niu, is that correct? If not, then the fix is to not enable RO_COMPAT_QUOTA on 2.4 by default, and if the filesystem already has quota enabled then it should refuse to mount in that case.</p> <p>Andreas, the quota is still enabled by default for 2.4 (see enable_default_ext4_features()), why we shouldn't enable it by default? for the performance problem or downgrading? For downgradning, I think user can just simply disable quota before downgranding lustre.</p> <p>To be clear, upgraded filesystems don't have RO_COMPAT_QUOTA by default. The admin has to explicitly run tunefs.lustre --quota to enable it. Once this is done, the admin will indeed have to clear the flag with tune2fs if he wants to downgrade.<br/> As for new filesystems formatted with 2.4, they have the quota feature enabled by default.</p> <p>Sorry for confusion. I thought that quota was enabled by default when upgrading to 2.4, but if this has to be done manually by tunefs that is fine. </p> <p>Is there any change needed for the manual in this case? If yes, please move this over to an LUDOC bug, otherwise it can just be closed.</p> Development Rank 1|hzvifj: Rank (Obsolete) 6636 Severity