linux-ext4 - "Unknown code" error when enabling metadata

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Date:	Mon, 30 Jul 2012 21:53:15 -0500
From:	Nick Semenkovich <semenko@...m.mit.edu>
To:	linux-ext4@...r.kernel.org
Subject: "Unknown code" error when enabling metadata_csum on ext4 raid1 device

I'm trying to enable metadata_csum on an ext4 raid1 device, but end up
with a semi-cryptic error.

(This is probably the same thing Tomasz Chmielewski reported in
http://www.spinics.net/lists/linux-ext4/msg33139.html )

Is this issue being tracked someplace?

$ uname -ar
Linux dev 3.5.0-6-generic #6-Ubuntu SMP Mon Jul 23 19:52:14 UTC 2012
x86_64 x86_64 x86_64 GNU/Linux

$ git clone git://git.kernel.org/pub/scm/fs/ext2/e2fsprogs.git
$ ./configure
[snip]
$ make progs
[snip]
$ sudo misc/tune2fs -O metadata_csum /dev/md1
tune2fs 1.42.3 (14-May-2012)
rewrite_directory: Unknown code Ijv 64 while rewriting directories

The error code changes when I re-run tune2fs (to [a-zA-Z]*3 64).


I've tried this on the master, "next", & "pu" git branches, all with errors.


$ debugfs -R 'stats' /dev/md1 >
http://web.mit.edu/semenko/Public/debugfs-md1.txt


Best,
Nick

-- 
Nick Semenkovich
Laboratory of Dr. Jeffrey I. Gordon
Medical Scientist Training Program
School of Medicine
Washington University in St. Louis
http://web.mit.edu/semenko/
--
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html