While booting i get these messages: *Remounting root filesystem read-only (if necessary) ... *Checking root filesystem ... Filesystem is clean Filesystem seems mounted read-only. Skipping journal replay. Checking internal tree..finished. *Remounting root filesystem read/write... Reproducible: Always Steps to Reproduce: 1. booting gentoo linux with default init scripts and reiserfs bootpartition Actual Results: i get the above messages Expected Results: i expect, that the filesystem check is performed AFTER remounting it r/w. Otherwise, i don't need a filesystem check... :)
you neglected to provide `emerge info` like the bug report page told you to also post your /etc/fstab as an attachment
Created attachment 55507 [details] Filestytem Table
i didn't think "emerge info" is relevant for this problem... but here it is: Portage 2.0.51.19 (default-linux/x86/2004.3, gcc-3.3.5, glibc-2.3.4.20041102-r1, 2.6.11.5apr3 i686) ================================================================= System uname: 2.6.11.5apr3 i686 AMD Athlon(TM) XP 1600+ Gentoo Base System version 1.4.16 Python: dev-lang/python-2.3.4-r1 [2.3.4 (#1, Mar 28 2005, 19:16:38)] dev-lang/python: 2.3.4-r1 sys-devel/autoconf: 2.59-r6, 2.13 sys-devel/automake: 1.7.9-r1, 1.8.5-r3, 1.5, 1.4_p6, 1.6.3, 1.9.4 sys-devel/binutils: 2.15.92.0.2-r1 sys-devel/libtool: 1.5.10-r4 virtual/os-headers: 2.6.8.1-r2 ACCEPT_KEYWORDS="x86" AUTOCLEAN="yes" CFLAGS="-O2 -march=athlon-xp -pipe -fomit-frame-pointer" CHOST="i686-pc-linux-gnu" CONFIG_PROTECT="/etc /usr/kde/2/share/config /usr/kde/3.4/env /usr/kde/3.4/share/config /usr/kde/3.4/shutdown /usr/kde/3/share/config /usr/lib/X11/xkb /usr/share/config /var/qmail/control" CONFIG_PROTECT_MASK="/etc/gconf /etc/terminfo /etc/texmf/web2c /etc/env.d" CXXFLAGS="-O2 -march=athlon-xp -pipe -fomit-frame-pointer" DISTDIR="/usr/portage/distfiles" FEATURES="autoaddcvs autoconfig ccache distlocks sandbox sfperms" GENTOO_MIRRORS="http://ftp-stud.fht-esslingen.de/pub/Mirrors/gentoo/ http://linux.rz.ruhr-uni-bochum.de/download/gentoo-mirror/ ftp://ftp.tu-clausthal.de/pub/linux/gentoo/" MAKEOPTS="-j2" PKGDIR="/usr/portage/packages" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/usr/portage" SYNC="rsync://rsync.gentoo.org/gentoo-portage" USE="x86 3dnow X aac aalib alsa apm arts avi berkdb bitmap-fonts crypt cups curl directfb dts dvd dvdread emboss encode esd fam flac font-server foomaticdb fortran gdbm gif gimpprint gphoto2 gpm imagemagick imlib java jpeg jpeg2k kde libg++ libwww mad mikmod mmx mng motif mp3 mpeg mysql ncurses nls nvidia oggvorbis opengl pam pdflib perl png povray python qt quicktime readline samba sdl spell sse ssl svg svga tcpd tetex tiff truetype truetype-fonts type1-fonts userlocales wmf xine xml xml2 xmms xscreensaver xv xvid zlib video_cards_nvidia linguas_de linguas_en" Unset: ASFLAGS, CBUILD, CTARGET, LANG, LC_ALL, LDFLAGS, PORTDIR_OVERLAY
This bug is invalid. Of course the filesystem has to be mounted read-only when reiserfsck it poking it or things would definitely blow up (well, reiserfsck would refuse to run anyway). Remember: Writing to the filesystem and writing to the block device directly is not the same. You really need to have exclusive write access. The best would be to not have a filesystem mounted on the block device at all when performing checks, but for the root filesystem read-only is the best you can do at that point.
The journal isn't played back because the filesystem is opened and might alter important on-disk structures which in turn might crash the opened filesystem. The journal is taken into consideration though. That's normal behavior.
i am a bit confused if the fs has to be "mounted r/w" or "not at all" to replay a journal, but nevertheless i can't believe that it is normal behaviour to SKIP that action that wants to return my fs into a valid state after a crash/power-loss or something. i mean, what do i have a journal for when it is NEVER used? "The journal isn't played back because the filesystem is opened and might alter important on-disk structures which in turn might crash the opened filesystem." who alters what? the journal the filesystem? that is what it is made for, isn't it?
what does `dmesg` report for mounting of / filesystem before init has started ? ext3 does recovery at that point
Created attachment 56176 [details] Complete output of dmesg dmesg lines referring reiserfs: ReiserFS: hda9: found reiserfs format "3.6" with standard journal ReiserFS: hda9: using ordered data mode ReiserFS: hda9: journal params: device hda9, size 8192, journal first block 18, max trans len 1024, max batch 900, max commit age 30, max trans age 30 ReiserFS: hda9: checking transaction log (hda9) ReiserFS: hda9: Using r5 hash to sort names VFS: Mounted root (reiserfs filesystem) readonly. Freeing unused kernel memory: 184k freed ReiserFS: hda9: Removing [860368 962700 0x0 SD]..done
looks to me like everything is acting as it should the journal was used before init was run, see these lines in your dmesg: ReiserFS: hda9: Removing [860368 962700 0x0 SD]..done ReiserFS: hda9: There were 1 uncompleted unlinks/truncates. Completed
