From: "Luis R. Rodriguez" <mcgrof@gmail.com>
To: Bartlomiej Zolnierkiewicz <bzolnier@gmail.com>
Cc: linux-kernel@vger.kernel.org,
Stephen Rothwell <sfr@canb.auug.org.au>,
Bob Copeland <me@bobcopeland.com>
Subject: Re: git pull on linux-next makes my system crawl to its knees and beg for mercy
Date: Fri, 18 Dec 2009 11:55:24 -0800 [thread overview]
Message-ID: <43e72e890912181155h444956a3tf228ddd8d281a9d3@mail.gmail.com> (raw)
In-Reply-To: <43e72e890912181119t53e01ec2y5dc8687d23f7a668@mail.gmail.com>
On Fri, Dec 18, 2009 at 11:19 AM, Luis R. Rodriguez <mcgrof@gmail.com> wrote:
> On Fri, Dec 18, 2009 at 9:38 AM, Bartlomiej Zolnierkiewicz
> <bzolnier@gmail.com> wrote:
>> On Friday 18 December 2009 06:26:29 pm Luis R. Rodriguez wrote:
>>
>>> on my kernel logs. Bewildered with this issue I set out to prove to
>>> myself this issue was not a 2.6.32 issue and booted other kernels,
>>> including Ubuntu's distro kernel on 2.6.31 and then later my own built
>>> fresh 2.6.27.41 kernel. The issue was reproducible on all three
>>> kernels!
>>>
>>> This lead me to believe this was a system / hard drive issue and
>>> embraced myself for a system fix. I yet needed to prove this was
>>
>> Just some hints for ruling out the system / hard drive problem.
>>
>> smartctl -a /dev/sdx is your friend for checking your disk (keep an eye
>> on anything suspicious like re-allocated sector count going up etc.)
>
> Sweet thanks, here's my current output, I'll try later after I get
> some day work done to pull linux-next and make it moan. Let me know if
> you see anything fishy.
<-- snip full log -->
> Also available at:
>
> http://bombadil.infradead.org/~mcgrof/logs/2009/12/smart-ctl-sda2.txt
>
>> It could be also fs related issue that shows up only under specific
>> conditions
>
> OK -- I see, I used a fresh new ext3, did not make the jump to ext4.
>
>> (i.e. almost full partition -- some file-systems starts to
>> crawl when the amount of available free space gets low).
>
> Got it, thanks, so partition has a lot of room.
>
> mcgrof@tux ~ $ df -h
> Filesystem Size Used Avail Use% Mounted on
> /dev/sda2 91G 43G 44G 50% /
>
> Also ony have one partition.
GSmartControl is very cool, just ran the short self test and it passed
without issues. I'll now run the extended self tests. I'll not that
right after the self test I had to checkout the 2.6.32.y branch on
hpa's tree and noticed similar type of slow down as I did with pulling
linux-next. Only thing with linux-next is it takes ages complete which
just makes waiting unbearable. This all makes me suspect its something
else. But lets seee what these results on the GSmartControl yield.
Luis
next prev parent reply other threads:[~2009-12-18 19:55 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-18 17:26 Luis R. Rodriguez
2009-12-18 17:38 ` Bartlomiej Zolnierkiewicz
2009-12-18 19:19 ` Luis R. Rodriguez
2009-12-18 19:55 ` Luis R. Rodriguez [this message]
2009-12-18 20:51 ` Luis R. Rodriguez
2009-12-18 21:13 ` Luis R. Rodriguez
2009-12-18 21:56 ` Stephen Rothwell
2009-12-18 22:03 ` Luis R. Rodriguez
2009-12-23 15:27 ` Denys Vlasenko
2009-12-23 16:20 ` Luis R. Rodriguez
2009-12-23 17:11 ` Denys Vlasenko
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=43e72e890912181155h444956a3tf228ddd8d281a9d3@mail.gmail.com \
--to=mcgrof@gmail.com \
--cc=bzolnier@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=me@bobcopeland.com \
--cc=sfr@canb.auug.org.au \
/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
all inboxes | Powered by JetHome®