On 11/25/2013 10:56 AM, dimas wrote:
Hello,
Here are the details:
# insmod
Usage: insmod filename [args]
no-no-no, insmod is used to load module. you must give it a module name to load.
also there is lsmod, which shows currently loaded modules. read man insmod, man
lsmod for details.
so, aftre your mount attempt (not before it, because modules usually load only
when requested) check if reiser4 module did loaded:
lsmod | grep "reiser4"
if it occasionaly shows nothing, try loading it manually, using "insmod
reiser4" or better
modprobe -v reiser4
if this will fail too, there should be a problem with the module itself.
i'm using no modules, building only what i need, and building it static (=Y).
static built reiser4 works perfectly wirh 3.11 for me, so i don't know, what's
that. check dmesg after attempt to load, maybe there is something.
# ll /proc/filesystems
-r--r--r-- 1 root root 0 Nov 25 12:18 /proc/filesystems
try "cat /proc/filesystems")) it shows list of fs types, which kernel currently
support
Back to the Question:
What reiser4 kernel build paramerers I need in the kernel build so I can
use this partition ?
I have set:
CONFIG_REISER4_DEBUG=n
CONFIG_REISER4_FS=m
if you are not using cryptocompress plugin (your fsck lock says, you are not).
i believe, this is enough.
Fsck doesn't report if compression has been enabled.
debugfs.reiser4 should be patched to show value of "create" (reg40 or
ccreg40),
"compress" (lzo1, or gzip1), etc.
Edward.
--
To unsubscribe from this list: send the line "unsubscribe reiserfs-devel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
