I now disabled pre-empt, and basically the only kernel patch
I added was supermount+ O(1) batch scheduler and -aa vm patch. Now the problem
seems to be different. If a process writes large files (about 1 or 2 gigs)
it will often hangs right when it reach the end of the file and it was
about to update the directory entry, it just hangs there. Top shows 100%
system usage (0% user) and I can't kill the process until it unhangs itself
which takes about 2-3 minutes. I'm using the 2.4.19 snapshot, but I just
saw that you have a 1.2 pre-release for 2.4.19, so I'm going to recompile
my kernel with that and just supermount. I'm also using vmware (which has
kernel modules) so i'm not sure if that has an impact or not, but I thought I'd
mention it. I could reproduce it often but just doing a "cp -a dir1 dir2"
with a couple of 1 gig files in it.
-Christian
On 14 Oct 2002, Eric Sandeen wrote:
| Hi Christian -
|
| I don't have a lot of experience with pre-empt, but the best thing to do
| would be to break into KDB and see which process is hung, and what it's
| hung on... if you have kdb....
|
| -Eric
|
| On Mon, 2002-10-14 at 12:00, Christian Lambert wrote:
| >
| > I've been running a stock debian 2.4.19 + xfs2.4.19 snapshot patch + preempt
| > and this worked fine for like 3-4 days now. But this morning I came up
| > and my system hung up when I did "ls" in the console. Then everything
| > hung up from there and lead eventually to X hanging as well, the hard drive
| > light was solid "on". I have a mix of reiserfs and xfs filesystems so I'm
| > not sure what caused it, but I wanted to know if this is known to cause
| > problems or it's supposed to work? I'm not using lock-break, just preempt.
| > I think what might have trigged this hang is the updatedb (for locate) that
| > ran during the night and maybe have hosed things up scanning thru the
| > filesystems.
| >
| > -Christian
| >
| >
| --
| Eric Sandeen XFS for Linux http://oss.sgi.com/projects/xfs
| sandeen@xxxxxxx SGI, Inc. 651-683-3102
|
|