From: Simon Mcnair <simonmcnair@gmail.com>
To: Phil Turmel <philip@turmel.org>
Cc: NeilBrown <neilb@suse.de>,
"linux-raid@vger.kernel.org" <linux-raid@vger.kernel.org>
Subject: Re: Linux software RAID assistance
Date: Thu, 17 Feb 2011 13:56:15 +0000 [thread overview]
Message-ID: <6037962689649361915@unknownmsgid> (raw)
In-Reply-To: <4D5D2723.1010101@turmel.org>
Phil, I think I need to connect them to the crippled machine directly,
I was just trying to leave it alone, I know that doesn't make much
sense but I'm more familiar with windows than Linux. The cards that I
have are all connected at gigabit and bonded. That machine has two
ports, so does the other. I'm running two asus p6ts (1 deluxe and 1
se) with i7 920's
I cant understand why it's so slow though I have seen some reports
that the supermicro card is quite slow.
Simon
Ps thanks for the bugfixes and updates
Simon
On 17 Feb 2011, at 13:48, Phil Turmel <philip@turmel.org> wrote:
> On 02/17/2011 08:26 AM, Simon Mcnair wrote:
>> Phil,
>> After a couple of attempts I realised that all I needed to do was
>> ./backup.sh sdi rather than specifying ./backup.sh /dev/sdi schoolboy
>> error huh, rtfm.
>>
>> I tried modifying the code, so I could kick them all off at once, but
>> I wanted to check that this would work from a multithreaded/sane
>> perspective (yes I know it's a bit of IO, but iotop seems to infer I'm
>> only getting 10M/s throughput from the disk anyway).
>
> That sounds suspiciously like a 100 meg ethernet bottleneck, so parallel operation won't help. If so, this'll take a very long time.
>
>> is this code kosha ?
>
> Looks pretty good. I've attached a slight update with your changes and a bugfix.
>
>> #! /bin/bash
>> #
>> function usage() {
>> printf "Usage:\n\t%s devname\n\n" "`basename \"$0\"`"
>> printf "'devname' must be a relative path in /dev/ to the
>> desired block device.\n"
>> exit 1
>> }
>>
>> # Verify the supplied name is a device
>> test -b "/dev/$1" || usage
>>
>> # Convert path separators and spaces into dashes
>> outfile="`echo \"$1\" |sed -r -e 's:[ /]+:-:g'`"
>>
>> # Create a side-stream for computing the MD5 of the data read
>> fifo=`mktemp -u`
>> mkfifo $fifo || exit
>> md5sum -b <$fifo >$2/$outfile.md5 &
>>
>> # Read the device and compress it
>> dd if="/dev/$1" bs=1M | tee 2>$fifo | gzip >$2/$outfile.gz
>>
>> # Wait for the background task to close
>> wait
>>
>> I was a little concerned as I didn't see the hdd drive LED light up
>> for my attempt even though the file was growing nicely on my CIFS
>> share. I'm dumping it on the 5x2TB disks (JBOD) in my windows 7 box
>> as my Thecus is not a happy chappy and I need time to mount the DOM
>> module in another machine to find out why.
>
> If you're willing to dismantle the thecus, directly connecting its drives to your crippled system will make things go much faster. You've got four empty motherboard SATA ports. You just have to watch out for the power load.
>
> Phil
> <block2gz.sh>
next prev parent reply other threads:[~2011-02-17 13:56 UTC|newest]
Thread overview: 64+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-10 16:16 Linux software RAID assistance Simon McNair
2011-02-10 18:24 ` Phil Turmel
2011-02-15 4:53 ` NeilBrown
2011-02-15 8:48 ` Simon McNair
2011-02-15 14:51 ` Phil Turmel
2011-02-15 19:04 ` Simon McNair
2011-02-15 19:37 ` Phil Turmel
2011-02-15 19:45 ` Roman Mamedov
2011-02-15 21:09 ` Simon McNair
2011-02-17 15:10 ` Simon Mcnair
2011-02-17 15:42 ` Roman Mamedov
2011-02-18 9:13 ` Simon McNair
2011-02-18 9:38 ` Robin Hill
2011-02-18 10:38 ` Simon Mcnair
2011-02-19 11:46 ` Jan Ceuleers
2011-02-19 12:40 ` Simon McNair
2011-02-19 17:37 ` Jan Ceuleers
2011-02-16 13:51 ` Simon McNair
2011-02-16 14:37 ` Phil Turmel
2011-02-16 17:49 ` Simon McNair
2011-02-16 18:14 ` Phil Turmel
2011-02-16 18:18 ` Simon McNair
2011-02-16 18:22 ` Phil Turmel
2011-02-16 18:25 ` Phil Turmel
2011-02-16 18:52 ` Simon McNair
2011-02-16 18:57 ` Phil Turmel
2011-02-16 19:07 ` Simon McNair
2011-02-16 19:10 ` Phil Turmel
2011-02-16 19:15 ` Simon McNair
2011-02-16 19:36 ` Phil Turmel
2011-02-16 21:28 ` Simon McNair
2011-02-16 21:30 ` Phil Turmel
2011-02-16 22:44 ` Simon Mcnair
2011-02-16 23:39 ` Phil Turmel
2011-02-17 13:26 ` Simon Mcnair
2011-02-17 13:48 ` Phil Turmel
2011-02-17 13:56 ` Simon Mcnair [this message]
2011-02-17 14:34 ` Simon Mcnair
2011-02-17 16:54 ` Phil Turmel
2011-02-19 8:43 ` Simon Mcnair
2011-02-19 15:30 ` Phil Turmel
[not found] ` <AANLkTinOXJWRw_et2U43R_T9XPBzQLnN56Kf2bOAz=_c@mail.gmail.com>
2011-02-19 16:19 ` Phil Turmel
2011-02-20 9:56 ` Simon Mcnair
2011-02-20 19:50 ` Phil Turmel
2011-02-20 23:17 ` Simon Mcnair
2011-02-20 23:39 ` Phil Turmel
2011-02-22 17:12 ` Simon Mcnair
2011-02-22 17:14 ` Simon Mcnair
2011-02-22 18:23 ` Phil Turmel
2011-02-22 18:36 ` Simon McNair
2011-02-22 19:06 ` Phil Turmel
2011-02-18 9:31 ` Simon Mcnair
2011-02-18 13:16 ` Phil Turmel
2011-02-18 13:21 ` Roberto Spadim
2011-02-18 13:26 ` Phil Turmel
2011-02-18 13:29 ` Simon Mcnair
2011-02-18 13:34 ` Phil Turmel
2011-02-18 14:12 ` Simon McNair
2011-02-18 16:10 ` Phil Turmel
2011-02-18 16:38 ` Roberto Spadim
[not found] ` <AANLkTi=RmR5nVnmFLuqK5anHc3WDPxjuYjitT6+5wAqS@mail.gmail.com>
2011-02-20 18:48 ` Phil Turmel
2011-02-20 19:25 ` Simon Mcnair
2011-02-19 8:49 ` Simon Mcnair
2011-02-16 13:56 ` Simon McNair
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=6037962689649361915@unknownmsgid \
--to=simonmcnair@gmail.com \
--cc=linux-raid@vger.kernel.org \
--cc=neilb@suse.de \
--cc=philip@turmel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).