If we have a partition
/dev/sda1, and mount it to a mount point (i.e.
/mnt), we can then use the files and folders under
Before changing the partition
/dev/sda1 I umount
/mnt, and then perform disk resizing operations.
/mnt has been unmounted I am confused as to how 'data corruption' can occur because the filesystem (
/mnt) has been unmounted.
i.e. after sometimes resizing the disk I get errors after I run
e2fsck on the unmounted partition - does this mean the actual data is stored on the partition
/dev/sda1 or is it meta-data of some sort?
Also in the future if I wish to make a backup would it make more sense to use
dd to backup the partition or use
cp to copy the data under
fsck /dev/sda2 fsck from util-linux 2.20.1 e2fsck 1.42.5 (29-Jul-2012) fsck.ext3: Group descriptors look bad... trying backup blocks... fsck.ext3: Bad magic number in super-block while trying to open /dev/sda2 The superblock could not be read or does not describe a correct ext3 filesystem. If the device is valid and it really contains an ext3 filesystem (and not swap or ufs or something else), then the superblock is corrupt, and you might try running e2fsck with an alternate superblock: e2fsck -b 8193 <device>