Peter Radig wrote:
Just to make sure I'm seeing the same situation on my box (or I'm too
confused to get your point):
/home and /vol/raid1 are two completely seperate filesystems that only
share their mountpoints in the root fs. How would these trigger the
bug -- or does the second mount of /home create the evil situation?
Thx,
Peter
The bug I described in the previous post is indeed _not_ triggered if
dazukofs
is mounted over seperate filesystem locations.
And it also should not have been triggered by mounting /home twice.
But are you sure that /home is absolutely independent from /vol/raid?
Or is /vol/raid a directory that contains some block device files (maybe
the
one where /home resides?)
And are you sure that mounting of these directories is the reason for
the bug?
I tried to reproduced this, but without success.
But the Oops you reported is exactly the one you get by executing the
steps I
described (performing a lookup that includes crossing the boundaries
of two filesystems).
And can you reproduce the bug?
And if so, does it also occur with the patch I applied?
Greetings,
Lino
Geschäftsführender Gesellschafter: Tjark Auerbach
Sitz der Gesellschaft: Tettnang
Handelsregister: Amtsgericht Ulm, HRB 630992
ALLGEMEINE GESCHÄFTSBEDINGUNGEN
Es gelten unsere Allgemeinen Geschäftsbedingungen
(AGB). Sie finden sie in der jeweils gültigen Fassung
im Internet unter http://www.avira.de/agb
***************************************************
_______________________________________________
Dazuko-help mailing list
Dazuko-help@nongnu.org
http://lists.nongnu.org/mailman/listinfo/dazuko-help