<br><br><div class="gmail_quote">On Mon, Oct 25, 2010 at 12:00 PM, <span dir="ltr"><<a href="mailto:kwlug-disc-request@kwlug.org">kwlug-disc-request@kwlug.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
Send <a href="http://kwlug-disc_kwlug.org" target="_blank">kwlug-disc_kwlug.org</a> mailing list submissions to<br>
<a href="mailto:kwlug-disc@kwlug.org">kwlug-disc@kwlug.org</a><br>
<br>
To subscribe or unsubscribe via the World Wide Web, visit<br>
<a href="http://astoria.ccjclearline.com/mailman/listinfo/kwlug-disc_kwlug.org" target="_blank">http://astoria.ccjclearline.com/mailman/listinfo/kwlug-disc_kwlug.org</a><br>
or, via email, send a message with subject or body 'help' to<br>
<a href="mailto:kwlug-disc-request@kwlug.org">kwlug-disc-request@kwlug.org</a><br>
<br>
You can reach the person managing the list at<br>
<a href="mailto:kwlug-disc-owner@kwlug.org">kwlug-disc-owner@kwlug.org</a><br>
<br>
When replying, please edit your Subject line so it is more specific<br>
than "Re: Contents of <a href="http://kwlug-disc_kwlug.org" target="_blank">kwlug-disc_kwlug.org</a> digest..."<br>
<br>
<br>
Today's Topics:<br>
<br>
1. Re: Media errors on a USB disk (Eric Gerlach)<br>
2. Re: Fast transfer protocol? (unsolicited)<br>
3. Re: Fast transfer protocol? (John Johnson)<br>
4. screen is keen (Richard Weait)<br>
<br>
<br>
----------------------------------------------------------------------<br>
<br>
Message: 1<br>
Date: Sun, 24 Oct 2010 13:06:37 -0400<br>
From: Eric Gerlach <<a href="mailto:eric%2Bkwlug@gerlach.ca">eric+kwlug@gerlach.ca</a>><br>
To: KWLUG discussion <<a href="mailto:kwlug-disc@kwlug.org">kwlug-disc@kwlug.org</a>><br>
Subject: Re: [kwlug-disc] Media errors on a USB disk<br>
Message-ID:<br>
<AANLkTinUBGGz1sJmsfkdaAsgwUvnL6HvgkB50=<a href="mailto:ZXgNpt@mail.gmail.com">ZXgNpt@mail.gmail.com</a>><br>
Content-Type: text/plain; charset=ISO-8859-1<br>
<br>
On Sun, Oct 24, 2010 at 10:25 AM, Bob Jonkman <<a href="mailto:bjonkman@sobac.com">bjonkman@sobac.com</a>> wrote:<br>
> This is why I wonder about Spinrite. ?While it seems to be an awesome<br>
> program, it DOES pay attention to partition tables and partitions, so it's<br>
> not just checking the raw sectors on the disk. But it checks an ext3<br>
> partition just as readily as an NTFS partition.<br>
<br>
I don't know why it allows that option either... I've only ever run it<br>
on entire disks, and don't know why you would want otherwise. It<br>
definitely operates on the block level, though.<br>
<br>
> FWIW, I've never managed to recover a damaged drive with Spinrite. ?Either<br>
> the drives I checked aren't badly enough damaged, so Spinrite indicates<br>
> they're good, or the drive is so badly damaged that even Spinrite can't read<br>
> it. ?I've had a drive that banged its heads against the backstop, run<br>
> Spinrite on it for 30 days continuously, and while Spinrite marked most of<br>
> the drive as "Bad" it didn't recover a thing.<br>
<br>
What's interesting is that because of the way SpinRite does things at<br>
Level 4 (read, invert, write, read, invert, write, read), it will<br>
sometimes cause the drive to catch sectors that are bad, but the drive<br>
didn't realise it. In the story I submitted to Security Now (which<br>
got read on the air twice), when SpinRite ran it didn't do any<br>
"DynaStat" recovery. But the drive worked afterwards. So you don't<br>
always *see* it working. Sometimes it just helps the drive out, and<br>
since the drive doesn't say "Thank You," it can't tell you it did<br>
anything.<br>
<br>
I will agree though, that many of the times a user comes to me and<br>
says "I think my HD is bad," the drive is too far gone for anything.<br>
<br>
Cheers,<br>
<br>
Eric<br>
<br>
<br>
<br>
------------------------------<br>
<br>
Message: 2<br>
Date: Sun, 24 Oct 2010 14:35:58 -0400<br>
From: unsolicited <<a href="mailto:unsolicited@swiz.ca">unsolicited@swiz.ca</a>><br>
To: KWLUG discussion <<a href="mailto:kwlug-disc@kwlug.org">kwlug-disc@kwlug.org</a>><br>
Subject: Re: [kwlug-disc] Fast transfer protocol?<br>
Message-ID: <<a href="mailto:4CC47C8E.6020608@swiz.ca">4CC47C8E.6020608@swiz.ca</a>><br>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed<br>
<br>
Paul Nijjar wrote, On 10/24/2010 12:41 AM:<br>
<br>
> So I ended up testing with a program called iperf<br>
> (<a href="http://iperf.sourceforge.net" target="_blank">http://iperf.sourceforge.net</a>) which appears to be a pretty standard<br>
> network testing tool. Because I am lazy I used precompiled versions,<br>
> which meant that there were version issues between the Windows version<br>
> (1.70) and the version on my Knoppix LiveCD (2.0.3 or something).<br>
<br>
Looks like 2.0.4-1 is in the cygwin repository.<br>
<br>
> I can pretty much max out my gigabit connection using iperf and two<br>
> Windows servers with built-in gigabit cards. Any other combination of<br>
> Windows/Linux maxes out at about 60% usage.<br>
><br>
> Samba is indeed slow. I get better throughput with an FTP server. Disk<br>
> does indeed appear to be a limiting factor.<br>
<br>
Any chance you accumulated numbers for standard windows file sharing?<br>
Differences would be interesting - would mean there's some<br>
efficiencies gained within the windows code. No differences would be<br>
reassuring, and indicate that 'file sharing' is whatever (speed) it is.<br>
<br>
> On at least one machine (one with Windows and Linux) I found that<br>
> something in the operating system and/or version of iperf makes the<br>
> results pretty different.<br>
<br>
Can anyone comment ... how much of this difference might be<br>
attributable to proprietary windows (netcard?) drivers?<br>
<br>
- I'm guessing there are no proprietary linux drivers available to be<br>
played with in Paul's test. (Unlike, say, proprietary nvidia drivers.)<br>
<br>
<br>
<br>
------------------------------<br>
<br>
Message: 3<br>
Date: Sun, 24 Oct 2010 14:50:39 -0400<br>
From: John Johnson <<a href="mailto:jvj@golden.net">jvj@golden.net</a>><br>
To: KWLUG discussion <<a href="mailto:kwlug-disc@kwlug.org">kwlug-disc@kwlug.org</a>><br>
Subject: Re: [kwlug-disc] Fast transfer protocol?<br>
Message-ID: <<a href="mailto:201010241850.o9OIoatu027381@smtp2.execulink.net">201010241850.o9OIoatu027381@smtp2.execulink.net</a>><br>
Content-Type: text/plain; charset="us-ascii"; format=flowed<br>
<br>
At 00:41 2010-10-24, you wrote:<br>
>I can pretty much max out my gigabit connection using iperf and two<br>
>Windows servers with built-in gigabit cards. Any other combination of<br>
>Windows/Linux maxes out at about 60% usage.<br>
<br>
Congrats. IMHO This was no easy feat.<br>
<br>
In my earlier post I did say that I doubted that with "a PC" meaning<br>
a single PC (inferring but not stating at least a receiver /<br>
transmitter pair) one would be hard pressed to get sustained data<br>
transfers anywhere near 1 Gigabit/sec. I thought that multiple PCs<br>
would be needed to get the aggregate data rate up to those limits.<br>
And a software-only utility involves the fewest internal components,<br>
i.e. CPU, RAM, busses and bridges, and of course the network "cards".<br>
<br>
John Johnson<br>
<br>
<br>
<br>
<br>
------------------------------<br>
<br>
Message: 4<br>
Date: Mon, 25 Oct 2010 07:40:20 -0400<br>
From: Richard Weait <<a href="mailto:richard@weait.com">richard@weait.com</a>><br>
To: KWLUG discussion <<a href="mailto:kwlug-disc@kwlug.org">kwlug-disc@kwlug.org</a>><br>
Subject: [kwlug-disc] screen is keen<br>
Message-ID:<br>
<<a href="mailto:AANLkTin2Gy50UsWFzrJdASt1OJS50VPkW227QA406bDp@mail.gmail.com">AANLkTin2Gy50UsWFzrJdASt1OJS50VPkW227QA406bDp@mail.gmail.com</a>><br>
Content-Type: text/plain; charset=ISO-8859-1<br>
<br>
You might remember a presentation on the GNU utility, screen, from a<br>
few meeting back. You might have thought, "sure that seems nice and<br>
all, but how do I add an animated wallpaper to it?"<br>
<br>
Or you might have thought, "hunh? Paul says it gets confused by sudo.<br>
I should probably remember that so it doesn't cause me trouble in the<br>
future."<br>
<br>
Let this be a lesson to you. Screen does get confused by sudo, so ssh<br>
in as the user who should be using screen. Thanks Paul for that tip<br>
that, had I remembered earlier, would have saved me ten minutes.<br>
Without your tip, I could have wasted hours.<br>
<br>
So screen is keen. I found it super-useful last week during a<br>
conference call regarding some server stuff. A developer and I used<br>
the same screen to work on the project via the -x option. We each<br>
ssh'd in to the server as the same user. I started a screen session.<br>
He used screen -x to attach to the existing screen session. Then we<br>
could each see what the other was typing, and all the results from<br>
those commands. This was a very handy way for two people with<br>
different skill sets to collaborate on a project. When combined with<br>
a telephone call for a simultaneous voice connection, it felt very<br>
productive.<br>
<br>
Plus the whacky, "I'm going to press enter when you are typing your<br>
password" hijinx.<br>
<br>
So, it was good fun. Screen is Keen. Paul's presentation saved me some time.<br>
<br>
Apparently screen will let different users attach to the same session,<br>
but I haven't tried that yet.<br></blockquote><div><br><br> Test <br></div><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<br>
<br>
<br>
------------------------------<br>
<br>
_______________________________________________<br>
<a href="http://kwlug-disc_kwlug.org" target="_blank">kwlug-disc_kwlug.org</a> mailing list<br>
<a href="http://kwlug-disc_kwlug.org" target="_blank">kwlug-disc_kwlug.org</a>@<a href="http://kwlug.org" target="_blank">kwlug.org</a><br>
<a href="http://astoria.ccjclearline.com/mailman/listinfo/kwlug-disc_kwlug.org" target="_blank">http://astoria.ccjclearline.com/mailman/listinfo/kwlug-disc_kwlug.org</a><br>
<br>
<br>
End of <a href="http://kwlug-disc_kwlug.org" target="_blank">kwlug-disc_kwlug.org</a> Digest, Vol 23, Issue 42<br>
****************************************************<br>
</blockquote></div><br><div style="visibility: hidden; display: inline;" id="avg_ls_inline_popup"></div><style type="text/css">#avg_ls_inline_popup { position:absolute; z-index:9999; padding: 0px 0px; margin-left: 0px; margin-top: 0px; width: 240px; overflow: hidden; word-wrap: break-word; color: black; font-size: 10px; text-align: left; line-height: 13px;}</style>