From: Theodore Tso <tytso@mit.edu>
To: Jens Kubieziel <maillist@kubieziel.de>
Cc: linux-ext4@vger.kernel.org
Subject: Re: git svn clone freezes the pc on ext4
Date: Fri, 18 Sep 2009 15:38:11 -0400 [thread overview]
Message-ID: <20090918193811.GB27303@mit.edu> (raw)
In-Reply-To: <20090917131356.GG9393@kubieziel.de>
On Thu, Sep 17, 2009 at 03:13:56PM +0200, Jens Kubieziel wrote:
>
> I recently changed my /home-partition to ext4 and wanted to clone a SVN
> repository. After calling "git svn clone https://...", git began
> fetching old revisions and at every try the complete pc freezes. It
> doesn't respond to any keyboard presses nor to SysRq. I tried the same
> command on different filesystems (ext3, reiser) and with different git
> versions. Only git on ext4 causes this freeze.
>
> The system logs have no uncommon messages. I found only:
> EXT4 FS on sda3, internal journal on sda3:8
> EXT4-fs: deleayed allocation enabled
> EXT4-fs: file extents enabled
> EXT4-fs: mballoc enabled
> EXT4-fs: mounted filesystem with ordered data mode
> Linux version is 2.6.28-15 (default installation from Ubuntu jaunty).
This sounds like the classic Ubuntu Jaunty's default kernel freezes
when deleting large numbers of files. It didn't occur with stock
mainline 2.6.28, nor with stock mainline 2.6.29, and it bisected to
one of Ubuntu's ext4 patch backports. No one was able to debug it
further, and I was never able to replicate it on my test systems, so
we ultimately just told people to use a mainstream kernel or a Karmic
beta kernel for people who wanted to use ext4 with Ubuntu Jaunty.
- Ted
prev parent reply other threads:[~2009-09-18 19:38 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-17 13:13 git svn clone freezes the pc on ext4 Jens Kubieziel
2009-09-17 14:27 ` Eric Sandeen
2009-09-18 18:37 ` Jens Kubieziel
2009-09-18 19:38 ` Theodore Tso [this message]
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=20090918193811.GB27303@mit.edu \
--to=tytso@mit.edu \
--cc=linux-ext4@vger.kernel.org \
--cc=maillist@kubieziel.de \
/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).