Re: PATCH: Arla 0.90 on Linux 2.6.24 to Linux 2.6.28

Michael Milligan <[email protected]>
Newsgroups gmane.comp.file-systems.arla.general
Message-ID <[email protected]>
Thanks for all your efforts to get this working on recent Linux kernels.

However, I'm still having issues with arlad/nnpfs blowing it's brains
out on 2.6.27 (the Ubuntu version specifically... 2.6.27-9-generic).

Here's what I'm seeing (debug logs... I apologize if wrapped lines are
ugly):

arlad:  (run as "/usr/sbin/arlad -z -n
--debug=kernel,cache-manager,volume-cache,file-cache,errors,warnings")

2008-12-18 19:28:07 UTC: arla: read_data: from 0 to 0x800
2008-12-18 19:28:07 UTC: arla: worker 0: done
2008-12-18 19:28:07 UTC: arla: worker 0 waiting
2008-12-18 19:28:07 UTC: arla: worker 0: processing
2008-12-18 19:28:07 UTC: arla: fcache_get_attr: have attr
2008-12-18 19:28:07 UTC: arla: fcache_get_attr: doing read_attr
2008-12-18 19:28:08 UTC: arla: trying to fetch status: 0
2008-12-18 19:28:08 UTC: arla: read_data: from 0 to 0x6
2008-12-18 19:28:08 UTC: arla: cm_getattr
2008-12-18 19:28:08 UTC: arla: fcache_get_attr: doing read_attr
2008-12-18 19:28:08 UTC: arla: trying to fetch status: 0
2008-12-18 19:28:08 UTC: arla: cm_getattr: done get attr
2008-12-18 19:28:08 UTC: arla: cm_getattr: return: 0
2008-12-18 19:28:08 UTC: arla: worker 0: done
2008-12-18 19:28:08 UTC: arla: worker 0 waiting
2008-12-18 19:28:08 UTC: arla: worker 0: processing
2008-12-18 19:28:08 UTC: arla: fcache_get_attr: have attr
2008-12-18 19:28:08 UTC: arla: fcache_get_attr: doing read_attr
2008-12-18 19:28:08 UTC: arla: trying to fetch status: 0
2008-12-18 19:28:08 UTC: arla: read_data: from 0 to 0x8
2008-12-18 19:28:08 UTC: arla: cm_getattr
2008-12-18 19:28:08 UTC: arla: fcache_get_attr: doing read_attr
2008-12-18 19:28:08 UTC: arla: trying to fetch status: 0
2008-12-18 19:28:08 UTC: arla: cm_getattr: done get attr
2008-12-18 19:28:08 UTC: arla: cm_getattr: return: 0
2008-12-18 19:28:08 UTC: arla: worker 0: done
2008-12-18 19:28:08 UTC: arla: worker 0 waiting
2008-12-18 19:28:08 UTC: arla: worker 0: processing
2008-12-18 19:28:08 UTC: arla: fcache_get_attr: have attr
2008-12-18 19:28:08 UTC: arla: fcache_get_attr: doing read_attr
2008-12-18 19:28:08 UTC: arla: trying to fetch status: 0
2008-12-18 19:28:08 UTC: arla: cm_getattr
2008-12-18 19:28:08 UTC: arla: fcache_get_attr: have attr
2008-12-18 19:28:08 UTC: arla: cm_getattr: done get attr
2008-12-18 19:28:08 UTC: arla: cm_getattr: return: 0
2008-12-18 19:28:08 UTC: arla: worker 0: done
2008-12-18 19:28:08 UTC: arla: worker 0 waiting
2008-12-18 19:28:09 UTC: arla: worker 0: processing
arlad: messages.c:671: nnpfs_message_getnode: Assertion
`(dentry)->flags.kernelp' failed.

nnpfs (kernel):

Dec 18 19:28:08 cheetah kernel: [17462.488859] nnpfs_block_open(00/03@)
walk failed: -2
Dec 18 19:28:08 cheetah kernel: [17462.488874] (1.536871004.1.1), fid
65542, id 3
Dec 18 19:28:08 cheetah kernel: [17462.488879] nnpfs_block_open: n 1,
mask 1, inode e7ad3a7c, aliases:  .acmeps.com(e1c0ac38)
Dec 18 19:28:08 cheetah kernel: [17462.488889] nnpfs_block_open failed: 2

And if I then try to umount /afs, I get:

Dec 18 19:31:30 cheetah kernel: [17664.616797] BUG: Dentry
d9ff6198{i=1f0f28,n=000000000ef1fca7.mpg} still in use (-1) [unmount of
nnpfs nnpfs]
Dec 18 19:31:30 cheetah kernel: [17664.616838] ------------[ cut here
]------------
Dec 18 19:31:30 cheetah kernel: [17664.616841] kernel BUG at
/build/buildd/linux-2.6.27/fs/dcache.c:666!
Dec 18 19:31:30 cheetah kernel: [17664.616844] invalid opcode: 0000 [#2]
SMP

.... [ugly possibly unneeded msgs deleted]

This is just from reading files, not even trying to write.  It's
intermittent.  It works great up until I get either a "walk failed"
message or a message like:

Dec 18 19:21:17 cheetah kernel: [17051.214123] reading block 03/C7/00:
not there

Write seems to generally have the same problem.

Any ideas on how to debug this further?

Regards,
Mike

-- 
Michael Milligan                                   -> [email protected]
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.