All of lore.kernel.org
 help / color / mirror / Atom feed
From: Francesco Biscani <frbiscani@jumpy.it>
To: reiserfs-list@namesys.com
Subject: reiser4 crash
Date: Sat, 24 Jul 2004 18:27:54 +0200	[thread overview]
Message-ID: <200407241827.54674.frbiscani@jumpy.it> (raw)

Hi,

I had reiser4 crash pretty badly. Here's the story.

My distribution is Gentoo. As you probably know it uses as packaging system a 
tool called "emerge" which basically installs applications following 
installation scripts called "ebuilds". Usually packages are compiled from 
sources, but not necessarily, since ebuilds can contain totally arbitrary 
instructions.

I decided to install the pre-compiled binary version of Openoffice 1.1.2, 
which under Gentoo is known as "openoffice-bin". The installation went on 
regularly, but near the end everything seemed to hang in the "Registering 
components" phase. No CPU or HD activity. After a while, suspecting a bug in 
the ebuild, I went over the Gentoo forums and I found these posts:

http://forums.gentoo.org/viewtopic.php?t=201410&highlight=openofficebin
http://forums.gentoo.org/viewtopic.php?t=184798&highlight=openofficebin+reiser4

These people also report problems installing openoffice on reiser4. In the 
meanwhile the installation process of openoffice-bin was still hanging, but 
suddenly the CPU went 100%. It was "system" activity, no "user" activity. Top 
revealed that it was the installation process that was eating all my CPU. The 
system was still working, but "sync" was not working (it hung). Pretty much 
worried, CPU still 100%, I tried to reboot, but the system was not able to do 
that. I tried to kill the offending process, with no luck. I had no choice 
but to push the power button.

fsck 0.5.6 revealed these errors:

FSCK: Directory [ccb2c:6d703300000000:10b195] (dir40), node [790184], item 
[0], unit [55]: entry has wrong offset
[10b195:0(NAME):14d69636861656c:2e4275626ce92e4d:14942a136fe7bf]. Should be
[10b195:0(NAME):14d69636861656c:2e4275626ce92e4d:14942a136f370f].
FSCK: Directory [209045:1536f6e6e792052:2e987a] (dir40), node [3593262], item 
[0], unit [5]: entry has wrong offset
[2e987a:0(NAME):1536f6e6e792052:6f6c6c696e73202d:2bd0cd03e55f727a]. Should be
[2e987a:0(NAME):1536f6e6e792052:6f6c6c696e73202d:2bd0cd03bde670ca].

I had to issue a --build-fs, which lead to:

FSCK: No 'lost+found' entry found. Building a new object with the key 
2a:0:ffff.
FSCK: Failed to recognize the plugin for the directory [2a:0:ffff].
FSCK: Trying to recover the directory [2a:0:ffff] with the default 
plugin--dir40.
FSCK: The file [2a:0:ffff] does not have a StatData item. Creating a new one. 
Plugin dir40.
FSCK: Directory [2a:0:ffff]: The entry "." is not found. Insert a new one. 
Plugin (dir40).
FSCK: Node (460152), item (2), [2a:0:ffff] (stat40): wrong size (0), Fixed to 
(1).
FSCK: Node (460152), item (2), [2a:0:ffff] (stat40): wrong bytes (0), Fixed to 
(50).
FSCK: Directory [ccb2c:6d703300000000:10b195] (dir40), node [790184], item 
[0], unit [55]: entry has wrong offset
[10b195:0(NAME):14d69636861656c:2e4275626ce92e4d:14942a136fe7bf]. Should be
[10b195:0(NAME):14d69636861656c:2e4275626ce92e4d:14942a136f370f]. Removed.
FSCK: Node (2917509), item (11), [ccb2c:6d703300000000:10b195] (stat40): wrong 
size (62), Fixed to (61).
FSCK: Node (2917509), item (11), [ccb2c:6d703300000000:10b195] (stat40): wrong 
bytes (4090), Fixed to (4012).
FSCK: Directory [209045:1536f6e6e792052:2e987a] (dir40), node [3593262], item 
[0], unit [5]: entry has wrong offset
[2e987a:0(NAME):1536f6e6e792052:6f6c6c696e73202d:2bd0cd03e55f727a]. Should be
[2e987a:0(NAME):1536f6e6e792052:6f6c6c696e73202d:2bd0cd03bde670ca]. Removed.
FSCK: Node (3688550), item (22), [209045:1536f6e6e792052:2e987a] (stat40): 
wrong size (13), Fixed to (12).
FSCK: Node (3688550), item (22), [209045:1536f6e6e792052:2e987a] (stat40): 
wrong bytes (1154), Fixed to (1052).

After that fs was consistent. In lost+found I found some files from the 
web-browser's cache and some temporary files from the installation of 
openoffice. So it probably stopped committing changes to the fs when the 
installation hung.

System logs did not record anything. Fortunately it seems like nothing is 
missing from my fs. Should I be worried about something? fsck does not find 
any errors.

Using auto-snapshot from 20 July agains 2.6.7-mm7.

Hope this is useful. I'll be glad to give more details is asked to. 
Regards,

  Francesco

             reply	other threads:[~2004-07-24 16:27 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-07-24 16:27 Francesco Biscani [this message]
2004-07-25  7:41 ` reiser4 crash mjt
2004-07-25 19:37   ` Francesco Biscani
2004-07-26 15:03     ` Francesco Biscani
2004-08-01 11:37 ` reiser4 crash [solved?] Francesco Biscani
2004-08-01 11:38   ` mjt
  -- strict thread matches above, loose matches on Subject: below --
2004-11-19  8:47 reiser4 crash 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-11-25 17:15 Yiannis Mavroukakis
2004-12-04 11:46 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
2007-10-18 10:39 Reiser4 crash Hubert (Chan) Chathi
2007-10-18 13:34 ` Edward Shishkin
2007-11-14 15:38   ` Hubert Chathi
     [not found] <5c7c368b0711141324l168d9b9fq1fb01cbddbc359cb@mail.gmail.com>
2007-11-14 21:28 ` Edward Shishkin
2007-11-14 21:40   ` Hubert Chathi
2008-11-11 20:50 geearf
2008-11-16 23:34 ` Edward Shishkin
2008-11-19  4:11   ` geearf

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=200407241827.54674.frbiscani@jumpy.it \
    --to=frbiscani@jumpy.it \
    --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.