Date: Wed, 19 Jun 2002 11:04:30 +0200 (CEST) From: Lukas Ertl <le@univie.ac.at> To: FreeBSD-gnats-submit@FreeBSD.org Subject: kern/39502: can't write on smbfs with scp Message-ID: <200206190904.g5J94UaO006023@pcle2.cc.univie.ac.at>
next in thread | raw e-mail | index | archive | help
>Number: 39502 >Category: kern >Synopsis: can't write on smbfs with scp >Confidential: no >Severity: serious >Priority: medium >Responsible: freebsd-bugs >State: open >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Wed Jun 19 02:10:01 PDT 2002 >Closed-Date: >Last-Modified: >Originator: Lukas Ertl >Release: FreeBSD 4.6-STABLE i386 >Organization: >Environment: System: FreeBSD pcle2.cc.univie.ac.at 4.6-STABLE FreeBSD 4.6-STABLE #0: Mon Jun 17 15:47:18 CEST 2002 le@pcle2.cc.univie.ac.at:/usr/obj/usr/src/sys/PCLE2 i386 >Description: I'm not able to write a file on an smbfs using scp. If /foobar is a locally mounted smbfs from a remote Samba server, then $ scp file.bla user@host:/foobar and $ scp user@host:file.bla /foobar both fail, the former with "lost connection", the latter with "Bad address" and "Write failed flushing stdout buffer. write stdout: Broken pipe". In both cases the file is created on the smbfs but has 0 bytes length. (Copying a file locally using cp works fine, though.) The SMB server that exports the share is Samba 2.2.5-pre1. The machine that mounts the share is 4.6-STABLE. >How-To-Repeat: Mount a Samba share using mount_smbfs, copy a file to it using scp. >Fix: >Release-Note: >Audit-Trail: >Unformatted: To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200206190904.g5J94UaO006023>