Date: Thu, 6 Dec 2018 12:15:19 +0300 From: Yuri Pankov <yuripv@yuripv.net> To: Carson Chittom <carson@wistly.net>, "freebsd-questions@freebsd.org" <freebsd-questions@freebsd.org> Subject: Re: can't copy files >= 1M to NFS share Message-ID: <f0b14b0e-ca65-1d83-1679-3ad9724a7fc2@yuripv.net> In-Reply-To: <20181206020451.DE4E9103AC@mailuser.nyi.internal> References: <20181206020451.DE4E9103AC@mailuser.nyi.internal>
next in thread | previous in thread | raw e-mail | index | archive | help
This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --iZObXB8EpF8cfh0ubJD1mqul1jOnxOEnF Content-Type: multipart/mixed; boundary="FMcj7egAs6rZs9m5puxXfi2TUJviE9QSu"; protected-headers="v1" From: Yuri Pankov <yuripv@yuripv.net> To: Carson Chittom <carson@wistly.net>, "freebsd-questions@freebsd.org" <freebsd-questions@freebsd.org> Message-ID: <f0b14b0e-ca65-1d83-1679-3ad9724a7fc2@yuripv.net> Subject: Re: can't copy files >= 1M to NFS share References: <20181206020451.DE4E9103AC@mailuser.nyi.internal> In-Reply-To: <20181206020451.DE4E9103AC@mailuser.nyi.internal> --FMcj7egAs6rZs9m5puxXfi2TUJviE9QSu Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: quoted-printable Carson Chittom wrote: > I've got an 11.2 system acting as my media server. I'm successfully exp= orting the directory which contains the media files via NFS, so that > they're accessible on my workstation, which is running Windows 10 Pro. = I can read the files fine from the Windows machine using the built-in > Microsoft NFS client, and I can create directories, new files, and so f= orth from the Windows machine in the share. >=20 > The issue is that I can't copy any files greater than or equal to 1M fr= om the Windows system to the NFS share. I confirmed this by using dd > to create a file which is 1023k, which I was able to copy, and one whic= h is 1024k, which I was not. I get the same behavior whether I try to > drag-and-drop into the NFS share, copy-and-paste, or using "copy" in th= e Windows Command Prompt. The error that Windows immediately gives me is= > "Error 0x8007045D: The request could not be performed because of an I/O= device error." (And again, I *don't* get this error if the file is unde= r 1M.) >=20 > I've done some web searches, and there's a fair amount of that particul= ar error code--but nothing that I saw seemed directly relevant > (mostly about timeouts...but I'm getting the error immediately). Maybe= I'm just bad at Google. >=20 > My /etc/exports is unexceptional, literally just the line: >=20 > /usr/local/plexdata -mapall=3Dplex >=20 > Unfortunately, I don't have another system to hand to test mounting the= share. So at this point, I'm not sure where to poke. Is this something = I > can address from the FreeBSD side? A limitation of the Windows NFS cli= ent? Some unfortunate combination of them? >=20 > If anybody can point me in the right direction, I'd be appreciative. FWIW, I just tried this from Windows 10 Pro (Version 1803 OS Build 17134.441) to FreeBSD-12.1 and FreeBSD 13-CURRENT, and I'm NOT seeing the issue (actually I was able to copy a 2GB file), so apparently it's not windows nfs client limitation. --FMcj7egAs6rZs9m5puxXfi2TUJviE9QSu-- --iZObXB8EpF8cfh0ubJD1mqul1jOnxOEnF Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- iQEzBAEBCAAdFiEE+Gq3PsPeLT4tL/9wk4vgf7Eq4WwFAlwI6KcACgkQk4vgf7Eq 4WyClAf/Qw8raM8GgXN3araWLfTkD4qLSTEl54iSTsfw7cCoch13VaCMpP2v7t/R RpO2cs3ySzcS5PNDi5Hs6q3IVL2Rql9l+XPWXFtpTfW4jyLhTlQZHdt43MKHCB1H gQ71JWyQj4BP9XrCMAPYRhFKCfiTzpZCc2JCj5/fwmgZ3SaaDhktuRTiwy7aCSiD Pjj/pC9CRGM1+rqMnyHUA6ehV9CNy6e6rHt7yg41vcn2NFcvl/sLRI4OUbyQQBNl Ozxk5Yp0UpgxhmK0S2miovO+Gx7tOnTJg+KpvvnuapZjFlvp4grrnvseVH8KZqUy b1kSlVh0CIcX9GmifA7jTU1NuO0w6w== =EOIo -----END PGP SIGNATURE----- --iZObXB8EpF8cfh0ubJD1mqul1jOnxOEnF--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?f0b14b0e-ca65-1d83-1679-3ad9724a7fc2>