Andy Smith <andy@xxxxxxxxxxxxxx> writes: >> Try mount -t ext4. If that doesn't work, see what e2fsck/tune2fs say. > > I've not needed that before and my instinct is that if it is needed, > something has gone wrong. But in any case it did not help: If the fs is listed in /etc/fstab, then mount finds the fs type from there. Otherwise, you have to specify it. At least, that used to be the case. This may have changed at some point and I still do it from mussle memory. > Here's the tuen2fs -l again: If tune2fs recognizes it then it should be fine. e2fsck -f should be the final arbiter of whether there is anything wrong with the filesystem though. You might check dmesg as mount suggests for any errors from the kernel explainging why it can't mount the filesystem. > In a way this is all becoming academic, as it seems very > filesystem-specific. Given I generally can't poke about inside these > disk images, it looks like I will never come up with a robust > procedure for block-wise copying of these LVs. It is filesystem specific. I believe FAT won't work right from this transition because it does embed the sector size in its boot sector. Due to its backward compatability, NTFS does this as well, though fixing this to reflect the new size isn't hard. Possibly HFS and iso9660 as well, but most common linux filesystems, such as ext4 and btrfs, already use 4k block sizes and so don't care about the sector size.
