From: "Lars Täuber" <taeuber@bbaw.de>
To: Michael Brade <brade@informatik.uni-muenchen.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.6.39, 3.0.0-rc7+: complete system freeze with rsync on big directory
Date: Thu, 21 Jul 2011 11:28:04 +0200 [thread overview]
Message-ID: <20110721112804.7aa0043d.taeuber@bbaw.de> (raw)
In-Reply-To: <201107211119.15496.brade@informatik.uni-muenchen.de>
Hi Michael,
I'm just curious, because I have troubles with storage IO too.
Am Thu, 21 Jul 2011 11:19:15 +0200
Michael Brade <brade@informatik.uni-muenchen.de> schrieb:
> Hi,
>
> this is perfectly reproducible: with vanilla 2.6.39.x and 3.0.0 from
> yesterday's git my system completely freezes after a minute or so when I do
>
> rsync -cavSH -n /source/ /dest/
>
> Watching htop, it freezes only after the caches are full but not
> immediately when the caches are full. No Alt-SysRq-magic is working
> anymore, nothing responds at all after the freeze. This is on tty1, no X
> server running.
>
> Note the -n which means dry run. I also mounted both directories read-only,
> so it's not the write commands. I am using XFS on both directories, one is
> mounted with iscsi, the other is local and encrypted with loop-aes. The
> directory size is >20 GB, 4000-6000 files. I first noticed it when a
> cp -a /source /dest froze the system.
>
> When I go back to 2.6.37.6 it works fine. I didn't try 2.6.38 yet.
>
> I am running this on a Dell Vostro, amd64, 6 GB RAM, 8x Intel Core i7 CPU Q
> 740 @ 1.73GHz.
>
> Any ideas how to debug this despite the freeze? Do you need my kernel
> config? Do you need any other info? Please CC me.
Could you try to capture the log via serial console?
(linux/Documentation/serial-console.txt)
What kind of disks/controller/driver do you use?
Lars
next prev parent reply other threads:[~2011-07-21 9:28 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-21 9:19 Michael Brade
2011-07-21 9:28 ` Lars Täuber [this message]
2011-07-21 18:13 ` Michael Brade
2011-08-13 22:17 ` [SOLVED: r8169 is the culprit] " Michael Brade
2011-08-13 22:49 ` David Miller
2011-07-21 19:40 ` Michael Brade
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=20110721112804.7aa0043d.taeuber@bbaw.de \
--to=taeuber@bbaw.de \
--cc=brade@informatik.uni-muenchen.de \
--cc=linux-kernel@vger.kernel.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
all inboxes | Powered by JetHome®