Hello everybody.

Due to a mistake of mine, i've reinstalled all my system last night, and upgraded to unstable with the last kernel for my architecture downloaded with apt (package linux-image-2.6.15-1-k7).

But I've got a....strange problem. I've put /var on a separate partition (my /etc/fstab is coming) on /dev/hdb3, but, this /var is a little strange.

While booting with the installation kernel (2.4.18, no initrd), it correctly mounts under /var, and it's populate with the lib/, log/, data/, of a normal system (and i'm posting with this kernel).

But when i'm trying the 2.6.15 kernel, the /var partition mounts correctly, but it's empty. The partition is mounted (and I manually mount/umount it, to be sure), but whatever i can do on it, when i'm go back to 2.4.18, the /var partition is in the same state than the last boot under 2.4.18.

Here's my /etc/fstab entry for this partition:
/dev/hdb3 /var reiserfs defaults 0 2

Thanks for your help, I'm getting crazy

is the size of the file system the same on both kernels?

what did you include in your initrc?

So... I'm trying to have it working, on another way et i displace my /var on the root partition.

But, the problem is the same. But, not only located in /var. /etc/mtab can't be write, a lot of file can't be open... but they are all owned by root, I give them world access, but the problem is the same...

The "funniest" thing, is that, as root, I can't remove some files, not opened by a proc (lsof is my friend).

The initrd is the one provided with the debian image binary. I'm currently comiling a new kernel, with the same config, just to see if it's could come from here....