When installing base system with Reiser and the ReiserFS tools, boot init calls fsck.ReiserFS from /sbin. What actually exists in /sbin for Reiser to check the filesystem before mounting RW is reiserfsck, with soft links to fsck.reiserfs. However, what's called is fsck.ReiserFS, which of course isn't the same. Reproducible: Always Steps to Reproduce: 1.Installation with default Reiserfs 2. 3. Actual Results: System reports unable to call "fsck.ReiserFS" during boot, skips Reiser journal replays. Expected Results: Should have run a journal check on an unmounted file system before continuing into init level 3. Solution is to create softlink fsck.ReiserFS or change that in the boot scripts.
could you emerge the reiserfs tools and provide the CONTENTS file so we can see where it installed files to ?
Created attachment 23568 [details] As requested, CONTENTS file from emerge of reiserfs programs Attached is requested information from vapier concerning emerge of reiserfsprogs. This emerge was initiated and successful on Jan 3, bug wasn't noticed until yesterday.
/sbin/fsck.reiserfs from reiserfsprogs /usr/sbin/fsck.reiserfs from progsreiserfs -> Bug 33012 maybe?
Bug was local as a result of bad entries in fstab, not inherrent in gentoo installation. User had followed examples where reiserfs was "ReiserFS" for fstab entries. After searching this evening I discovered this, was able to replicate the bug locally and issue a fix. Problem may be considered a minor documentation issue, but not likely.
i looked through the x86 install doc and all references to reiserfs are correct ... that is, when used in normal paragraphs, it is 'ReiserFS', and when used in code examples, it is 'reiserfs' ...