blkid knows to identify the ext4dev FSTYP of a partition that was formatted with mkfs.ext4dev. quota tools and various util-linux utils are also aware of ext4dev, so ext4dev shares the same capabilit
Adding ext4dev to every case seems harmless enough. TBH I thought I had it there already but I guess not. I'm less certain of the change from fsck -t $FSTYP to fsck.$FSTYP What issue are you avoiding
As I wrote in the patch description, the fsck utility in Fedora 15 invokes fsck.ext4 for some reason when calling fsck -t ext4dev. this fails because fsck.ext4 doesn't know the snapshot feature. I di
RHEL6 does the same; mkfs.ext4dev then fsck -t ext4dev invokes fsck.ext4; but this is because blkid identifies it as ext4, not ext4dev, despite the test_fs flag being set. ISTR this is due to some to
No, I didn't file a bug. In any case, it was Sergey, who tested and reported the problem on F15. Would you agree to fix the problem in xfstests now, so that F15 users can test ext4dev and fix the bug
No, I didn't file a bug. In any case, it was Sergey, who tested and reported the problem on F15. Would you agree to fix the problem in xfstests now, so that F15 users can test ext4dev and fix the bu
To make a long story a bit shorter, there was no intention to set FSTYP manually, that was only a temporary hack to make next4 clone work, but since ext4dev is identified by blkid and respected by fs
This is a change I make locally when I've been debugging my bigalloc code as well. There reason for that is because I want to override the fsck.ext4 that would get used by using path hacking. The pro