public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: Marcel Holtmann <marcel@holtmann.org>
To: Sasikiran Maddula <Madula.Sasikiran@Atheros.com>
Cc: johan.hedberg@gmail.com,
	"linux-bluetooth@vger.kernel.org"
	<linux-bluetooth@vger.kernel.org>
Subject: Re: Is there any limit on the bluetooth share folder in linux either in bluez stack or in obex ftp?
Date: Wed, 16 Sep 2009 07:56:13 -0700	[thread overview]
Message-ID: <1253112973.28416.6.camel@localhost.localdomain> (raw)
In-Reply-To: <4AB0ACA9.8030102@Atheros.com>

Hi Sasikiran,

> >> I tried to send a file of more than 2 GB using bluetooth in linux. It
> >> says "Error while copying. There is not enough space on the destination.
> >> Try to remove files to make space". When I look for more details it says
> >> "There is 2.0GB available, but 2.8GB required", but the file size I am
> >> trying to send is 2.8 GB, also in the other end it has more space than
> >> the file size. I am trying to copy the file from laptop1 to laptop2 with
> >> a share folder as "x" in laptop2. I used several vendor dongles. All of
> >> them behave the same way. When I check for the properties of folder x in
> >> laptop1 it shows as 2.0 GB used and 2.0 GB free. But actually the share
> >> folder is not filled by 2.0GB, but it is more. I used linux 2.6.28 and
> >> 2.6.31 kernel versions with bluez 4.32. I even verified with 2.6.31 with
> >> 4.32 bluez and 2.6.28 with 4.53 bluez. All of them behave the same way.
> >> Could some body suggest me where is the issue and how to rectify the
> >> issue.
> >>     
> >
> > BlueZ comes neither with an OBEX server nor an OBEX client. Which client
> > and server are you using? AFAIK by using standard OBEX FTP the only way
> > for the client to know the amount of free space in the server is through
> > the capability object. Maybe the capability object on server contains
> > false information or then your client is interpreting it incorrectly.
> >
> >   
> By default Linux comes with obex-data-server. I am using that itself. Do 
> you think I need to update that and try. If so can you tell me what 
> version has the fix.

neither from Johan or me you will get help on obex-data-server. We are
focusing on obexd and I don't remember it having any of these issues.

Regards

Marcel



      reply	other threads:[~2009-09-16 14:56 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-16  6:33 Is there any limit on the bluetooth share folder in linux either in bluez stack or in obex ftp? Sasikiran Maddula
2009-09-16  6:49 ` Johan Hedberg
2009-09-16  9:15   ` Sasikiran Maddula
2009-09-16 14:56     ` Marcel Holtmann [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1253112973.28416.6.camel@localhost.localdomain \
    --to=marcel@holtmann.org \
    --cc=Madula.Sasikiran@Atheros.com \
    --cc=johan.hedberg@gmail.com \
    --cc=linux-bluetooth@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox