similar to: rhev/gluster questions , possibly restoring from a failed node

Add a new api xfs_repair for repairing an XFS filesystem. Signed-off-by: Wanlong Gao <gaowanlong at cn.fujitsu.com> --- daemon/xfs.c | 116 +++++++++++++++++++++++++++++++++++++++++ generator/generator_actions.ml | 23 ++++++++ gobject/Makefile.inc | 6 ++- po/POTFILES | 1 + src/MAX_PROC_NR | 2 +- 5 files changed, 145

Hi, Red Hat Gluster Storage is EOL, Red Hat moved Gluster devs to other projects, so Gluster doesn't get much attention. From my experience, it has deteriorated since about version 9.0, and we're migrating to alternatives. /Z On Fri, 27 Oct 2023 at 10:29, Marcus Peders?n <marcus.pedersen at slu.se> wrote: > Hi all, > I just have a general thought about the gluster >

On Mon, Mar 23, 2015 at 2:24 PM, Stephen Drotar <stephen at artifex360.com> wrote: > Hi, > > Everytime I restart Centos 7 I receive a error saying? > > metadata is corrupt > > and then I need to go through the process of mount and unmount the disk uuid then run > > xfs_repair {some uuid} > or > xfs_repair -L {some uuid} which ultimately corrupts

Hello, Recently I spent a bit time understanding rebalance since I want to know its performance given that there could be more and more bricks to be added into my glusterfs volume and there will be more and more files and directories in the existing glusterfs volume. During the test I saw something which I'm really confused about. Steps: SW versions: glusterfs 3.4.4 + centos 6.5 Inital

Hi Dudes/Dudettes, Does anyone know if Red Hat's bare metal KVM solution, RHEV-H, and the management component, RHEV-M, are available for CentOS? All I know is RHEV-M was being ported to Java and it would be getting released soon. I suppose RHEV-H isn't 100% necessary. Just running a minimum CentOS install for your KVMs would give you essentially the same thing. If there was a

Hi all, I have some doubts concerning the way asterisk records calls using the Monitor command. I ´ve done some jitter and packet loss tests in a such way that, from asterisk 1, I send a file to asterisk 2 and record this file in asterisk 2 using the Monitor command. To simulate the jitter and packet loss, I use the Cloud software, so with that one, I can "control" the jitter and

I used to be able to 'repair' ext4 fs issue (when the boot process drops you into emergency mode)... but now with xfs - it does not seem to let me do that. xfs_repair /dev/sda3 or xfs_repair -L /dev/sda3 both say fatal error fatal error -- couldn?t initialize XFS library How can I repair XFS with burning a DVD and finding an external USB reader etc... Thanks, Jerry

From: Qixiang Wan <qwan at redhat.com> Commit 0973765674abd773ad04a99ddfdff8e81693e1ff introduced a regression which caused the OVF file not to be generated when outputting to RHEV. Fixes RHBZ#602067 --- lib/Sys/VirtV2V/Target/RHEV.pm | 2 +- 1 files changed, 1 insertions(+), 1 deletions(-) diff --git a/lib/Sys/VirtV2V/Target/RHEV.pm b/lib/Sys/VirtV2V/Target/RHEV.pm index

Send CentOS-announce mailing list submissions to centos-announce at centos.org To subscribe or unsubscribe via the World Wide Web, visit http://lists.centos.org/mailman/listinfo/centos-announce or, via email, send a message with subject or body 'help' to centos-announce-request at centos.org You can reach the person managing the list at centos-announce-owner at centos.org When

I recently ran into some problems using certain oVirt (3.3) features on CentOS 6.4 hosts. The solution was to use the qemu-kvm-rhev version from the EL6 RHEV repository: http://ftp.redhat.com/pub/redhat/linux/enterprise/6Server/en/RHEV/SRPMS/qemu-kvm-rhev-0.12.1.2-2.355.el6_4.9.src.rpm It seems that this tree is not carried/built by CentOS. Are there any plans on the CentOS for carrying these

