similar to: software raid1 syncing

When a new system CentOS-4.4 is built the swap partition is always reversed... Note md3 below, the raidtab is OK, I have tried various raid commands to correct. swapoff -a raidstop /dev/md3 mkraid /dev/md3 --really-force swapon -a And then I get a proper ourput for /proc/mdstat, but when I reboot /proc/mdstat again reads as below, with md3 [0] [1] reversed. [root]# cat /proc/mdstat

Dear All, I would like to get community's feedback with regard to RAID1 ( Software or Hardware) implementations with asterisk. This is my setup Motherboard with SATA RAID1 support CENT OS 4.4 Asterisk 1.2.19 Libpri/zaptel latest release 2.8 Ghz Intel processor 2 80 GB SATA Hard disks 256 MB RAM digium PRI/E1 card Following are the concerns I am having I'm planing to put this asterisk

--- Ryan Lane <ryanlane@gmail.com> wrote: > On Fri, 11 Mar 2005 07:21:39 -0800 (PST), Steven > Vishoot > <sir_funzone@yahoo.com> wrote: > > ok now i am frustrated. this is the third day in a > row > > that my server has crashed running centos4, i can > not > > ping or access the console but the hardware is > still > > running. it does not leave

The secondary disc was used in a lab rig to boot off of and test something after which the primary was replaced and the system was booted off of. It saw the secondary as more recent and dropped the primary so, the secondary was removed and the primary was used to boot. Figuring that made it more recent, even after it was restarted with the "now older" secondary, it still wants to drop

Hello All, I have an off topic question about rsync and was wondering if i can get some kind person help with it. I have two servers with each server have three same directories on them /dir1/ /dir2/ /dir3/ . How would i achieve this by using rsync? I have tried rsync -avrt --delete server_ip:/dir1/ /dir2/ /dir3/ /dir1/ /dir2/ /dir3/ this does not do anything except give errors. Someone on IRC

Dear fellow CentOS users, I have never experienced this problem with hard disk management before and cannot explain it to myself on any rational basis. The setup: I have a workstation for testing, running latest CentOS 7.3 AMD64. I am evaluating oVirt and a storage-ha as part of my bachelors thesis. I have already been running a RAID1 (mdraid, lvm2) for the system and some oVirt 4.1 testing.

> On Mon, Feb 25, 2019 at 11:54 PM Simon Matter via CentOS > <centos at centos.org> > wrote: > >> > >> > What makes you think this has *anything* to do with systemd? Bitching >> > about systemd every time you hit a problem isn't helpful. Don't. >> >> If it's not systemd, who else does it? Can you elaborate, please? >> >

it seems like I keep running into a wall. The present raid array...well let me do an fdisk -l: ---------------------------------------- Disk /dev/hda: 250.0 GB, 250059350016 bytes 255 heads, 63 sectors/track, 30401 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Device Boot Start End Blocks Id System /dev/hda1 * 1 13 104391 fd Linux

Hello, I was trying to install CentOS-5.5-i386-bin-DVD tonight and kept on getting this same error and i have no idea what is causing this annoyance and not letting me complete the install because as soon as this error is produced it says this a bug and should be filed. Before I file a bug report i would like to know if anyone else ran into this and would mind pointing me in the right

I am running software RAID1 on a somewhat critical server. Today I noticed one drive is giving errors. Good thing I had RAID. I planned on upgrading this server in next month or so. Just wandering if there was an easy way to fix this to avoid rushing the upgrade? Having a single drive is slowing down reads as well, I think. Thanks. Feb 7 15:28:28 server smartd[2980]: Device: /dev/sdb

I just installed CentOS 5.4 64 bit release on a 1.9ghz CPU with 8gB of RAM. It has 2 Western Digital 1.5TB SATA2 drives in RAID1. [root at server ~]# df -h Filesystem Size Used Avail Use% Mounted on /dev/md2 1.4T 1.4G 1.3T 1% / /dev/md0 99M 19M 76M 20% /boot tmpfs 4.0G 0 4.0G 0% /dev/shm [root at server ~]# Its barebones

> > Dear all, Thanks for the greate explanation regaing Software/H/W Raid. This details better but on voip-info.org/wiki pages. Thanks lot agian. Regs, Vidura Senadeera. ====================================== Dear All, > > > > I would like to get community's feedback with regard to RAID1 ( Software > or > > Hardware) implementations with asterisk. > >

(Resend: message didn't show, was my original message too big? Posted one of the output files to a website to see) The point of RAID1 is to allow for continued uptime in a failure scenario. When I assemble servers with RAID1, I set up two HDDs to mirror each other, and test by booting from each drive individually to verify that it works. For the OS partitions, I use simple partitions and

You don't need to mount it. Like this : # getfattr -d -e hex -m. /path/to/brick/.glusterfs/00/46/00462be8-3e61-4931-8bda-dae1645c639e # file: 00/46/00462be8-3e61-4931-8bda-dae1645c639e trusted.gfid=0x00462be83e6149318bdadae1645c639e trusted.gfid2path.05fcbdafdeea18ab=0x30326333373930632d386637622d346436652d393464362d3936393132313930643131312f66696c656c6f636b696e672e7079

Right, that's my problem. a drive is unplugged... while the system is not running mdadm will not reassemble the array on boot. Red Hat Bugzilla ? Bug 1451660 Write that Fixed In Version:dracut-033-546.el7 I have drucat version 033-554.el7 and this bag don't fixed! >I believe you are hitting this bug: > > ? https://bugzilla.redhat.com/show_bug.cgi?id=1451660 > >That is,

I''ve been trying to install a 2.6.37-12 kernel from kernel-ppa on one of my Ubuntu machines without success. It keeps giving errors like this: [ 9.115544] ata9: exception Emask 0x0 SAct 0xf SErr 0x0 action 0x10 frozen [ 9.115550] ata9.00: failed command: READ FPDMA QUEUED [ 9.115556] ata9.00: cmd 60/04:00: d4:82:85/00:00:1f:00:00/40 tag 0 ncq 2048 in [ 9.115557]

Hey, I installed 2 new data servers with a big (12TB) RAID6 mdraid. I formated the whole arrays with bad blocks checks. One server is moderately used (nfs on one md), while the other not. One week later, after the raid-check from cron, I get on both servers a few block_mismatch... 1976162368 on the used one and a tiny bit less on the other...? That seems a tiny little bit high... I do the

Good morning, hope i got it right... using: https://access.redhat.com/documentation/de-de/red_hat_gluster_storage/3.1/html/administration_guide/ch27s02 mount -t glusterfs -o aux-gfid-mount glusterpub1:/workdata /mnt/workdata gfid 1: getfattr -n trusted.glusterfs.pathinfo -e text /mnt/workdata/.gfid/faf59566-10f5-4ddd-8b0c-a87bc6a334fb getfattr: Removing leading '/' from absolute path

ok, finally managed to get all servers, volumes etc runnung, but took a couple of restarts, cksum checks etc. One problem: a volume doesn't heal automatically or doesn't heal at all. gluster volume status Status of volume: workdata Gluster process TCP Port RDMA Port Online Pid ------------------------------------------------------------------------------

Hi, Can you find and check the files with gfids: 60465723-5dc0-4ebe-aced-9f2c12e52642faf59566-10f5-4ddd-8b0c-a87bc6a334fb Use 'getfattr -d -e hex -m. ' command from https://docs.gluster.org/en/main/Troubleshooting/resolving-splitbrain/#analysis-of-the-output . Best Regards,Strahil Nikolov On Sat, Jan 20, 2024 at 9:44, Hu Bert<revirii at googlemail.com> wrote: Good morning,