Enough is enough. You can either join BAARF. Or not.
RAID-5 Write Penalty
"...If you later modify the data block it recalculates the parity by subtracting the old block and adding in the new version then in two separate operations it writes the data block followed by the new parity block. To do this it must first read the parity block from whichever drive contains the parity for that stripe block and reread the unmodified data for the updated block from the original drive. This read-read-write-write is known as the RAID5 write penalty since these two writes are sequential and synchronous the write system call cannot return until the reread and both writes complete, for safety, so writing to RAID5 is up to 50% slower than RAID0 for an array of the same capacity. (Some software RAID5's avoid the re-read by keeping an unmodified copy of the orginal block in memory.)"
RAID-5 Drive Failure "Now if a drive in the RAID5 array dies, is removed, or is shut off data is returned by reading the blocks from the remaining drives and calculating the missing data using the parity, assuming the defunct drive is not the parity block drive for that RAID block. Note that it takes 4 physical reads to replace the missing disk block (for a 5 drive array) for four out of every five disk blocks leading to a 64% performance degradation until the problem is discovered and a new drive can be mapped in to begin recovery."
Raid-5 Failure Rate Increases As the number of disks in a RAID 5 group increases, the Mean Time Between Failures (MTBF, the reciprocal of the failure rate) can become lower than that of a single disk.
RAID-5 is EVIL! Never Ever, EVER use RAID-5, You will LOSE DATA! RAID-1 or RAID-10 only for production use.
If you are thinking about Raid-5, forget it, just stripe your drives in a RAID-0 and enjoy the performance benefits and keep frequent good backups and test your restores.
1) Lack of GigE switch between the machines, or a really really poor GigE switch (80 mbps - that sounds like Fast Ethernet) 2) Poor GigE chipset(s) on the mobo. 3) Poor CPU - rsync and scp encrypt the transfer which uses alot of cpu at each end. Also, GigE generates a fantastic number of interrupts/sec. Intel's Pro/1000 GT has an "Interrupt Moderation" feature to help with that. 4) Your hard drive speed. GigE is faster than most single hard drives. Seagate's Savvio 15k could maybe push it, with a STR of 117-97 MBps. A 10k Raptor is only 84 MB/s STR.
Run iPerf between two machines and see what your hardware can really do. (Quick tutorial, run `iperf -s` on one machine and `iperf -c {ip of other machine}` on the other. Then reverse the roles. FYI for a Lan, no IP Stack tuning is necessary)
Yes, trying to get what Gig-E promises has pissed me off too.
Anyway, you do realize what local root exploit is don't you? A normal user mode program could run this and gain root access. Say you had SSH running under uid for nobody, Now normally a hole in that would mean that the cracker just has access equiv to 'nobody', but with this, 'nobody', can become root.
Or a more likely scenario, say you were running a browser with a remote code exploit. Normally the browser would only have access as your user account, but with this now your browser has root access.._.
I submit to you, my fellow slashdotters, the parent post for the most ironic post ever. Such a long, insightful post about how to do a successful software deployment, and then not clicking preview to realize that the formatting of your list is all screwed up. Only posting as an A/C saved you a year of personal shame.
How about just adding cheats as elements to the game? Players like radar? Add it. The ability to see through walls? Auto aim, auto trigger? Make them power ups. Don't fight it, integrate it.
That's it! The opterons produce heat, which boils water which runs the turbines to generate electricity to power the opterons! My god man! It's the Google perpetual motion machine!
If you copied a Steak Dinner, would the fact that it would be in the sewer in a few hours have any relevance to making the copy?
Stealing a Steak dinner deprives someone of a Steak dinner. Copying the Steak dinner doesn't deprive anyone of the original Steak dinner, it deprives someone of something else.
That's the whole copying argument; by making a copy, what claims of loss can be made, by whom, do the claims make sense, and can the same claims be made in every copying instance?
/now I feel like a Steak Dinner. Where can I get a good copy, high quality original, lossless encoding preferred.
Oh god, I'm gonna die. I have never laughed like that. The eBay feedback '...never had computer equipment smell unholy before', the refund 'You gotta believe me...'
Slashdot Mirror
Wouldn't Lastpass Enterprise's Shared Folders suffice for that?
Yes, and install a Big Red Switch.
http://www.baarf.com/
Enough is enough.
You can either join BAARF. Or not.
RAID-5 Write Penalty
"...If you later modify the data block it recalculates the parity by subtracting the
old block and adding in the new version then in two separate operations it
writes the data block followed by the new parity block. To do this it must
first read the parity block from whichever drive contains the parity for
that stripe block and reread the unmodified data for the updated block from
the original drive. This read-read-write-write is known as the RAID5 write
penalty since these two writes are sequential and synchronous the write
system call cannot return until the reread and both writes complete, for
safety, so writing to RAID5 is up to 50% slower than RAID0 for an array of
the same capacity. (Some software RAID5's avoid the re-read by keeping an
unmodified copy of the orginal block in memory.)"
RAID-5 Drive Failure
"Now if a drive in the RAID5 array dies, is removed, or is shut off data is
returned by reading the blocks from the remaining drives and calculating
the missing data using the parity, assuming the defunct drive is not the
parity block drive for that RAID block. Note that it takes 4 physical
reads to replace the missing disk block (for a 5 drive array) for four out
of every five disk blocks leading to a 64% performance degradation until
the problem is discovered and a new drive can be mapped in to begin
recovery."
Raid-5 Failure Rate Increases
As the number of disks in a RAID 5 group increases, the Mean Time Between Failures (MTBF, the reciprocal of the failure rate) can become lower than that of a single disk.
Why RAID 5 stops working in 2009
HTH,
HAND.
When not running it's purpose built program, let it run Electric Sheep! (The idea being that the cluster is "sleeping")
Great! Does that mean we might see a 64-bit plug sooner rather than later? We've been waiting over 5 years!
RAID-5 is EVIL! Never Ever, EVER use RAID-5, You will LOSE DATA! RAID-1 or RAID-10 only for production use.
If you are thinking about Raid-5, forget it, just stripe your drives in a RAID-0 and enjoy the performance benefits and keep frequent good backups and test your restores.
Why RAID 5 stops working in 2009
Why aren't disk reads more reliable?
End of Raid 5
finally, BAARF - Battle Against ANY Raid Five BAARF
HTH, HAND, don't cry.
Your transfer limit is either:
1) Lack of GigE switch between the machines, or a really really poor GigE switch (80 mbps - that sounds like Fast Ethernet)
2) Poor GigE chipset(s) on the mobo.
3) Poor CPU - rsync and scp encrypt the transfer which uses alot of cpu at each end. Also, GigE generates a fantastic number of interrupts/sec. Intel's Pro/1000 GT has an "Interrupt Moderation" feature to help with that.
4) Your hard drive speed. GigE is faster than most single hard drives. Seagate's Savvio 15k could maybe push it, with a STR of 117-97 MBps. A 10k Raptor is only 84 MB/s STR.
Run iPerf between two machines and see what your hardware can really do. (Quick tutorial, run `iperf -s` on one machine and `iperf -c {ip of other machine}` on the other. Then reverse the roles. FYI for a Lan, no IP Stack tuning is necessary)
Yes, trying to get what Gig-E promises has pissed me off too.
Troll?
._.
Anyway, you do realize what local root exploit is don't you? A normal user mode program could run this and gain root access. Say you had SSH running under uid for nobody, Now normally a hole in that would mean that the cracker just has access equiv to 'nobody', but with this, 'nobody', can become root.
Or a more likely scenario, say you were running a browser with a remote code exploit. Normally the browser would only have access as your user account, but with this now your browser has root access.
I submit to you, my fellow slashdotters, the parent post for the most ironic post ever. Such a long, insightful post about how to do a successful software deployment, and then not clicking preview to realize that the formatting of your list is all screwed up. Only posting as an A/C saved you a year of personal shame.
How about just adding cheats as elements to the game? Players like radar? Add it. The ability to see through walls? Auto aim, auto trigger? Make them power ups. Don't fight it, integrate it.
It's a good story, but only a story; she took a guided tour like anyone else entering the area: http://en.wikipedia.org/wiki/Elena_Filatova
That's it! The opterons produce heat, which boils water which runs the turbines to generate electricity to power the opterons! My god man! It's the Google perpetual motion machine!
If you copied a Steak Dinner, would the fact that it would be in the sewer in a few hours have any relevance to making the copy?
/now I feel like a Steak Dinner. Where can I get a good copy, high quality original, lossless encoding preferred.
Stealing a Steak dinner deprives someone of a Steak dinner. Copying the Steak dinner doesn't deprive anyone of the original Steak dinner, it deprives someone of something else.
That's the whole copying argument; by making a copy, what claims of loss can be made, by whom, do the claims make sense, and can the same claims be made in every copying instance?
Oh god, I'm gonna die. I have never laughed like that. The eBay feedback '...never had computer equipment smell unholy before', the refund 'You gotta believe me...'
Yes, it reads like you could throw it across the room and it would get up and keep going. Not sure if it could fall on purpose (seems kinda against the idea). OTOH, it can do wicked katas. (Just needs the programming like the dances) As well as walking on two legs, if QRIO does lose its balance, it reacts to protect itself against the impact. And after it falls, QRIO checks front, back, left and right, and gets back up, by itself.