similar to: All data gone AWOL

Hello, We have an application that does a huge amount of disk i/o (mostly writes) and have hit performance problems. It seems that the use of O_DIRECT would help but information on the development status is hard to come by. I have checked 2.4.18 and 2.5 kernels and there seems to be an interface but no actual implementation. It has been suggested that it only works with ext2 but we need ext3.

I doubt that this is actually an ext3 problem so I'm taking a bit of a liberty, but... We have several machines that have two ext3 partitions (/, /boot) and a large raw partition. Something happened that destroyed both the ext3 partitions on all machines. I appears that the app writing to the raw partition had a bug that caused it to write to negative block numbers and that this wrote all

I am moving from a CentOS 6 VM to a CentOS 7 VM and two pieces of software I use seem to be missing: RT (from Best Practical Solutions) -- an RPM for rt 3.1.13 was in EPel 6 and until recently, was also in EPel 7. It is not there now. Since it is just Perl code, I wonder if I can just install the el6 rpm on a CentOS 7 system. Bugzilla -- I installed this from an RPM on my

Hello all-- These instructions are somewhat OK but my messed up box is the only one I've got basically to help with this problem. Where can we find "correction" instructions using a "rescue" CD or flash drive? I understand RedHat provided detailed instructions to supported customers. Thanks. _______________________ Sent from MzK's phone. ---------- Forwarded message

On 09.12.2015 00:39, NightLightHosts Admin wrote: > On Tue, Dec 8, 2015 at 5:26 PM, Dennis Jacobfeuerborn > <dennisml at conversis.de> wrote: >> Hi, >> today we ran into a strange problem: When performing a regular Windows >> 2008r2 update apparently among other things the following was installed: >> "SUSE - Storage Controller - SUSE Block Driver for

This is a quick recovery and fix for the machines rendered unbootable after the grub2/shim yum update. It is written for CentOS 8.2.2004 but similar should work for any CentOS 8 or 7 as long as you get the correct shim file, that is, the one from the latest installation media. I am running on an x86_64 architecture (see uname -i). Please use the correct shim file for your architecture

OK sorry to hammer the list but one more question - having almost got the drives mirrored and happy - since I have created a custom initrd that has the raid1 drivers in it, do I now have to tell yum to ignore kernel updates? Will the stock kernel render me unbootable? Actually I am not 100% sure the initrd I created # mkinitrd -f --preload=raid1 /mnt/tmp/initrd-`uname -r`.img `uname -r` is

Akemi Yagi <amyagi at gmail.com> wrote: > This issue? > > https://bugs.centos.org/view.php?id=17767 This is a huge bug! Using Firefox to watch videos is a basic activity. The bug with grub2 a few months ago was even more serious: it made systems unbootable. It's discomfiting to see two major bugs so close to each other. -- Yves Bellefeuille <yan at storm.ca>

Hi, I've got a problem with booting zfs-on-root FreeBSD 9.2-PRERELEASE. I'm getting: ZFS: i/o error - all block copies unavailable ZFS: can't read MOS of pool klawisz gptzfsboot: failed to mount default pool klawisz Machine is VM running under KVM on Proxmox 2.3-13. VM has 8 GB of RAM, 400 GB of local storage with SCSI Controller type: Default (lsi). I'm not sure what I did to

I am running an Intel x64 machine using UEFI to boot an SSD. Installing the latest yum update which includes grub2 and kernel 4.18.0-193.14.2.el8_2.x86_64 renders the machine unbootable, blank screen where grub should be, no error messages, just hangs. After some hours I managed to modify another bootable partition (containing older software) and boot it from there. After that, I? found out

I have a Windows 7 laptop that I want to make dual boot with CentOS 6.2. My plan was to use the Windows Disk Management tool to partition the disk, but I do not have the needed admin rights on the box to use that. Has anyone used the partitioning tool that comes with 6.2 to do this? Can I have some level of confidence that it will not mess things up so that I cannot boot into Windows? if it screws

I'd like to rename my existing volume groups and logical volumes (I picked names a long time ago I no longer like :-). I recently stumbled across the lvrename and vgrename commands, but when I tried the former to rename the logical volume that my root partition resides on, the system became unbootable. In addition to renaming the LV (and VG if I decide to to that as well), what

I was looking at my newly installed CentOS 4.2 system with ls* commands yesterday and lsdev was not on the system. Did I miss installing a package? A Google search for CentOS 4.2 and lsdev was unhelpful. -- Jerry Hubbard hubbardjw at charter.net

About a month ago I did an upgrade of glibc on one of our test centos5 systems. And yum happily gave me about 8 packages, including both bitted-nesses of glibc-common. This morning I was showing a co-worker how to upgrade glibc. And he found that yum wouldn't give him glibc-common-2.5-123.el5_11.1.i386.rpm. So I browsed to the web interface of one of the centos5 mirrors, and couldn't

On Tue, Mar 24, 2015 at 10:56:29AM -0700, Ali Corbin wrote: > This morning I was showing a co-worker how to upgrade glibc. And he > found that yum wouldn't give him > glibc-common-2.5-123.el5_11.1.i386.rpm. > > So I browsed to the web interface of one of the centos5 mirrors, and > couldn't find it either. Not in the x86_64 tree anyway. It's in the updates tree for

Hi, I came back from a quiet weekend today and found my E400P box to have gone astray. Asterisk is loaded from inittab, and started crashing and reloading a couple of thousands of times, each time notifying my monitoring service :-P I remember there would be issues on old cvs stuff since the crash at digium so I made a clean checkout just now. Here is what happens when I load manually:

I am cleaning up my 4-STABLE system. After a fresh installworld, I am looking at files that did not get touched by the install. Is it safe to remove all such files? In particular, I am looking at /usr/libexec/lib-elf.so.1, which has the schg flag set. I am afraid to remove this for fear of making my system unbootable. Could somebody please reassure me that it is ok to noschg and remove this old

On 22/10/2019 18:58, John Redmond wrote: > Thanks, Rowland.? Here's the smb.conf file on the Unix domain member.? > I know you are not a fan of winbind enum, but I add it to see if it > helped. It isn't that I am not a fan of 'winbind enum', it is that it only does two things: It enumerates users and groups (which isn't actually required) It slows things down I

Hello All, updating from Centos7.3 to Centos7.4 rendered one of our laptops unbootable. EM: Failed to open \EFI\BOOT\grubx64.efi - Not Found Failed to load image \EFI\BOOT\grubx64.efi: Not Found start_image() returned Not Found How could this occur because of an update and how to fix this? What I tried is booting from centos usb, chroot to /mnt/sysimage and gave command: efibootmgr

Following the advice on this mailing list, I rebuilt (from scratch) Centos 7.8. I added the following line into /etc/yum.conf before the first update: exclude=grub2* shim* mokutil The system worked fine. I was able to do general updates yum -y update and all was well. HOWEVER, following Johnny Hughes' directions: a) remove the 'exclude' line from yum.conf b) perform update: