upgrade

New raid array with Linux and mdadm

Posted by Cameron Stokes on February 28, 2009
geek, raid, upgrade / 2 Comments

I ran out of free space on my file server a few months back and have been too cheap to upgrade until recently. I first started with four 400 GB drives a few years ago and setup a RAID 5 array using Linux and mdadm giving me roughly 1.2 TB of space. I upgraded a disk at a time as needed until I had seven drives and about 2.6 TB of space:

Filesystem Size Used Avail Use% Mounted on
/dev/md0 2.6T 2.6T 2.8G 100% /mnt/sata-array

Having filled this up I started looking for the best way to upgrade. The Seagate 1.5 TB drives offered the best per GB pricing however with the recent bad news specific to these drives I decided to stear clear of Seagate. The next best option I could find were the 1 TB Western Digital Green Power drives. The Green Power drives have a lower overall rotational speed and will spin down as allowed to save power with the added benefit of generating less heat and also noise.

After reading several threads (one here) regarding Bit Error Rates (BER) with drives this large and the potential for errors even with a RAID 5 array I decided to go for RAID 6 with my new array. RAID 6 can survive 2 disk drive failuers and will theoretically protect me from the high BER these drives are susceptible to.

In a previous post I mentioned trying ZFS. I scrapped that idea when I found you can’t expand a ZFS zpool by adding single drives to the system. You can add additional zpools to a zpool (not sure if my terminology is right there) but that means adding an equal amount of storage to your existing array when you want to upgrade. This means if I have 4 drives in a zpool, I’d have to add another 4 drives to upgrade. You can also replace drives in the zpool with larger drives to expand them, but you have to replace each drive. Neither option is very cost effective for me. I was a little disappointed not to be able to try something new but have been happy with Linux and mdadm so it was not a difficult decision to go back to them.

I ordered 6 drives from Amazon and once they arrived I assembled them into a RAID 6 array. mdadm has to sync the newly created array but the array is online and can be used normally. A quick ext3 format and I have 3.6 TB of space available.

Filesystem Size Used Avail Use% Mounted on
/dev/md0 3.6T 229G 3.2T 7% /opt/sata-array

After the format I started transferring my data which slows down the sync, but transferring all my data will take a few days anyway so the overall timeline doesn’t really matter for me. Doing a cat /proc/mdstat shows me the status of the array:

Personalities : [linear] [multipath] [raid0] [raid1] [raid6] [raid5] [raid4] [raid10]
md0 : active raid6 sdf[5] sde[4] sdd[3] sdc[2] sdb[1] sda[0]
3907049984 blocks level 6, 64k chunk, algorithm 2 [6/6] [UUUUUU]
[======>..............] resync = 32.0% (312900864/976762496) finish=4727.0min speed=2340K/sec

unused devices: <none>

Short of having to setup a second computer to transfer the data, the entire process is very easy. I feel better knowing my data is reasonably safe with RAID 6 even though I don’t have a backup. Backing up that much data is just too expensive to be worthwhile.

Tags: , ,

Wordpress 2.7 Upgrade Issues

Posted by Cameron Stokes on December 14, 2008
upgrade, wordpress / No Comments

I decided to upgrade to Wordpress 2.7 despite my usual reservations in performing any type of upgrade.  Unfortunately, I was correct in my reservations and had a few issues during the upgrade.  Despite the very manual process of performing backups and installing the new version I still ran into some issues that I may have anticipated but nevertheless ran into.

After changing the wp-config.php file for my database I let the Wordpress script make the necessary database changes and then logged into the administration site.  I was quite impressed by the new interface but my enthusiasm soon faded when I tried to access my blog and was presented with a very unfriendly blank page.  After reading several different forum posts regarding various reasons for the blank pages experiences after upgrading, I went to the Themes page in the administration portion of the application and saw a message that my current theme wasn’t supported by 2.7 and that it had been disabled.  I was now back to the default Wordpress theme.  After googling I found that the MistyLook theme I had been using didn’t support the new Wordpress version, at least not yet.

Having the default theme I was able to see that the photos I had uploaded in my previous posts, weren’t working.  This was easy to fix as I had actually followed the backup instructions above and just copied the uploads folder back into the new install.  The next hiccup I rant into was that all of my plugins had disappeared.  I copied the plugins folder over from my backup, re-activated them and everything seemed fine, except I had to re-enter my site keys for WP-reCAPTCHA.

Now that everything seemed to be functional, I started looking for a new theme.  I settled on the Big City theme which I actually like better than my previous theme.

Big City Theme

Big City Screenshot

I removed the default logo and would like to eventually replace the skyline rendering with perhaps a rendering of the Atlanta skyline.  We’ll have to see how good my Photoshop skills are.

All in all the upgrade didn’t go too bad. I didn’t lose any data, only spent about an hour on the upgrade and fixing the issues, and am now on the latest and greatest version with a cool new theme. Some of the issues were probably due to me reading the upgrade instructinos too quickly but the upgrade process could probably be streamlined by the Wordpress developers.  Hopefully I won’t have to upgrade again for a while.

Tags: ,