hoctinhoc

How to perform fsck on a ploop container


(UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY)



http://kb.sp.parallels.com/en/115683






To run fsck, follow the following steps:

1. Ensure the container is stopped:
   ~# vzctl stop 100500 ~# vzlist 100500 CTID NPROC STATUS IP_ADDR HOSTNAME 100500 - stopped 10.10.10.11 fsck.test Note: Do not perform fsck when the container is running or mounted.
2. Mount the container's ploop image. This allocates a ploop device on the host:
   ~# ploop mount /vz/private/100500/root.hdd/DiskDescriptor.xml add delta dev=/dev/ploop1 img=/vz/private/100500/root.hdd/root.hds (rw)
3. Run fdisk -l for the /dev/ploopX device reported by the previous command. You will need to let the system fetch a list of partitions on /dev/ploopX:
   ~# fdisk -l /dev/ploop1 WARNING: GPT (GUID Partition Table) detected on '/dev/ploop1'! The util fdisk doesn't support GPT. Use GNU Parted. Disk /dev/ploop1: 10.7 GB, 10737418240 bytes 255 heads, 63 sectors/track, 1305 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk identifier: 0x00000000 Device Boot Start End Blocks Id System /dev/ploop1p1 1 1306 10485759+ ee GPT
4. Perform a file system check for the partition reported in the previous command's output:
   ~# e2fsck /dev/ploop1p1 e2fsck 1.41.12 (17-May-2010) /dev/ploop1p1: clean, 22404/655360 files, 238012/2620923 blocks Note: You may add more options to e2fsck, check the manual pages if needed.
5. Unmount the ploop image:
   ~# ploop umount -d /dev/ploop1 Unmounting device /dev/ploop1