From: Oleg Drokin <green@namesys.com>
To: "Sebastian DrЖge" <sebastian.droege@gmx.de>
Cc: reiserfs-list@namesys.com, linux-kernel@vger.kernel.org
Subject: Re: Reiserfs Corruption with 2.5.5-pre1
Date: Mon, 18 Feb 2002 09:03:43 +0300 [thread overview]
Message-ID: <20020218090343.B1186@namesys.com> (raw)
In-Reply-To: <20020214155716.3b810a91.sebastian.droege@gmx.de> <20020214180501.A1755@namesys.com> <20020214162232.5e59193b.sebastian.droege@gmx.de> <20020214172421.5d8ae63c.sebastian.droege@gmx.de> <20020214192633.A2311@namesys.com> <20020215135223.46af1b28.sebastian.droege@gmx.de> <20020215155413.A7974@namesys.com> <20020216162503.270ab9cc.sebastian.droege@gmx.de>
In-Reply-To: <20020216162503.270ab9cc.sebastian.droege@gmx.de>
Hello!
Please show a process list when this happens (ps axlwww)
Bye,
Oleg
On Sat, Feb 16, 2002 at 04:25:03PM +0100, Sebastian DrЖge wrote:
> Hi,
> I've run gnome-terminal with strace and something interesting has happened...
> gnome-terminal hangs with an endless loop doing polls. strace output is attached. Maybe you can find the problem
>
> Back to the files again... in 2.4.17 they aren't created... in 2.5.5-pre1 they are SOMETIMES created.
> In the moment I'm running 2.5.5-pre1 and no strange file is created
> gnome-terminal doesn't run. Every (?) other programm runs
>
> Bye
prev parent reply other threads:[~2002-02-18 6:04 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-14 14:57 Reiserfs Corruption with 2.5.5-pre1 Sebastian Dröge
2002-02-14 15:05 ` Oleg Drokin
2002-02-14 15:22 ` Sebastian Dröge
2002-02-14 16:24 ` Sebastian Dröge
2002-02-14 16:26 ` Oleg Drokin
2002-02-15 12:52 ` Sebastian Dröge
2002-02-15 12:54 ` Oleg Drokin
2002-02-16 15:04 ` Sebastian Dröge
2002-02-16 17:22 ` [reiserfs-list] " system_lists
[not found] ` <20020216162503.270ab9cc.sebastian.droege@gmx.de>
2002-02-18 6:03 ` Oleg Drokin [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=20020218090343.B1186@namesys.com \
--to=green@namesys.com \
--cc=linux-kernel@vger.kernel.org \
--cc=reiserfs-list@namesys.com \
--cc=sebastian.droege@gmx.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 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.