after the lucid server upgrade, situation was identical, karmic and lucid 32-bit clients had duplicate exports. lucid 64-bit client worked flawlessly.
took out fsid=0, and everything went back to normal
(rw,sync,crossmnt,no_subtree_check) instead of (rw,fsid=0,sync,crossmnt,no_subtree_check)
fsid=0 has the meaning of identifying the export as root. Multiple exports cannot be made this way. What I suggest is that a warning should be given by exportfs when using multiple fsid=0 export entries.
Technically this does not seem to be a bug, but a nagging annoyance caused by the parser being unprotected against inherited malpractice, so turning into one.
I would like to hear your opinion on this, particularly the developer's opinion.
ok, here goes:
after the lucid server upgrade, situation was identical, karmic and lucid 32-bit clients had duplicate exports. lucid 64-bit client worked flawlessly.
took out fsid=0, and everything went back to normal
(rw,sync, crossmnt, no_subtree_ check) instead of (rw,fsid= 0,sync, crossmnt, no_subtree_ check)
fsid=0 has the meaning of identifying the export as root. Multiple exports cannot be made this way. What I suggest is that a warning should be given by exportfs when using multiple fsid=0 export entries.
Technically this does not seem to be a bug, but a nagging annoyance caused by the parser being unprotected against inherited malpractice, so turning into one.
I would like to hear your opinion on this, particularly the developer's opinion.
All the best
Antonio