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: Thu, 12 Feb 2009 22:36:24 +0100 From: Christian Ohm <chr.ohm@....net> To: linux-ext4@...r.kernel.org Subject: Re: How to recover a damaged ext4 file system? On Saturday, 7 February 2009 at 13:04, Eric Sandeen wrote: > that's counting "cylinders" - try "fdisk -u" to be able to display (or > specify) geometry in sectors, which is not a unit open to interpretation... Corrupted disk: Disk /dev/sdc: 1000.2 GB, 1000204886016 bytes 255 heads, 63 sectors/track, 121601 cylinders, total 1953525168 sectors Units = sectors of 1 * 512 = 512 bytes Disk identifier: 0xaaaaaaaa Device Boot Start End Blocks Id System /dev/sdc1 1 1953520064 976760032 83 Linux New partition: Disk /dev/sdc: 1000.2 GB, 1000204886016 bytes 255 heads, 63 sectors/track, 121601 cylinders, total 1953525168 sectors Units = sectors of 1 * 512 = 512 bytes Disk identifier: 0xaaaaaaaa Device Boot Start End Blocks Id System /dev/sdc1 63 1953520064 976760001 83 Linux Both disks show the exact same size in sectors (in the kernel messages as well), so the new partition on the new drive should be exactly the same as the one on the old drive. For some reason the new partition starts at sector 63, while the old one starts at sector 1 - but that could be a difference in creating the partitions (unless sector 1 is an invalid starting sector?). Best regards, Christian Ohm -- 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