null_lookup() vnode locking wierdness
Alexander Leidinger
Alexander at Leidinger.net
Mon Nov 24 03:00:10 PST 2003
On Mon, 24 Nov 2003 12:53:53 +0600
Boris Popov <bp at freebsd.org> wrote:
> Yes, this seems to be correct and necessary addition. At first sight,
> the later code shouldn't blow because of that. BTW, buildworld -jN on top of
> the null mount together with another buildword -jN on the underlying file
> system helps a lot to discover vnode locking problems.
While you're looking at nullfs... I get a ENAMETOOLONG while trying to
mount a FS with nullfs or unionfs. The funny thing: realpath reports a
max of 79 characters for both pathnames.
---snip---
{71} <FreeBSD 5.1-CURRENT> [M87:~netchild/FreeBSD/SystemOnCD]
(62) root at ttyp0 # realpath work/SystemOnCD-1/usr/ports/distfiles |wc -c
79
{0} <FreeBSD 5.1-CURRENT> [M87:~netchild/FreeBSD/SystemOnCD]
(63) root at ttyp0 # realpath /space/distfiles |wc -c
17
{0} <FreeBSD 5.1-CURRENT> [M87:~netchild/FreeBSD/SystemOnCD]
(64) root at ttyp0 # mount -t unionfs -o -b /space/distfiles work/SystemOnCD-1/usr/ports/distfiles
unionfs: /space/distfiles: File name too long
{71} <FreeBSD 5.1-CURRENT> [M87:~netchild/FreeBSD/SystemOnCD]
(65) root at ttyp0 # mount -t unionfs -o -b /space/distfiles /mnt
---snip---
Any ideas what's wrong or where I need to look for a bug?
Bye,
Alexander.
--
If Bill Gates had a dime for every time a Windows box crashed...
...Oh, wait a minute, he already does.
http://www.Leidinger.net Alexander @ Leidinger.net
GPG fingerprint = C518 BC70 E67F 143F BE91 3365 79E2 9C60 B006 3FE7
More information about the freebsd-current
mailing list