baselayout-2.0.0_alpha4 & _alpha3 confuse reiser4 partitions on a reiser4-enabled kernel with reiserfs partitions one speciality, though: the reiser4 partition uses cryptcompress plugin with lzo1 Reproducible: Always Steps to Reproduce: 1.create reiser4 partition with mkfs.reiser4 -o create=ccreg40,compress=lzo1 /dev/foo 2. extract portage tarball on it 3. set fstab up 4. reboot system (you need a system with at least 1 more reiserfs partition, at best /boot with reiserfs & / with reiserfs 5. see strange output of fsck.reiser4 or fsck.reiserfs with list of reiserfs plugins; usually boot-produce halts & asks for root password to correct errors Expected Results: it should have mounted the reiser4 partitions without problems (it did this with baselayout-1) /etc/fstab: # <file system> <mount point> <type> <options> <dump> <pass> /dev/sda1 /boot reiserfs noatime,nodiratime 1 2 /dev/sda7 / reiserfs noatime,nodiratime 0 1 /dev/sda8 none swap sw 0 0 /dev/cdroms/cdrom0 /mnt/cdrom iso9660 noauto,ro 0 0 proc /proc proc defaults 0 0 none /dev/shm tmpfs nodev,nosuid,noexec 0 0 /dev/sda9 /usr/portage reiser4 noauto,noatime,nodiratime 0 2 /dev/mapper/home /home reiserfs noatime,nodiratime 0 2 ## /dev/sda1 /usb/usbstick_or_hdd auto noauto,user 0 1 #tmpfs /tmp tmpfs size=100m,mode=177 0 0
/dev/sda9 /usr/portage reiser4 noauto,noatime,nodiratime Yup, the noauto option means just that - no automatic mounting. For the fsck errors, see bug #116016 for a patch to reiserfsprogs and give feedback on it.
what still wonders me is that strange output which those reiser4- or reiserfsprogs give, I'll give your patch a try - thanks :)
