Re: Re (3): Apparent disagreement between df and cp.

2012-06-30 Thread Chris Davies
Keith McKenzie wrote: > It was about cp reporting 'no space left on device', whilst df said that > there was space available. The OS reported "No space left on device" (or more accurately, errno 28: ENOSPC) to cp. Rather than trying to guess whether this really meant what it said or whether it wa

Re: Re (3): Apparent disagreement between df and cp.

2012-06-30 Thread Keith McKenzie
On 29 June 2012 23:41, Doug wrote: > On 06/29/2012 05:29 PM, peasth...@shaw.ca wrote: > >> From: Dom >> Date: Thu, 28 Jun 2012 16:02:45 +0100 >> >>> Ok, I've just tested this. It is a FAT filesystem limitation. >>> >> /snip/ > > I've looked at this thread a number of times, but I was then and

Re (4): Apparent disagreement between df and cp.

2012-06-29 Thread peasthope
From: Doug Date: Fri, 29 Jun 2012 18:41:17 -0400 > cp ... none of the options mentions determining the size of a file- > system or the remaining space therein. The primary function seen by the user is copying. The relative size of the projectile and its target are only relevant to the use

Re: Re (3): Apparent disagreement between df and cp.

2012-06-29 Thread Doug
On 06/29/2012 05:29 PM, peasth...@shaw.ca wrote: From: Dom Date: Thu, 28 Jun 2012 16:02:45 +0100 Ok, I've just tested this. It is a FAT filesystem limitation. /snip/ I've looked at this thread a number of times, but I was then and still am puzzled. According to "Linux in a Nutshell," by S

Re (3): Apparent disagreement between df and cp.

2012-06-29 Thread peasthope
From: Dom Date: Thu, 28 Jun 2012 16:02:45 +0100 > Ok, I've just tested this. It is a FAT filesystem limitation. Nice analysis! > On FAT12 (and FAT16, iirc) there is a limit of 512 files in the root > directory. Other directories don't have this limit. I found additional information here. h

Re: Re (2): Apparent disagreement between df and cp.

2012-06-28 Thread Dom
On 28/06/12 16:18, peasth...@shaw.ca wrote: From: Berni Elbourn Date: Thu, 28 Jun 2012 08:32:29 +0100 Are there too many files in target folder? 197 files here whereas Wikipedia mentions 65,460 files for "32 KB" clusters. From: Chris Davies Date: Thu, 28 Jun 2012 08:47:21 +0100 What

Re (2): Apparent disagreement between df and cp.

2012-06-28 Thread peasthope
From: Berni Elbourn Date: Thu, 28 Jun 2012 08:32:29 +0100 > Are there too many files in target folder? 197 files here whereas Wikipedia mentions 65,460 files for "32 KB" clusters. From: Chris Davies Date: Thu, 28 Jun 2012 08:47:21 +0100 > What is the output of "mount | grep sdd1" ...

Re: Apparent disagreement between df and cp.

2012-06-28 Thread Chris Davies
peasth...@shaw.ca wrote: > How can df report MiBs available while cp reports > "No space left on device"? > peter@dalton:~$ df /media/43* > Filesystem 1K-blocks Used Available Use% Mounted on > /dev/sdd1 498648 18840479808 4% /media/4345-A417 It's possible

Re: Apparent disagreement between df and cp.

2012-06-28 Thread Sven Joachim
On 2012-06-28 09:32 +0200, Berni Elbourn wrote: > On 28/06/12 05:45, peasth...@shaw.ca wrote: >> How can df report MiBs available while cp reports >> "No space left on device"? >> >> peter@dalton:~$ df /media/43* >> Filesystem 1K-blocks Used Available Use% Mounted on >> /dev/sdd1

Re: Apparent disagreement between df and cp.

2012-06-28 Thread Berni Elbourn
On 28/06/12 05:45, peasth...@shaw.ca wrote: How can df report MiBs available while cp reports "No space left on device"? peter@dalton:~$ df /media/43* Filesystem 1K-blocks Used Available Use% Mounted on /dev/sdd1 498648 18840479808 4% /media/4345-A417 peter

Apparent disagreement between df and cp.

2012-06-27 Thread peasthope
How can df report MiBs available while cp reports "No space left on device"? peter@dalton:~$ df /media/43* Filesystem 1K-blocks Used Available Use% Mounted on /dev/sdd1 498648 18840479808 4% /media/4345-A417 peter@dalton:~$ ls -l Mail.Text -rw--- 1 peter