| 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
| ||
|
Date: Wed, 26 Aug 2015 23:39:49 -0400 From: Theodore Ts'o <tytso@....edu> To: Chris Hunter <chris.hunter@...e.edu> Cc: linux-ext4@...r.kernel.org Subject: Re: errors following ext3 to ext4 conversion On Wed, Aug 26, 2015 at 08:53:13PM -0400, Chris Hunter wrote: > I attempted to convert ext3 to ext4 filesystem. I am using e2fsprogs > (1.42.12.wc1 (15-Sep-2014)). I ran command tune2fs tune2fs -O > extents,uninit_bg,dir_index /dev/DEV -o acl,user_xattr /dev/DEV. > I then encountered errors (below) when running read-only e2fsck. I have not > mounted the filesystem. I'd suggest using debugfs -w -R "features ^extents,^uninit_bg" /dev/DEV and then try re-running the read-only e2fsck. Did you try running a read-only e2fsck before you tried using the tune2fs command? Merely turning on the extents feature doesn't actually convert any files to use extents. So if e2fsck is showing errors like this: > e2fsck shows a variety of errors: > Pass 1: Checking inodes, blocks, and sizes > Inode 118843400, end of extent exceeds allowed value > (logical block 1409, physical block 3803034390, len 976) > Inode 118843400, end of extent exceeds allowed value > (logical block 2385, physical block 3803056554, len 4294966945) This suggests that the file system was likely corrupted before you tried converting the file system, since there should not have been any extent-mapped files in an ext3 file system. Regards, - Ted -- 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
Powered by blists - more mailing lists