Forgot your password?
typodupeerror

Comment: Re:Magic (Score 1) 366

by ByTor-2112 (#47883529) Attached to: The State of ZFS On Linux

You could add the 3TB drive to the pool, it just wouldn't be a part of the RAID-Z vdev and thus have limited redundancy. It would be RAID-0. But you could survive one failure in the original vdev. Any additional failure or loss of the new drive would result in total loss of data.

So... Backup, destroy pool, restore. Think ahead better the next time. Really, a good SAS JBOD controller is only a couple hundred bucks. Spend the money and plan your storage accordingly.

Comment: Re: Magic (Score 1) 366

by ByTor-2112 (#47883477) Attached to: The State of ZFS On Linux

OP is not talking about adding to a pool but replacing drives (zpool replace is a one-for-one replacement). You are correct in that one cannot add to an existing vdev, only replace drives. But you can add additional vdevs to a pool without a problem. They don't even have to have the same redundancy level (stupid idea).

Comment: Re:Moving to FreeBSD is probably more a ZFS thing (Score 1) 613

by ByTor-2112 (#47818577) Attached to: You Got Your Windows In My Linux

I've been on FreeBSD since 1999, and went "all in" on ZFS about 7 or 8 years ago. I can attest to the robustness of the system; it's incredibly stable. Definitely a reason to look beyond Linux. Most code should be pretty portable unless you are looking in /proc for a bunch of things, something which I has always appalled me.

Comment: Re: Baby steps (Score 1) 289

by ByTor-2112 (#47794995) Attached to: Hidden Obstacles For Google's Self-Driving Cars

Every time you start up your driverless car, are you going to click agree to an EULA that says you take full responsibility for the car's actions? Are you going to sue the guy who wrote the braking algorithm? The vision system? The granny detection module? The snow module? Would you write any of that code knowing it could kill people? Are the people who get injured going to sue the coders? The driver? The car manufacturer? Some of these questions were probably ready asked way back when cars were first invented but may have to be read dressed.

In my opinion it will never happen as a purely vehicle based solution. Why spend millions of dollars developing a new stoplight detection algorithm that will never be 100% accurate when you could simply add a 5 cent reflector to stoplights. Or some other bit of cheap tech that communicates with the cars. The driverless cars need roads designed to aid them.

Comment: network (Score 2) 152

by ByTor-2112 (#47549795) Attached to: What percentage of your media consumption is streamed?

I've been doing something similar for nearly a decade now. I started with a D-Link DSM-520 media streamer, then a WDTV, but eventually moved to XBMC and a custom built box to get the media compatibility I needed. Basically...

- The first rule of Netflix streaming is that they won't have the movie you want to see. Ever.
- WiFi is not a good option, especially for streaming HD video. You don't want the thing stuttering when you bring a date home or your kids are screaming for Finding Nemo.
- Streaming over NFS seems to have the best performance. Streaming via HTTP was unreliable, as was DLNA, MiniUPNP etc.
- Gigabit ethernet is your best option. Wire everything you can. If you can't get ethernet, use powerline networking.
- Don't cheap out on your hardware. I spent the money to get a 4U chassis with 16 3.5" hotswap bays, SAS backplane and redundant power supply. It sounds like a freight train but the reliability has been very, very good.
- Redundant storage is absolutely necessary. If you add up the time it takes to compile your media collection one video at a time, a storage failure could take months and months of downloading or re-encoding to recover from. There may even be some exotic content that just isn't available any more. If you are serious about it then you will find yourself using so much storage that a true "backup" is very expensive or even impossible, although with 3TB and 4TB drives available now that is not so true any more.
- Don't be afraid to rip and encode yourself. MakeMKV is a great piece of software and allowed me to remove AnyDVD HD from my workflow, which significantly streamlined the process. If you are handy with scripting, you can almost automate the entire process. I've automated the ripping process and the encoding process, but have not bothered to bridge the two yet... DVD's are apparently created by a team of monkeys and the disc structure is frequently completely broken. Blu-ray video tends to be very well done, but the audio streams vary and sometimes the discs are mastered with a bunch of fake stuff to "foil" rippers (I'm looking at you, Disney).

Comment: Re:The Seagate Squeak (Score 1) 444

by ByTor-2112 (#46030649) Attached to: Who Makes the Best Hard Disk Drives?

I have a long memory of failing WD drives, so I have been avoiding them like the plague for the last 6 years. It's only 2 data points, but:

- 8x1.5TB array seagates in a RAIDZ2 configuration, ran essentially 24x7 for 2 or 3 years with no failures
- 8x3TB array seagates in same configuration, been running for about 2 years with no failures.

Seems my experience is not the norm... Or maybe I need to cross that 3-year barrier. Shame I fill them up too fast to make it 3 years so far.

"Be *excellent* to each other." -- Bill, or Ted, in Bill and Ted's Excellent Adventure

Working...