On Thu, 2003-01-30 at 19:51, Philip Rowlands wrote: > On Thu, 30 Jan 2003, Taylor, ForrestX wrote: > >> I think I'm probabbly missing something dumb but I can't for the life of > >> me figure out what it is. > > > >It is trying to get a lock. Try mount -o nolock,wsize=8192,rsize=8192 > >server:/dir > > > >The -o nolock option should keep it from trying to lock it, causing a > >10-20 minute timeout. > > I'm sure this works, because people keep suggesting it, but I'm not sure > it's an accurate diagnosis. > > I worked around this problem by doing the mount in a separate %pre > section, with --nochroot. It's accurate. The mount in the installer environment is a hacked mount which does the equivalent of -o nolock by default. Cheers, Jeremy
