From: geearf@free.fr
To: Edward Shishkin <edward.shishkin@gmail.com>
Cc: reiserfs-devel@vger.kernel.org
Subject: Re: Reiser4 crash
Date: Wed, 19 Nov 2008 05:11:29 +0100 (CET) [thread overview]
Message-ID: <1507673316.377921227067889231.JavaMail.root@zimbra4-e1.priv.proxad.net> (raw)
In-Reply-To: <4920AE1D.8070808@gmail.com>
----- Mail Original -----
De: "Edward Shishkin" <edward.shishkin@gmail.com>
À: geearf@free.fr
Cc: reiserfs-devel@vger.kernel.org
Envoyé: Dimanche 16 Novembre 2008 15:34:53 GMT -08:00 USA/Canada - États du Pacifique
Objet: Re: Reiser4 crash
geearf@free.fr wrote:
>> Hello ML,
>>
>> just to report one issue that I had yesterday with r4:
>>
>> I restarted Xorg the hard way (ctrl alt backspace) without any real reason for that, just to try some different xorg.conf and >>then I could not log in KDE anymore (I had a bad crash the previous day so it could have been related).
>> Result was that certain files were corrupted and fsck.reiser4 did not fully help. To fix my issues I had to fsck the partition >>and manually remove anything in /tmp and /var/tmp from another OS. Removing anything in /var/tmp while using that partition as >>the OS would result in a crash even after fsck said everything was fixed...
>>
>It is reproducible?
I have no idea how, and I do not have much time to corrupt my system this week.
>Compression is disabled?
It was enabled
>if both is "yes", then, please, pack the metadata by
>debugfs.reiser4 -P /dev/xxx | gzip > meta.gz
>and let me download the file meta.gz
>> What I saw in dmsg was pretty much the same we had a year ago when KDE4 was out, with the "out of memory?" warning and stuff till Edward fixed R4.
>
>
>Yes, it looks like a bug in handling some special
>case of incomplete conversion. Anyway, detailed
>kernel complaints are highly desirable..
>Thanks,
>Edward.
Sorry I did not keep any data after fixing the fs...
John
--
To unsubscribe from this list: send the line "unsubscribe reiserfs-devel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2008-11-19 4:11 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-11 20:50 Reiser4 crash geearf
2008-11-16 23:34 ` Edward Shishkin
2008-11-19 4:11 ` geearf [this message]
[not found] <5c7c368b0711141324l168d9b9fq1fb01cbddbc359cb@mail.gmail.com>
2007-11-14 21:28 ` Edward Shishkin
2007-11-14 21:40 ` Hubert Chathi
-- strict thread matches above, loose matches on Subject: below --
2007-10-18 10:39 Hubert (Chan) Chathi
2007-10-18 13:34 ` Edward Shishkin
2007-11-14 15:38 ` Hubert Chathi
2004-12-04 11:46 reiser4 crash Andrew Benton
2004-12-04 12:18 ` Frank Denis (Jedi/Sector One)
2004-12-04 12:20 ` Frank Denis (Jedi/Sector One)
2004-12-04 12:52 ` Mark Nipper
2004-12-04 13:52 ` Andrew Benton
2004-11-25 17:15 Yiannis Mavroukakis
2004-11-19 8:47 Sami Liedes
2004-11-25 7:54 ` Vladimir Saveliev
2004-11-25 9:36 ` Sami Liedes
2004-11-25 11:19 ` Cal
2004-11-25 11:23 ` mjt
2004-11-25 11:42 ` Cal
2004-11-25 12:05 ` mjt
2004-11-25 12:35 ` Cal
2004-11-25 16:55 ` Vladimir Saveliev
2004-11-25 18:21 ` Cal
2004-11-25 18:48 ` mjt
2004-11-25 20:00 ` Cal
2004-11-25 20:21 ` mjt
2004-11-25 21:14 ` Cal
2004-11-25 21:28 ` mjt
2004-11-25 21:42 ` Cal
2004-11-25 21:47 ` mjt
2004-11-25 22:14 ` Cal
2004-07-24 16:27 Francesco Biscani
2004-07-25 7:41 ` mjt
2004-07-25 19:37 ` Francesco Biscani
2004-07-26 15:03 ` Francesco Biscani
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=1507673316.377921227067889231.JavaMail.root@zimbra4-e1.priv.proxad.net \
--to=geearf@free.fr \
--cc=edward.shishkin@gmail.com \
--cc=reiserfs-devel@vger.kernel.org \
/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.