Not a very friendly approach anyway if you ask me. I hope no species get the same idea with planet Earth as target for their research.

You must be new around here. Where did you get that low uid from?

Given the post you replied to, you must mean:
LTO6 is â40/6TB compressed.
4TB hdd is â130.
2TB hdd is â80.

Well, we have backups in Canada, Australia and England so we do not qualify with regards to the requirements because we do not have backups in any state.

I am a girl, you insensitive clod.

Running wp without at least a WAF in front of it, what could possibly go wrong?

yes brother, I am all with you!

I am a drummer too.

You are right about this. Once, a linux kernel update, or was it mdtools? was screwed. You would add a new partition to an linux MD raid array and it wouldn't sync the partition before putting it online ;-) This is where a good backup strategy comes into place.

Anyways, toying around with linux MD and cheap solutions makes you more creative in the long run IMHO.

Just keep your mind open please. There are plenty of approaches and trade-offs available and just as you said:

Furthermore, it depends on SLAs and such and having the best cost effective solution. As long as you know what you are doing and document it, you don't have to worry about covering your arse so much...

Who says I don't ALSO work for others and I don't know about more expensive solutions? I just don't brag about it mister Shaman ;-)

I know enough to know about people covering their arses, it is pretty common you know...

Yet, I never lost any data on the cheaper setup I run on the side.

Take care man!

Hello,

I am in a data center and I had email rejected by hotmail for no reasons (not on any rbl blacklist etc.). I solved it by masquerading outgoing mail for hotmail on another IP on a different subnet I own on my datacenter connection. I would try this first. You can also try to contact hotmail so they whitelist your IPs.

If your 5 IPs are on the same subnet and blacklisted by hotmail, I don't see any other solutions than routing your mail through an intermediate mail server. Have you tried relaying it through comcast MX? I can't imagine hotmail rejecting emails from all comcast subscribers.

Also, you probably have somebody sending spam on the same subnet as yours and hotmail seem to like to block /24 subnets. They should eventually unblock you if your subnet stop sending spam.

Exactly, use ZFS that does just that if you want to afford the extra memory. Use a fancy hardware raid controller that does that if you wish. I just use cheap drives and Linux MD. Do your research before commenting on setup you don't seem to know about. You don't have to brag about your hardware here and try to convince others to do as you do.

Didn't I mention in my first post: "Most people would say this is crazy but in my opinion,..."?

I do not see what was your point in replying to my posts anyway other than brag about using more expensive solutions and treat others that don't do just like you like idiots.

Oh, and while at it, RAID 1 doesn't have parity information!

I did not learn a single thing from your replies.

Take care nevertheless!

Good one! mke2fs -c -c

Thanks for pointing this out!

I suggest you do a little more research. If a sector was successfully written to and then 2 months later the drive hardware can't read from it, there is no way for the drive hardware to automagically correct the error and recover the data. The drive hardware then just increment the Current_Pending_Sector count. You could start by reading your own link but then again, you seem to have problems reading my own posts so your mileage may vary ;-)

Exactly, the first thing I thought about was this:

http://www.metrolyrics.com/i-p...

I know that. I run e2fsck -c -c (write+read test) to generate random pattern writes on the drives then read the data to make sure it is the same. If I put the drive back on line, e2fsck -c -c will always report 0 bad blocks and no timeouts will have occurred. I also check for timeouts in the logs.

Failed reads on a drive part of a RAID array will usually cause the drive to be kicked out of the RAID array after a timeout slowing down the machine. The strategy I suggested allow the drive hardware to indeed relocate the bad blocks and to bring Current_Pending_Sector to zero.

So, more or less:
1) Drive gets kicked out of the array.
2) Look for read timeouts in the logs
3) Use what I described until read timeouts vanish.
4) Keep an eye on smart data and further read timeouts to insure the drive has stabilized. I actually use cron scripts for that.