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: Thu, 30 Jan 2003 14:32:18 +0300 [thread overview]
Message-ID: <20030130143218.A1057@namesys.com> (raw)
In-Reply-To: <5.2.0.9.2.20030129233147.02056cf8@pop.tvnet.hu>
Hello!
On Wed, Jan 29, 2003 at 11:34:10PM +0100, Newsmail wrote:
> Where does process hang this time? (press SysRQ-T, decode the output and
> send it to me) ---->
> could you please tell me what is SysRQ-T? btw its a remote machine...
sysrq-T is combinatin of keys "Alt+PrtSc/SysRq+t" (three keys totally)
that should be pressed simultaneusly (in this order.).
You need to have sysrq enabled both in your kernel config and in
sysctl (modern discros tend to disable it for some reason).
Well, if the box is remote, then may be you have serial console?
You need to send <Break> followed by T, then (over your serial line).
That will output list of currently running tasks and their stacks.
> ps: well you say that its maybe a crypto-loop side problem, what I dont
> understand why it only came after 2.4.20-preX introduced, and it works
> absolutly without any problem on 2.4.19.
Well, there were not only reiserfs changes in 2.4.20-pre series, you know.
You can even take content of fs/reiserfs/{*.c,Makefile} and
include/linux/reiserfs*.h from 2.4.19, put these into 2.4.20 kernel
sources at appropriate places, recompile the kernel and see what will happen.
I tried to write with reiserfs onto crypto-aes enabled loop device and
wrote 20G of data (with scp) without any problems. So it seems I cannot
reproduce that problem locally and I really need your help in debugging it.
Bye,
Oleg
next prev parent reply other threads:[~2003-01-30 11:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-29 22:34 lvm+loop-aes+reiserfs / iput deadlock fix Newsmail
2003-01-30 11:32 ` Oleg Drokin [this message]
2003-01-30 12:43 ` Newsmail
-- strict thread matches above, loose matches on Subject: below --
2003-01-26 23:11 Newsmail
2003-01-28 6:40 ` Oleg Drokin
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=20030130143218.A1057@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.