Displaying 7 results from an estimated 7 matches for "ae22".
Did you mean:
a22
2017 May 03
3
CentOS 7 cloned VM cannot boot
...PE="LVM2_member"
/dev/sr0: UUID="2017-03-16-21-15-06-00" LABEL="ISOIMAGE" TYPE="iso9660"
PTTYPE="PMBR"
/dev/mapper/centos-root: UUID="fcee6215-e97a-4a4f-9473-5115f8559683"
TYPE="xfs"
/dev/mapper/centos-swap: UUID="b220b45f-ae22-4393-a74d-90b03d37c41b"
TYPE="swap"
# cat /etc/fstab
#
# /etc/fstab
# Created by anaconda on Thu Dec 8 13:40:06 2016
#
# Accessible filesystems, by reference, are maintained under '/dev/disk'
# See man pages fstab(5), findfs(8), mount(8) and/or blkid(8) for more info
#
/de...
2017 May 04
0
CentOS 7 cloned VM cannot boot
...ot;
> /dev/sr0: UUID="2017-03-16-21-15-06-00" LABEL="ISOIMAGE" TYPE="iso9660"
> PTTYPE="PMBR"
> /dev/mapper/centos-root: UUID="fcee6215-e97a-4a4f-9473-5115f8559683"
> TYPE="xfs"
> /dev/mapper/centos-swap: UUID="b220b45f-ae22-4393-a74d-90b03d37c41b"
> TYPE="swap"
>
> # cat /etc/fstab
> #
> # /etc/fstab
> # Created by anaconda on Thu Dec 8 13:40:06 2016
> #
> # Accessible filesystems, by reference, are maintained under '/dev/disk'
> # See man pages fstab(5), findfs(8), m...
2017 May 04
2
CentOS 7 cloned VM cannot boot
...D="fcee6215-e97a-4a4f-9473-5115f8559683"
TYPE="xfs"
/dev/vda2: UUID="cey71w-b81q-w1se-0Cww-X2cr-Milx-dWw15Z" TYPE="LVM2_member"
/dev/vda1: UUID="297e2939-d6f5-431a-9813-9848368ee306" TYPE="xfs"
/dev/mapper/centos-swap: UUID="b220b45f-ae22-4393-a74d-90b03d37c41b"
TYPE="swap"
# cat /etc/fstab
/dev/mapper/centos-root / xfs defaults 0 0
UUID=297e2939-d6f5-431a-9813-9848368ee306 /boot
xfs defaults 0 0
/dev/mapper/centos-swap swap swap defaults...
2017 May 03
3
CentOS 7 cloned VM cannot boot
Hello,
I'm struggling to make a cloned CentOS 7 VM (under KVM) to work.
The VM was cloned using mondorestore. Restore appears successful but the
VM won't boot; see:
http://iweb.noa.gr/files/centos7/supergrub2-scratchvm-20170503-04.png
I booted with CentOS 7 disk in troubleshooting mode (where the virtual
disk was automatically mounted without issues) and I tried to repair:
2017 Oct 26
0
not healing one file
Hey Richard,
Could you share the following informations please?
1. gluster volume info <volname>
2. getfattr output of that file from all the bricks
getfattr -d -e hex -m . <brickpath/filepath>
3. glustershd & glfsheal logs
Regards,
Karthik
On Thu, Oct 26, 2017 at 10:21 AM, Amar Tumballi <atumball at redhat.com> wrote:
> On a side note, try recently released health
2017 Oct 26
3
not healing one file
On a side note, try recently released health report tool, and see if it
does diagnose any issues in setup. Currently you may have to run it in all
the three machines.
On 26-Oct-2017 6:50 AM, "Amar Tumballi" <atumball at redhat.com> wrote:
> Thanks for this report. This week many of the developers are at Gluster
> Summit in Prague, will be checking this and respond next
2017 Oct 26
2
not healing one file
....c:1327:afr_log_selfheal] 0-home-replicate-0: Completed data selfheal on d3592efe-ed87-4b33-94cc-1263e733d45f. sources=0 [2] sinks=1
[2017-10-25 10:40:30.617211] I [MSGID: 108026] [afr-self-heal-metadata.c:52:__afr_selfheal_metadata_do] 0-home-replicate-0: performing metadata selfheal on bf0eeb5e-ae22-4cb3-bbf4-923d527db50a
[2017-10-25 10:40:30.620118] I [MSGID: 108026] [afr-self-heal-common.c:1327:afr_log_selfheal] 0-home-replicate-0: Completed metadata selfheal on bf0eeb5e-ae22-4cb3-bbf4-923d527db50a. sources=0 [2] sinks=1
[2017-10-25 10:40:30.627813] I [MSGID: 108026] [afr-self-heal-common....