Hi Brad,
We have committed some unionfs fixes to 8-CURRENT.
Please try it, I guess those latest fixes gives you success.
If you have fails still after that, please send us your
panic report. Thanks :)
Brad Pitney wrote:
once again:
KDB: stack backtrace:
db_trace_self_wrapper(c074b5ee,e70c79ac,
once again:
KDB: stack backtrace:
db_trace_self_wrapper(c074b5ee,e70c79ac,c05b6853,c4b8c420,e70c79ac,...)
at db_trace_self_wrapper+0x26
kdb_backtrace(c4b8c420,e70c79ac,c07025c5,e70c79bc,c4c002b8,...) at
kdb_backtrace+0x29
vfs_badlock(c4a31900,e70c79bc,c07b00a0,c4c002b8,c4b8c420) at vfs_badlock+0x2
On Thu, Mar 20, 2008 at 10:20 AM, Kris Kennaway <[EMAIL PROTECTED]> wrote:
> [..]
> This is likely to be a unionfs bug.
>
unionfs_close: warning: open count is 0
unionfs_close: warning: open count is 0
unionfs_close: warning: open count is 0
unionfs_close: warning: open count is 0
unionfs_close:
On Thu, Mar 20, 2008 at 10:20 AM, Kris Kennaway <[EMAIL PROTECTED]> wrote:
>
> Brad Pitney wrote:
> > Not sure why it keeps wedging, at first I thought it was something to
> > do with the LORs, now after adding some more debugging options I
> > think I might have found the answer!
> >
> > KDB
Brad Pitney wrote:
Not sure why it keeps wedging, at first I thought it was something to
do with the LORs, now after adding some more debugging options I
think I might have found the answer!
KDB: stack backtrace:
db_trace_self_wrapper(c074b5ee,e70599ac,c05b6853,c4a9e000,e70599ac,...)
at db_trac
Not sure why it keeps wedging, at first I thought it was something to
do with the LORs, now after adding some more debugging options I
think I might have found the answer!
KDB: stack backtrace:
db_trace_self_wrapper(c074b5ee,e70599ac,c05b6853,c4a9e000,e70599ac,...)
at db_trace_self_wrapper+0x26
k
