1) is this a good idea?
2) any of you are running vserver guests on iSCSI targets? Happy
with it?
Yes, we have been using iSCSI to hold vserver guests for a couple of
years now and are generally unhappy with it. Besides our general
distress at Nexenta, there is the constraint of the
Hello Bob Friesenhahn and List,
On August, 06 2011, 20:41 Bob Friesenhahn wrote in [1]:
I think that this depends on the type of hardware you have, how much
new data is written over a period of time, the typical I/O load on the
server (i.e. does scrubbing impact usability?), and how critical
The hardware ist SM-Board, Xeon, 16 GB reg RAM, LSI 9211-8i HBA,
6 x Hitachi 2TB Deskstar 5K3000 HDS5C3020ALA632.
Server is standing in the basement by 32°C
The HDs are filled to 80% and the workload ist only most reading.
Whats the best? Scrubbing every week, every second week once a
On 8/7/11 6:36 AM, Roy Sigurd Karlsbakk wrote:
That's why, back in 1992, the sliding window protocol was created
(http://tools.ietf.org/html/rfc1323), so that a peer won't wait for a TCP ACK
before resuming operation.
It was part of TCP _long_ before that (it was never as stupid as XMODEM
maximum memory page size and is limited to no more than 4KB. iSCSI
appears to acknowledge every individual block that is sent. That means
the most data one can stream without an ACK is 4KB. That means the
throughput is limited by the latency of the network rather than the
bandwidth.
I am
Hello Roy Sigurd Karlsbakk and List,
On August, 07 2011, 19:27 Roy Sigurd Karlsbakk wrote in [1]:
Generally, you can't scrub too often. If you have a set of striped
mirrors, the scrub shouldn't take too long. The extra stress on the
drives during scrub shouldn't matter much, drives are made
