Jump to content

BRiT

Members
 View Profile  See their activity

  • Posts

    6,582

  • Joined

  • Days Won

    8

 Content Type 

Everything posted by BRiT

  1. BRiT
    Alright, here's your full post: I do not see "for me" in there at all. You also stated it gets even worse if you have WD Greens. Was that not a reference to the WEADS / WEARS ?
  2. BRiT
    Yes, really. Reread the following statement which seems aimed at all GPs.
  3. BRiT
    Well your statement seemed to be aimed at all WD GP drives. Mine are the older EADS.
  4. BRiT
    terrastrife, I going to have to refute your claims. My array has a final parity check speed of 75 MB/s and I am using 3 WD Green 2TB drives. They start off at over 100 MB/sec. That puts the difference in speed from 95 MB/s to 75 MB/s a drop of about 22% {the math: (1 - (75/95)) * 100 }, which is nowhere close to your claimed 50% performance loss. Perhaps your drop in performance is from the adding of another drive, regardless of it's type.
  5. BRiT
    IIRC, a flaw in your trivial solution is the partition table is written at the very beginning of the drive, as is the filesystem tables.
  6. BRiT
    Interesting idea, but how would you suggest handling the following situation: 1) replacing a failed Data Drive X with a larger Data Drive Y, where size(y) > size(x). You've made this typical and likely scenario rather complex.
  7. BRiT
    They do not, at least not by emHttp.
  8. BRiT
    You can run multiple preclear_discs on the server, either open multiple telnet/ssh terminals or on the physical console.
  9. BRiT
    Anyone have a clue why this may be? Most likely it's due to a bug/feature in the MB BIOS implementation of S3.
  10. BRiT
    I think you at least want to grep for the actual network interface. If you don't, you may never go to sleep because of non-network traffic on the loopback device. The cut may not be needed, but I wanted to show some advanced possibilities for determining bytes send and received.
  11. BRiT
    That includes information for loopback, which isn't purely network activity. Standard unRAID tends to only support a single NIC so it would be: NetSnapshot=$(cat /proc/net/dev | egrep eth0 | cut -d: -f2) NetBytesRecv=$(echo $NetSnapshot | cut -d\ -f1) NetBytesTran=$(echo $NetSnapshot | cut -d\ -f9) The last two lines are 'cut -d\[space][space]-f#'
  12. BRiT
    uuuhmmm? Is that a compile yourself kinda thing? Yes, exactly.
  13. BRiT
    That's just the way Linux's libata works. The 3G / 1.5G Sata only refers to the maximum burst rate allowed. No disk's can sustain that speed, not even SSDs.
  14. BRiT
    One of your disks is running in ATA/33 mode, but it's one you're not using in the array. Your 1TBand 2TB WD drives are set as UDMA/133 and 3G SATA.
×
×
  • Create New...