similar to: mdadm RAID sync speed limitation?

This is probably a hardware problem but I am posting here in case anyone else has seen it or it is actually software. If you have seen anything like it please let me know. Chuck For the last 1.5 years I have had occasional problems on a large (6.8 TB) Samba server. Two of the mounted filesystems will partially dismount at intervals between 3 days and 3 months. Files will still be open but any

-----Original Message-----From: John R Pierce <pierce at hogranch.com> Reply-to: CentOS mailing list <centos at centos.org> To: centos at centos.org Subject: Re: [CentOS] SCSI drives and Centos 7 Date: Sat, 29 Apr 2017 13:31:11 -0700 On 4/29/2017 12:42 PM, Gregory P. Ennis wrote: > what does `lspci` have to say about this raid card ? > > John, > > Thanks for the prompt

One of the greatest things about rails is that it is so standards-compliant, no other framework that I have seen have complied to the HTTP standard (think REST) in such a degree that Rails does. Kudos to you all for that. I think we (Rails community) should follow the line of standards compliance and also take it to the binary prefixes [1], i.e. kilobytes, megabytes, etc. For more than half a

-----Original Message-----From: John R Pierce <pierce at hogranch.com> Reply-to: CentOS mailing list <centos at centos.org> To: centos at centos.org Subject: Re: [CentOS] SCSI drives and Centos 7 Date: Sat, 29 Apr 2017 11:19:38 -0700 On 4/29/2017 10:49 AM, Gregory P. Ennis wrote: > I am remote from the unit today, and do not have a good way to look at > the board today, but the

From: Nikolay Ivanets <stenavin@gmail.com> Inspection code checks /etc/mdadm.conf to map MD device paths listed in mdadm.conf to MD device paths in the guestfs appliance. However on some operating systems (e.g. Ubuntu) mdadm.conf has alternative location: /etc/mdadm/mdadm.conf. This patch consider an alternative location of mdadm.conf as well. --- daemon/inspect_fs_unix_fstab.ml | 13

https://bugzilla.samba.org/show_bug.cgi?id=6881 Summary: --bwlimit option uses KiB/s, but is documented as (what amounts to) kB/s Product: rsync Version: 3.1.0 Platform: All OS/Version: All Status: NEW Severity: trivial Priority: P3 Component: core AssignedTo: wayned at

I've found what I think is an inconsistency in the Maildir quota implementation. According to the Maildir++ quota specification at: http://www.inter7.com/courierimap/README.maildirquota.html Maildir++ quota can be specified as maximum size, or maximum number of messages, or even both. The size specification is supposed to be in bytes. So I could use '10000000S' to set a quota of

md_create: mdadm: boot: mdadm: boot is not a block device. at /home/rjones/d/libguestfs/images/guest-aux/make-fedora-img.pl line 95. Looking into this, it appears the old version of mdadm shipped in Ubuntu (mdadm 2.6.7) doesn't support the notion of giving arbitrary names to devices. Thus you have to do: mdadm --create /dev/md0 [devices] We do: mdadm --create boot [devices] which it

Il 29/01/19 18:47, mark ha scritto: > Alessandro Baggi wrote: >> Il 29/01/19 15:03, mark ha scritto: >> >>> I've no idea what happened, but the box I was working on last week has >>> a *second* bad drive. Actually, I'm starting to wonder about that >>> particulare hot-swap bay. >>> >>> Anyway, mdadm --detail shows /dev/sdb1

I am trying to install on a CentOS5 box http://www.mjmwired.net/resources/files/msttcorefonts-2.0-1.noarch.rpm then did an xfs restart, even an alt-ctrl-backspace. The fonts are located in /usr/share/fonts/msttcorefonts/ with the owner root & 644. I can't see them when I go to preferences > fonts. I have another computer with CentOS5, the fonts are installed and I can use them w/o

