Date: Thu, 24 Nov 2005 08:09:49 -0500 From: "Frank Reid" <fcreid@ourcorner.org> To: "'Boris Popov'" <bp@freebsd.org> Cc: 'Craig Rodrigues' <rodrigc@crodrigues.org>, freebsd-bugs@freebsd.org Subject: RE: FW: mount_smbfs Message-ID: <20051124131150.3BC0F43D73@mx1.FreeBSD.org> In-Reply-To: <016501c5f0ef$3a012250$d100a8c0@FRAD.ORG>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, Nov 24, 2005 at 06:39:19AM -0500, Frank Reid wrote:
>
> > Try to backout rev 1.16 of sys/fs/smbfs/smbfs_smb.c and tell me
> > if this helps. This patch was heavily tested on NT-like machines but
may
> > break with w9x family.
>
> Unfortunately, just backing out that one change ("ctx->f_flags |=
> SMBFS_RDD_EOF | SMBFS_RDD_NOCLOSE;") did not correct this problem. By the
> way, I did mention that the W2K/XP machine shares still load and access
> properly on the same machine, right? It's just this one Win ME machine
> share that doesn't any longer.
> Well, there wasn't any other major changes except one done by
> Craig on Wed Nov 16 02:26:25 2005 UTC, which fits into "week or so". I
don't
> see right now how it can break ME machines. Hm, only if it inadvertently
> changes order of some operations.
I tried reverting to smbfs_vfsops.c 1.3.6, but after doing so all shares
(including the W2K) refused to mount with an error "mount_smbfs: mount
error: " so there must be more to it than just the single file. I wish I
could be of more help on this for you.
Frank
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20051124131150.3BC0F43D73>