From: Oleg Drokin <green@namesys.com>
To: Newsmail <newsmail@satimex.tvnet.hu>
Cc: reiserfs-list@namesys.com
Subject: Re: lvm+loop-aes+reiserfs / iput deadlock fix
Date: Tue, 28 Jan 2003 09:40:39 +0300 [thread overview]
Message-ID: <20030128094039.B32093@namesys.com> (raw)
In-Reply-To: <5.2.0.9.2.20030127000631.01d7a068@pop.tvnet.hu>
Hello!
On Mon, Jan 27, 2003 at 12:11:37AM +0100, Newsmail wrote:
> ftp://ftp.namesys.com/pub/reiserfs-for-2.4/2.4.20-pending/01-iput-deadlock-fix.diff
> patch on 2.4.20aa1 and this patch DOES improve the situation.
That's good... and bad.
> Before I used the patch when I made heavy copying of 10-50 meg files, after
> some time the copying process hung, and WASN'T killable. And also it left
> files that werent deletable, and also left the deleting process hung. and
> many times I wasnt even able to acces the folder where the strange file was
> located.
> Now with the iput deadlock fix, the copying process does hang as well, BUT
> it is killable after, and the 'fucked up' file is deletable also.
That is clear sign of problems at new_inode() stage (something propagated from block level, I think).
And given that you do not have space shortage and any unusual kernel messages...
This is very strange.
Where does process hang this time? (press SysRQ-T, decode the output and send it to me)
Bye,
Oleg
next prev parent reply other threads:[~2003-01-28 6:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-26 23:11 lvm+loop-aes+reiserfs / iput deadlock fix Newsmail
2003-01-28 6:40 ` Oleg Drokin [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-01-29 22:34 Newsmail
2003-01-30 11:32 ` Oleg Drokin
2003-01-30 12:43 ` Newsmail
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=20030128094039.B32093@namesys.com \
--to=green@namesys.com \
--cc=newsmail@satimex.tvnet.hu \
--cc=reiserfs-list@namesys.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.