Hi, what?s the proposed way of handling mdadm in Centos 7? I did not get any notification when a disk in a RAID1 failed, and now that the configuration has changed after resolving the problem, I might be supposed to somehow update /etc/mdadm.conf. Am I not supposed to be notified by default when something goes wrong with an array? How do I update /etc/mdadm.conf? I?m used to all this working

Hello, i have a little problem. Our server has an broken RAID. # cat /proc/mdstat Personalities : [raid1] md0 : active raid1 sda1[2](F) sdb1[1] 2096064 blocks [2/1] [_U] md2 : active raid1 sda3[2](F) sdb3[1] 1462516672 blocks [2/1] [_U] md1 : active raid1 sda2[0] sdb2[1] 524224 blocks [2/2] [UU] unused devices: <none> I have remove the partition: # mdadm --remove

On 4/29/2017 12:42 PM, Gregory P. Ennis wrote: > what does `lspci` have to say about this raid card ? > > John, > > Thanks for the prompt : > > lspci demonstrates : > > 02:01.0 RAID bus controller: LSI Logic / Symbios Logic MegaRAID (rev 01) > 02:02.0 SCSI storage controller: Adaptec AIC-7902B U320 (rev 10) > 02:02.1 SCSI storage controller: Adaptec AIC-7902B U320

On Sun, Apr 30, 2017 at 1:03 PM, Gregory P. Ennis <PoMec at pomec.net> wrote: > Thanks for your help. I did not want to replace this machine with new > equipment, but it looks like I may need to do just that. > > Here are the results with respect to the lsi raid board for : > > lspci -nn > > > 02:01.0 RAID bus controller [0104]: LSI Logic / Symbios Logic MegaRAID

I installed a CentOS-5 core OS (using --nobase in my kickstart). For some reason, it included mysql-5.0.22. When I do "yum remove mysql", it says it will also remove exim and mdadm for dependencies. I don't care that exim will be removed, but I need mdadm as I'm doing software RAID. But why are these even related? When I do: rpm -q --requires mysql neither exim or mdadm is

In article <20190225050144.GA5984 at button.barrett.com.au>, Jobst Schmalenbach <jobst at barrett.com.au> wrote: > Hi. > > CENTOS 7.6.1810, fresh install - use this as a base to create/upgrade new/old machines. > > I was trying to setup two disks as a RAID1 array, using these lines > > mdadm --create --verbose /dev/md0 --level=0 --raid-devices=2 /dev/sdb1

Hi, I lost my mdadm.conf (and /proc/mdadm shows nothing useful) and I'd like to mount the filesystem again. So I've booted using rescue but I was wondering if I can do a command like this safely (i.e without losing the data previously stored). mdadm -C /dev/md0 --level=raid0 --raid-devices=2 /dev/sda1 /dev/sdb1 Where of course the raid devices and the /dev/x are the correct ones

Hey List, So I had a 4 drive software RAID 5 set up consisting of /dev/sdb1, /dev/sdc1, /dev/sdd1 and /dev/sde1. I reinstalled my OS and after the reinstall I made the mistake of re-assembling the array incorrectly by typing "sudo mdadm --assemble /dev/md0 /dev/sdb /dev/sdc /dev/sdd /dev/sde" in a moment of stupidity. Obviously this didn't work and the array wouldn't mount and

Is there some new trick to making raid devices on Centos5? # mdadm --create /dev/md3 --level=1 --raid-devices=2 /dev/sdc1 /dev/sdc1 mdadm: error opening /dev/md3: No such file or directory I thought that worked on earlier versions. Do I have to do something udev related first? -- Les Mikesell lesmikesell at gmail.com

Il 29/01/19 20:42, mark ha scritto: > Alessandro Baggi wrote: >> Il 29/01/19 18:47, mark ha scritto: >>> Alessandro Baggi wrote: >>>> Il 29/01/19 15:03, mark ha scritto: >>>> >>>>> I've no idea what happened, but the box I was working on last week >>>>> has a *second* bad drive. Actually, I'm starting to wonder about