----- Mail Original ----- De: "Edward Shishkin" <edward.shishkin@xxxxxxxxx> À: geearf@xxxxxxx Cc: reiserfs-devel@xxxxxxxxxxxxxxx Envoyé: Dimanche 16 Novembre 2008 15:34:53 GMT -08:00 USA/Canada - États du Pacifique Objet: Re: Reiser4 crash geearf@xxxxxxx 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@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
