Saturday, April 18, 2009

Good news and bad news...

Good news: I was able to tame Drobo to be friends with FreeNAS.

Long story short (assuming Drobo is on /dev/da0):
gpt destroy /dev/da0
gpt create /dev/da0
gpt add -t linux /dev/da0
gpt show /dev/da0
glabel label drobo1 /dev/da0p1
mke2fs -r0 -L Drobo01 -i 262144 -m0 /dev/da0p1


That allows Drobo to properly understand what has been deleted and whatnot.

Bad news:

IT GETS HOT!!!

I put four drives in it and started writing data. I made a mistake of putting the front cover on...

When I took the cover off and touched the drives to check, THEY BURNED MY FINGERS.



The fan was blowing all the time... So it's not a fan failure.

I think that's about it. No more Drobo for me. No way in hell I'm keeping a device that gets this hot!

My measly DriveStations don't do that even!

Wednesday, April 15, 2009

UFS smoke test

So my current setup is:

* My home NAS server: Mac Mini running FreeNAS (which is based on FreeBSD)
* 2 x Buffalo DriveStation Duo (USB2.0) with 2 750Gb drives each, connected to the abovementioned Mac Mini. They are just standalone drives, no RAID, so I'm sorta worried, hence Drobo.

I mean to migrate date from those drives to Drobo (one drive at a time)

So the first smoke test: I'm slipping a couple of spare 250Gb drives into Drobo, hooking it up to Mini (lovingly nicknamed "Brick"), formatting Drobo as UFS (FreeBSD's native filesystem) and copying a 50Gb bunch of data to it. Then deleting it and copying again. Lather, rinse, repeat five times. The theory is that the Drobo will not recognize that the data has been deleted, and at the end of this excersize it will think it's 100% full (5 x 50Gb = 250Gb. With only two drives, Drobo has only one drive's capacity, as the other one is used for redundancy.)

What this is all about

In our age of growing personal digital libraries, backing data up is quite important. I've been shopping around for a backup solution for quite a while, but everything I found to date has is disadvantages. The biggest thing about RAID storage is that it's not future-proof: you can't upgrade it one disk at a time, you have to ditch the whole thing at once, and that involves moving mountains of data around. Do you have any idea how long it takes to transfer 4TB? Ouch.

So I was looking at the neat little device called Drobo. It connects to the computer as a standard USB mass storage device, but in fact is a sparse storage array, consisting of up to 4 drives up to 2Gb each, redundant and single disk failure-tolerant. It's visible as a 2Gb disk (or a few of them if total amount of storage ends up being larger than that). Almost a miracle huh?

Well, there's nothing perfect in the world. Such "sparse storage" devices have a little problem: in order to accurately track their contents, they need to be able to tell apart the blocks that contain current data (and thus must be preserved) from the blocks that contain the data from the files that have been deleted (and may be overwritten). To do so, the device must understand the logic of the overlying filesystem. And Drobo understands FAT32 and NTFS, and, secretly, ext3. But the problem is, my OS of choice is FreeBSD with its own UFS filesystem. I searched and searched and was not able to find anything useful regarding "Drobo + FreeBSD" (or Drobo + NFS, for that matter) on the net. So I didn't have a choice but to buy a Drobo and try it all for myself...