- private: Yes --> No
After many hours of high load (dbench 200 + stress.sh -n 100 + infinite compilation of kernel sources with -j 10) umount takes ~40'. During umount IO activity is ~1000 blocks/sec (vmstat, bo). Despite umount is not finished, the Reiser4 partition is not already in the tables of mounted file systems. It is possible to perform fsck.reiser4 on this partition, which is not yet unmounted without force option(!) and of course, fsck will report that partition is not consistent. The dump produced by echo w > /proc/sysrq-trigger attached