Hi. I'm also migrating to BeeGFS and CephFS (depending on usage). What I liked most about Gluster was that files were easily recoverable from bricks even in case of disaster and that it said it supported RDMA. But I soon found that RDMA was being phased out, and I always find entries that are not healing after a couple months of (not really heavy) use, directories that can't be

Store log from MSI installer. Log file will be located in firstboot scripts-done directory with name rhev-apt.log. The path has to be double-quoted to handle spaces in path name properly. Hopefully this can help resolve RHBZ#1584678 someday. Signed-off-by: Tomáš Golembiovský <tgolembi@redhat.com> --- v2v/convert_windows.ml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git

Hi, Everytime I restart Centos 7 I receive a error saying? metadata is corrupt and then I need to go through the process of mount and unmount the disk uuid then run xfs_repair {some uuid} or xfs_repair -L {some uuid} which ultimately corrupts even more. I?m running on a RAID 1 two identical drives this has happened more then once and had to reinstall. Any way I can prevent this when I

rmtree can die instead of returning failure under some circumstances. We don't want this to stop cleanup. --- lib/Sys/VirtV2V/Target/RHEV.pm | 15 ++++++++++++--- 1 files changed, 12 insertions(+), 3 deletions(-) diff --git a/lib/Sys/VirtV2V/Target/RHEV.pm b/lib/Sys/VirtV2V/Target/RHEV.pm index 295c19d..c9add0c 100644 --- a/lib/Sys/VirtV2V/Target/RHEV.pm +++

RHEV will fail to start a guest with more than one VirtIO disk marked as bootable. The previous behaviour of V2V simply marked all disks as bootable, intending to follow the behaviour of libvirt's qemu driver. However, libvirt's qemu driver actually only marks the first disk specified in the domain XML (which may or may not be Xda) as bootable. This change updates the RHEV output to follow

The previous support documentation said that for UEFI guests, when using RHEL ≥ 7.3 host, you must use qemu-kvm-rhev. For RHEL 8 this is inaccurate since qemu-kvm-rhev no longer exists. Since 7.3 is now an obsolete version of RHEL 7 we can change the text to refer to RHEL 7 only: On RHEL 7, only qemu-kvm-rhev (not qemu-kvm) is supported. Thanks: Ming Xie. --- v2v/virt-v2v-support.pod | 2

ovf:Envelope/Content/Section[xsi:type='ovf:OperatingSystemSection_Type']/@ovf:id is actually the canonical UUID of the guest, and must correspond to the filename. If it doesn't, the VM cannot be deleted from the export domain. Fixes RHBZ#583536 --- lib/Sys/VirtV2V/Target/RHEV.pm | 6 ++---- 1 files changed, 2 insertions(+), 4 deletions(-) diff --git

Date formats were previously undefined in RHEV's OVF output. They are now defined as: 'yyyy/mm/dd hh:mm:ss'. This change updates dates output by virt-v2v to use the new format. --- lib/Sys/VirtV2V/Target/RHEV.pm | 19 ++++++++++--------- 1 files changed, 10 insertions(+), 9 deletions(-) diff --git a/lib/Sys/VirtV2V/Target/RHEV.pm b/lib/Sys/VirtV2V/Target/RHEV.pm index

Without rhev-apt.exe the code path where firstboot scripts are created isn't taken, so it isn't tested and v2v/test-v2v-windows-conversion.sh is supposed to fail (it actually doesn't but for another reason, addressed in a followup patch). Signed-off-by: Roman Kagan <rkagan@virtuozzo.com> --- tests/fake-virt-tools/rhev-apt.exe | 1 + 1 file changed, 1 insertion(+) create mode

See: https://bugzilla.redhat.com/show_bug.cgi?id=1584678#c15 Fixes commit bcdbe6405c10ecb7374ae47eee6385be17dbd49e. However this bug was copied directly from old virt-v2v which did the same thing (from lib/Sys/VirtConvert/Converter/Windows.pm): echo installing rhev-apt >>log.txt "rhev-apt.exe" /S /v /qn >>log.txt Thanks: Lev Veyde --- v2v/convert_windows.ml | 2 +- 1