public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
* Is there any limit on the bluetooth share folder in linux either in bluez stack or in obex ftp?
@ 2009-09-16  6:33 Sasikiran Maddula
  2009-09-16  6:49 ` Johan Hedberg
  0 siblings, 1 reply; 4+ messages in thread
From: Sasikiran Maddula @ 2009-09-16  6:33 UTC (permalink / raw)
  To: linux-bluetooth@vger.kernel.org

Hi,

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.

Thanks,
Sasikiran.

^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: Is there any limit on the bluetooth share folder in linux either in bluez stack or in obex ftp?
  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
  0 siblings, 1 reply; 4+ messages in thread
From: Johan Hedberg @ 2009-09-16  6:49 UTC (permalink / raw)
  To: Sasikiran Maddula; +Cc: linux-bluetooth@vger.kernel.org

Hi,

On Wed, Sep 16, 2009, Sasikiran Maddula wrote:
> 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.

Johan

^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: Is there any limit on the bluetooth share folder in linux either in bluez stack or in obex ftp?
  2009-09-16  6:49 ` Johan Hedberg
@ 2009-09-16  9:15   ` Sasikiran Maddula
  2009-09-16 14:56     ` Marcel Holtmann
  0 siblings, 1 reply; 4+ messages in thread
From: Sasikiran Maddula @ 2009-09-16  9:15 UTC (permalink / raw)
  To: johan.hedberg, linux-bluetooth@vger.kernel.org

Johan Hedberg wrote:
> Hi,
>
> On Wed, Sep 16, 2009, Sasikiran Maddula wrote:
>   
>> 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.
>
> Johan
>   
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.

Thanks,
Sasikiran.

^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: Is there any limit on the bluetooth share folder in linux either in bluez stack or in obex ftp?
  2009-09-16  9:15   ` Sasikiran Maddula
@ 2009-09-16 14:56     ` Marcel Holtmann
  0 siblings, 0 replies; 4+ messages in thread
From: Marcel Holtmann @ 2009-09-16 14:56 UTC (permalink / raw)
  To: Sasikiran Maddula; +Cc: johan.hedberg, linux-bluetooth@vger.kernel.org

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



^ permalink raw reply	[flat|nested] 4+ messages in thread

end of thread, other threads:[~2009-09-16 14:56 UTC | newest]

Thread overview: 4+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
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 is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox