reiserfs umount error

[Headmaster]

I'm new to Linux, and just compiled my first kernel. Everything worked pretty well except the following:

when I try to halt the server, I get see the following error:

/dev/hda3 umounted                   failed
Oops: Umount failed :-( -- trying to remount readonly...
/dev/hda3 on / type reiserfs (ro, dontpanic)
/dev/hda3 on / type reiserfs (ro, dontpanic)
extra sync...
... hope now it's ok to reboot.

When I boot back to the old kernel, I notice that the reiserfs is loaded as a module. When I built the new kernel, I loaded reiserfs into the kernel. Is this part of my problem? I didn't see any errors when halting the server with my old kernel. I also don't see any errors when the server boots. Any ideas what I did wrong here?

Thanks,
Scott

 

[clonny2]

First, make sure that reiserfs is truely running in the kernel.

Once you boot type this:

1: Create a temp dir called foo.
mkdir foo
cd foo

2: Create a temp file that will be a filesystem.
dd if=/dev/zero of=file bs=8192 count=100

This will make a small file called file.

3: Format the file.
mkfs.reiserfs file

4: Create a mount point
mkdir mnt

5: Mount the newly formated fs.
mount file mnt

If it mounts Ok, then you should be good.

6: Try to unmount the fs.
umount mnt

7: Make sure it can unmount the fs.

This is a quick way to test to make sure everything is ok. BTW, you can do this to test any type of filesystem. So you can add experimental filesystems or test filesystems like xfs, jfs, etc...

 

[Headmaster]

clonny2:

I tried your suggestion.

On step 2, I got
100+0 records in
100+0 records out

On step 3, I got
mkfs.reiserfs 3.6.2(2002)
file is not a block special device Continue(y/n)y
mkfs.reiserfs: Guessing about desired format
mkfs.reiserfs: Kernel 2.4.19-4GB-SMP is running
reiserfs_create_journal: can not create filesystem on 200 blocks

Before trying this, I recompiled the kernel again, this time loading reiserfs as a module. I did the mk_initrd, and that looked successful. In the dmesg output, it looks to me like it's mounting the filesystem. I'm confused now!

Any other suggestions? what's interesting, is that I can create, delete, copy etc like their is nothing wrong...

thanks for your help!
Scott

 

[Headmaster]

Doing a little more digging, and now I notice that the root partition is getting mounted as read-only. I have another partition on another drive called /bak, and it's getting mounted as read-write. Their must be a parameter in some file somewhere that is causing this? But where, and why would the 'old' kernel mount / just fine?

Thanks for the help!
Scott