On Wed, Aug 26, 2015 at 10:43:45PM -0500, Eric Sandeen wrote: > On 8/26/15 10:39 PM, Theodore Ts'o wrote: > > > 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. > > Hm, do we not require a freshly-fsck'd fs (tm) prior to a conversion attempt, > like we do (I think) for resize? tune2fs is not as strict as resize2fs; iirc resize whines if it finds ERROR status, lack of VALID status, or it having been too long since the last fsck, whereas tune2fs only cares that the fs is marked VALID. (Scary, if you think about it...) --D > > That might be a good idea ... > > -Eric > > -- > To unsubscribe from this list: send the line "unsubscribe linux-ext4" in > the body of a message to majordomo@xxxxxxxxxxxxxxx > More majordomo info at http://vger.kernel.org/majordomo-info.html -- To unsubscribe from this list: send the line "unsubscribe linux-ext4" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
