Re: Recover from an fsck failure

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]



Hi

> On Thu, May 28, 2020 19:38, Robert Nichols wrote:
>
>> What output do you get from:
>>
>>      file -s /dev/mapper/vg_voinet01-lv_log
>>      lsblk -f /dev/mapper/vg_voinet01-lv_log
>>
>
> file -s /dev/mapper/vg_voinet01-lv_log
> /dev/mapper/vg_voinet01-lv_log: symbolic link TO '../DM-5'
> dm-f
>
> lsblk -f /dev/mapper/vg_voinet01-lv_log
> NAME                      FSTYPE LABEL UUID MOUNTPOINT
> vg_voinet01-lv_log (dm-5)
>
>
> The cloned source is a CentOS-6.6 based FreePBSX appliance using lvm.  It

How exactly did you create the cloned disk?

If the source disk still works and is in operation without system errors,
the cloned disk with its filesystems should really be without error as
well.

If the filesystems have errors, maybe the cloning didn't go well?

If you cloned the disk while the system was running, it should at least be
done in single user mode to prevent filesystem errors.

Regards,
Simon

_______________________________________________
CentOS mailing list
CentOS@xxxxxxxxxx
https://lists.centos.org/mailman/listinfo/centos



[Index of Archives]     [CentOS]     [CentOS Announce]     [CentOS Development]     [CentOS ARM Devel]     [CentOS Docs]     [CentOS Virtualization]     [Carrier Grade Linux]     [Linux Media]     [Asterisk]     [DCCP]     [Netdev]     [Xorg]     [Linux USB]


  Powered by Linux