Follow along with the video below to see how to install our site as a web app on your home screen.
Note: This feature may not be available in some browsers.
So the obvious question is: is a parity write considered to be a burst write?
Parity data is the same volume as the per drive volume of data (roughly) so if the data drives are being taxed then so is the parity drive. If the data you are writing is in bursts then the parity is in bursts, if the data is a constant stream so is the parity.
The problem would not be restore speed but slow backup speed.and if there is a lot of data will it take too long to restore let's say 40TB+?
Disk storage will never beat tape for price or density. It's more convenient because no manual intervention is required, so SMR beats density above regular drives.
The reason why I put that out there was based on the data capacity of LTO-6, which is 2.5TB raw, as opposed to 8TB for this drive. Also the SMR drive itself is $290-300, where as an LTO-6 drive is ~$2100; LTO-6 cartridges run to ~$35/tape.
Tape is $35 per 2.5TB, which is $14 per terabyte. The 8TB SMR drive is $37.50 per terabyte. SMR disk is 2.67 times the cost of tape.
The tape drive costs a couple grand, but amortizes out for meaningful library volumes. If you're only backing up a few tens of terabytes, SMR might be more competitive because of the cost of the drive. But we'd also have to assume you're moving the drives around; if you're keeping them in a chassis, we'd have to consider those costs, too.
The performance question is a bit different. The tapes, IIRC, can only be written to at about 150 megs/second. I'm sure the SMR drives can keep up with that, though they might struggle when using a file system that's SMR-ignorant.
I was thinking whether these SMR drives would be better in RAID4 where the parity stripe is stored on a non-SMR drive (or stored on multiple drives in RAID0 because you can't yet get a single 8TB non-SMR drive). With RAID5 the parity writes are distributed so all of the drives are going to suffer band rewrite penalty during rebuild, but with a RAID4 the bulk of the write operations will be on the parity drives instead where there is no penalty. Writes to the data stripe drives will still suffer the penalty but it should happen less often because there would be fewer writes to those drives.
The SMR penalty happens when writes aren't sequential and continuous, aren't aligned to the start of bands, or aren't band-sized. RAID rebuilds don't guarantee these things: the controller may decide to rebuild in any order, write housekeeping information, and might not have alignment and sizing that matches the drive.During a rebuild, you're reading from your remaining drives, to write to a new drive. There should be no SMR penalty.
These are shingled storage. Essentially, they're write once. If you need to re-write anything on the drive, you've got to re-record the whole drive. What commercial file systems support such drives?
Is this true? From what I've read it will re-write the band, not the platter or whole drive. Unless the 8TB drive is different...
See http://www.anandtech.com/show/7290/seagate-to-ship-5tb-hdd-in-2014-using-shingled-magnetic-recording
In terms of using these Seagate Archive Drives in a software raid (specifically snapraid) what was the consensus conclusion here? I heard:
1) These drives are good candidate to be "data drives" in a situation for media & other data that is written infrequently and read / streamed frequently.
2) I wasn't clear if these drives are good candidated for the parity drives in a SnapRaid setup. Should "Normal" or PMR drives be used for the parity drive?
Thanks