[EMAIL PROTECTED] wrote:
> "Jrgen_P._Tjern":
>> I've now stumbled upon more problems. I switched from 2.6.17-10-server 
>> to 2.6.17-11-generic, recompiled aufs-module with no issues, and mounted 
>> /storage. (I guess this problem existed before I switched kernel)
>> I went into /storage/apt-proxy (which resides on /vault/sdd/apt-proxy), 
>> and did du -sh: (It still has the umount bug)
>>
>> [  421.415679] aufs 20070226
>> [  482.034285] ------------[ cut here ]------------
>> [  482.034364] kernel BUG at /root/aufs.wcvs/aufs/fs/aufs/vdir.c:608!
> 
> A few weeks ago another user reported the same thing which is an
> internal checking in vdir.c. His cause seemed his mis-configuration 
> about CONFIG_AUFS_LHASH_PATCH.
> I suggest you to check your configuration.
I thought CONFIG_AUFS_LHASH_PATCH was for using NFS-filesystems as a 
branch of your aufs? I haven't touched AUFS_LHASH_PATCH, I just fetched 
source and did make -f local.mk. :-)

> And please select your kernel and tell me where I can get its source
> code. Currectly I guess something around umount was changed by ubuntu
> people and it caused your umount problem.
> I could not reproduce your problem on plain linux-2.6.17.
Here are the files for the kernel:
http://archive.ubuntu.com/ubuntu/pool/main/l/linux-source-2.6.17/linux-source-2.6.17_2.6.17.1.orig.tar.gz
http://archive.ubuntu.com/ubuntu/pool/main/l/linux-source-2.6.17/linux-source-2.6.17_2.6.17.1-11.35.diff.gz


Kindest regards, Jørgen.

-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV

Reply via email to