On Tue, 05 Feb 2008 18:28:29 +0900 (JST)
Ryusuke Konishi <[EMAIL PROTECTED]> wrote:

> Hi Gábor,
> 
> From: Ryusuke Konishi <[EMAIL PROTECTED]>
> Subject: Re: [NILFS users] Deadlocks! help, please!
> Date: Tue, 22 Jan 2008 12:02:00 +0900
> > On Tue, 2008-01-22 at 00:00 +0100, Gergely Gábor wrote:
> > > > Here I attach a test patch to fix the problem.
> > > > Could you try the patch ?
> > > > 
> > > > So, if rtorrent (or something else) hang again, then
> > > > send me a copy of /proc/slabinfo, please.
> > > It hang again,
> > 
> > Ugh! OK, I'll continue to work on it.
> 
> Today I could reproduce the hang problem, and succeeded in capturing
> a stack trace of the suspended cleaner process.
> 
> After short analysis, a suspicious bug was found in a write routine
> of NILFS.  It seems to be the root cause of this problem.
> 
> I will attach a revised patch below.
> Could you try the patch?
> 
> It is applicable to nilfs-2.0.0-testing-8 as usual,
> (Ignore hunks, they are harmless)
> 
I have installed it (with some other patches: the one for the mount option bug, 
and other for udivdi (that is needed to link the module properly at me) and 
started a download in rtorrent for the night. It has not ferrzed, but i have 
experianced massive memory leaks, either on the cleaner, or int he module. now 
i'm trying to reproduce the bug with fs running without cleaner. if it will not 
arise in a day, i'll try the cleaner as well. I have a question about the 
cleaner, that might help my find the bug: can I send a signal to the cleaner to 
finish and commit unfinished changes and exit after that? and can I manually 
start a cleaner (possibly with valgrind)? Can I send signals to pause cleaning 
(for example I go on battery), and to resume?
This leak error ate up all my memory, and forced all apps to swap, slowing the 
system down so much, that it took almost an hour to exit rtorrent... 
unfortunalety i forgot to vmstat after the kill of the cleaner, before 
umounting the fs. If I kill the fs will it not leave garbage (i mean badly 
formed entries in the log) after itself if it will, will those entries be 
cleaned up? after i umounted the partition, i had my ram back cleanly (i'd say 
that this was possibly the cleaner, as the module was left in memory even after 
the umount, still the ram wasn't wasted...) Is that possible, that the ram was 
not wasted, but the cleaner/fs is bit inefficient, or can't be made simpler, 
and I should buy more ram? it ate ~440Mb of memory. (i have 512Mb)

Otherwise the patch seems to work cleanly I haven't applied the previous patch 
you proposed, should I have tried? (it gave errors) Possibly if you set up a 
git/hg/other repo, life'd be more convinient. they made my life simpler even in 
my small school projects.

Sorry for the letter being a bit unstructured, many questions arise in me, may 
as writing the letter and actually asking is simpler than checking out myself. 
(well, i might check out, but why not try asking?)

Best regards:
-- 
Gergely Gábor <[EMAIL PROTECTED]>

* random fortune:
Before borrowing money from a friend, decide which you need more.
                -- Addison H. Hallock

Attachment: signature.asc
Description: PGP signature

_______________________________________________
users mailing list
[email protected]
https://www.nilfs.org/mailman/listinfo/users

Reply via email to