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: Fri, 15 Feb 2002 15:54:13 +0300 [thread overview]
Message-ID: <20020215155413.A7974@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>
In-Reply-To: <20020215135223.46af1b28.sebastian.droege@gmx.de>
Hello!
On Fri, Feb 15, 2002 at 01:52:23PM +0100, Sebastian DrЖge wrote:
> > Do these files disa[[ear after you quit GNOME?
> They don't disappear but I can't reproduce the behaviour anymore...
> I've run reiserfsck --fix-fixable, it detects one error, fixes that and after reboot the files were gone in 2.4.17 AND 2.5.5-pre1
What was the error?
> I had this behaviour before the reiserfscks but I thought it has something to do with the files
> 2.4.17, again, runs without any problems
> Maybe somebody can test if he can start gnome-terminal with 2.5.5-pre1
Where do these gnome-terminal hangs? (check ps axl output,
also sysrq-t may be of some help)
Bye,
Oleg
next prev parent reply other threads:[~2002-02-15 12:54 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 [this message]
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
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=20020215155413.A7974@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.