New answers tagged

2

Judging from mdadm-3.4 source code, it does not accept any other inputs. As for the near=2,far=1 output, that's the default and nothing changed but values =1 are simply no longer printed because that essentially means "no additional copy" (counting starts at 1). In case both near and far equal 1, it prints NO REDUNDANCY. However you're not actually able to ...


1

Yes, as soon as you have filled up the systems buffers, your program will start to wait for the writes to complete to the slower disc. If that were not the case, the RAID software would essentially have to dynamically degrade the array and then sync in the background. In your case (!) I would upgrade the USB 2.0 external drive to a USB 3.0 enclosure.


0

In my case I brought up CentOS 7 and tried following everyone's instructions on this page. I kept running into a device busy message. The reason in my opinion why you are getting the "mdadm: cannot open device /dev/sda1: Device or resource busy" error message is because the device is already mounted as something else. I also did not want to make any changes ...


0

Ultimately the fix I found was similar to the one @Anthon posted. I ended up making a directory (VAR) in /home. I copied the contents of /var into that, then changed /etc/fstab such that /dev/md2 was being mounted at /var. Then I rebooted the system. When it came back I created a new /home directory (now ending up on /dev/md1), moved each of the user ...


0

The simple solution, as derobert suggested in a comment, is to leave (most of) the existing files where they are, only move the one directory that's going to receive big files, and create a symbolic link to make the expected path point to where the files will actually be stored. For example, if you're converting this server to hold a lot of mail, you might ...


1

RAID1 will destroy everything in the case you make a mistake or a virus decides to destroy your files. But, it makes it easy to fix actual hard drive failures. rsync will cause downtime in the (very common) case that your primary hard drive fails, because you have to transfer the data back (or at least swap out the drives). But, it makes it easy to recover ...


3

My personal favourite is: create a Raid1 Software Raid (mdadm) do regular incremental backups do weekly full-backups. The software raid1 protects you from online-faults, such that the volume is active ALWAYS, as long as one drive is okay. The software raid automatically syncs the contents between the drives, so you always have the up-to-date data ...


3

As your md2 is not empty, the easiest way is to rsync the data from /var to the new partition and then make a soft link: rsync -xav /var /home/VAR mv /var /var.org ln -s /home/VAR /var This would be best done when booted from a live distro (with mounted md1 and md2 and adapted paths), if that is not possible, you might want to rsync another time in ...



Top 50 recent answers are included