This failure mode depends on the size of the filesystem, the number of reserved blocks, and the inodes used. This series of steps reproduces the problem for me:
rm -f /dev/shm/test.ext4 dd if=/dev/zero of=/dev/shm/test.ext4 bs=1 count=1 seek=1023M mkfs.ext4 -F /dev/shm/test.ext4 tune2fs -r 0 /dev/shm/test.ext4 mkdir -p /mnt/test mount -o loop /dev/shm/test.ext4 /mnt/test echo $(seq $(( $(hexdump -s 0x410 -n 2 -e '"%d\n"' /dev/shm/test.ext4) - 5007 )) ) | (cd /mnt/test; xargs touch) umount /mnt/test blkid -p /dev/shm/test.ext4 /dev/shm/test.ext4: ambivalent result (probably more filesystems on the device, use wipefs(8) to see more details) -- mount ext fileystem fails, booting fails, blkid produces no output https://bugs.launchpad.net/bugs/518582 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
