Hi All,
Trying to run fsck on a local linux raid partition gave the following.
[root@... /]# fsck.ext4 /dev/md0 e2fsck 1.41.12 (17-May-2010) /dev/md0 has unsupported feature(s): 64bit e2fsck: Get a newer version of e2fsck!
Odd as the server is 64bit running latest kernel and using latest "e2fsprogs.x86_64".
Any ideas awould be much appreciated.
Cheers Steve k
Try this out to find out who complains the arch, strace fsck.ext4 /dev/md5. Post the output here that we can check more if it's from the app or the kernel.
------------ Banyan He Blog: http://www.rootong.com Email: banyan@rootong.com
On 2012-10-25 5:10 PM, Steve Brooks wrote:
Hi All,
Trying to run fsck on a local linux raid partition gave the following.
[root@... /]# fsck.ext4 /dev/md0 e2fsck 1.41.12 (17-May-2010) /dev/md0 has unsupported feature(s): 64bit e2fsck: Get a newer version of e2fsck!
Odd as the server is 64bit running latest kernel and using latest "e2fsprogs.x86_64".
Any ideas awould be much appreciated.
Cheers Steve k _______________________________________________ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
I think it comes out from the app itself for the verification. The question is if the soft raid supports by anyhow. Trying to build one test box for it.
print_unsupp_features: if (features[0] || features[1] || features[2]) { int i, j; __u32 *mask = features, m;
fprintf(stderr, _("%s has unsupported feature(s):"), ctx->filesystem_name);
for (i=0; i <3; i++,mask++) { for (j=0,m=1; j < 32; j++, m<<=1) { if (*mask & m) fprintf(stderr, " %s", e2p_feature2string(i, m)); } } putc('\n', stderr); goto get_newer; }
------------ Banyan He Blog: http://www.rootong.com Email: banyan@rootong.com
On 2012-10-25 5:10 PM, Steve Brooks wrote:
Hi All,
Trying to run fsck on a local linux raid partition gave the following.
[root@... /]# fsck.ext4 /dev/md0 e2fsck 1.41.12 (17-May-2010) /dev/md0 has unsupported feature(s): 64bit e2fsck: Get a newer version of e2fsck!
Odd as the server is 64bit running latest kernel and using latest "e2fsprogs.x86_64".
Any ideas awould be much appreciated.
Cheers Steve k _______________________________________________ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
On Thu, 25 Oct 2012, Banyan He wrote:
I think it comes out from the app itself for the verification. The question is if the soft raid supports by anyhow. Trying to build one test box for it.
print_unsupp_features: if (features[0] || features[1] || features[2]) { int i, j; __u32 *mask = features, m;
fprintf(stderr, _("%s has unsupported feature(s):"), ctx->filesystem_name); for (i=0; i <3; i++,mask++) { for (j=0,m=1; j < 32; j++, m<<=1) { if (*mask & m) fprintf(stderr, " %s", e2p_feature2string(i, m)); } } putc('\n', stderr); goto get_newer; }
Banyan He Blog: http://www.rootong.com Email: banyan@rootong.com
Thanks for looking, the issue was the filesystem was built with version of "e2fspogs" not consistent with upstream. Version "1.42-0" was compiled from source and used to create a filesystem of 20T as that is what was needed on the server. No entry was made in the repo config file to prevent the "rogue" "e2fspogs" from being replaced and so when an update took place this broke the filsystem utilities. After reinstalling the original "1.42-0" all is well again..
[root@... x86_64]# fsck.ext4 /dev/md0 e2fsck 1.42 (29-Nov-2011) /dev/md0: clean, 198212/335761408 files, 3637729870/5372161872 blocks
Cheers,
Steve