Hi,
I posted this question a few weeks ago but didn't get a response.
Perhaps if I rephrase it a bit...
After much RTFM-ing I still don't know anything more. My situation is
that I am mounting a share from a Windows 2000 server on my Redhat6.2
box with samba 2.0.7 (compiled from source, not using RPM). I am then
trying to back up this share with Amanda from a third server. When
Amanda connects to the Redhat box, it runs smbclient to discover the
total size of the volume to be dumped to tape. From Amanda's debug info
I am seeing smbclient report a large negative number for the filesize of
the share. This causes Amanda to fail to back up this volume. Amanda
does succeed in backing up the native partitions on this box, so I am
confident that Amanda itself is operating normally.
Here is what I see just doing an ls on the share:
total 7056080
-rwxr-xr-x 1 operator disk 3610983424 Dec 1 06:23 Backup.bkf
-rwxr-xr-x 1 operator disk 3614442496 Nov 12 19:46 fullvolume.bkf
So two 3.6 GB files, for a total of 7.2 GB. Now this is what happens
when Amanda runs smbclient to get the file size:
sendsize: getting size via smbclient for //nitrous/backups level 0
sendsize: running "/usr/bin/smbclient '\\nitrous\backups' XXXXX -d
0 -U
backup -E -c 'archive 0;recurse;du'"
added interface ip=xxx.xxx.xxx.13 bcast=xxx.xxx.xxx.255
nmask=255.255.255.0
34727 blocks of size 262144. 4577 blocks available
Total number of bytes: -1612049408
One note of peculiarity that makes me think it's the large files is that
when I first set up this mount, there was one 500 MB file in there and
it got backed up just fine. Nothing has changed since then except the
files in the share. So I presume that there is some issue with enormous
files that causes smbclient to incorrectly report the total bytes. Can
anyone recommend a solution?
Thanks,
Eric
--
Eric Sproul, Systems Administrator
Cornerstone Networks Inc. (http://www.cstone.net)
-------------------------------------------------
The score was Hydrogen: 2 and Oxygen: 1 when the game was called because
of rain.
If you run "df" or "du" do you get accurate answers ? Check out the "dfree command" parameter in smb.conf. You can specify your own script if necessary. See man 5 smb.conf for details. Cheers Jon Gerdes Network Services GKN Westland Helicopters Ltd>>> "Eric A. Sproul" <esproul@cstone.net> 12/01/00 04:46pm >>>Hi, I posted this question a few weeks ago but didn't get a response. Perhaps if I rephrase it a bit... After much RTFM-ing I still don't know anything more. My situation is that I am mounting a share from a Windows 2000 server on my Redhat6.2 box with samba 2.0.7 (compiled from source, not using RPM). I am then trying to back up this share with Amanda from a third server. When Amanda connects to the Redhat box, it runs smbclient to discover the total size of the volume to be dumped to tape. From Amanda's debug info I am seeing smbclient report a large negative number for the filesize of the share. This causes Amanda to fail to back up this volume. Amanda does succeed in backing up the native partitions on this box, so I am confident that Amanda itself is operating normally. Here is what I see just doing an ls on the share: total 7056080 -rwxr-xr-x 1 operator disk 3610983424 Dec 1 06:23 Backup.bkf -rwxr-xr-x 1 operator disk 3614442496 Nov 12 19:46 fullvolume.bkf So two 3.6 GB files, for a total of 7.2 GB. Now this is what happens when Amanda runs smbclient to get the file size: sendsize: getting size via smbclient for //nitrous/backups level 0 sendsize: running "/usr/bin/smbclient '\\nitrous\backups' XXXXX -d 0 -U backup -E -c 'archive 0;recurse;du'" added interface ip=xxx.xxx.xxx.13 bcast=xxx.xxx.xxx.255 nmask=255.255.255.0 34727 blocks of size 262144. 4577 blocks available Total number of bytes: -1612049408 One note of peculiarity that makes me think it's the large files is that when I first set up this mount, there was one 500 MB file in there and it got backed up just fine. Nothing has changed since then except the files in the share. So I presume that there is some issue with enormous files that causes smbclient to incorrectly report the total bytes. Can anyone recommend a solution? Thanks, Eric -- Eric Sproul, Systems Administrator Cornerstone Networks Inc. (http://www.cstone.net) ------------------------------------------------- The score was Hydrogen: 2 and Oxygen: 1 when the game was called because of rain.
JON GERDES wrote:> > If you run "df" or "du" do you get accurate answers ? Check out the "dfree command" parameter in smb.conf. You can specify your own script if necessary. See man 5 smb.conf for details.Jon, Thanks for the advice. I will try a "dfree" script on tonight's run. Here is the df output: //nitrous/backups 8890112 8334080 556032 94% /mnt/nitrous And the du output: 7429911 /mnt/nitrous Yet the files add up to 7,608,228,864 bytes. -rwxr-xr-x 1 operator disk 3993786368 Dec 1 17:04 Backup.bkf -rwxr-xr-x 1 operator disk 3614442496 Nov 12 19:46 fullvolume.bkf So that doesn't match but maybe the dfree script will help nonetheless. I'll follow up tomorrow. Thanks! Eric -- Eric Sproul, Systems Administrator Cornerstone Networks Inc. (http://www.cstone.net) ------------------------------------------------- The score was Hydrogen: 2 and Oxygen: 1 when the game was called because of rain.
Sorry, I wasn't watching properly ... You are correct that dfree will not be much use for a share *from* an NT box *to* smbclient. One thought is you may have hit a file size limitation on Linux AFAIK ext2 is limited to 2Gb files for example, so its possible that Samba is affected in the same way. I'll try duplicating your problem Cheers JG>>> "Eric A. Sproul" <esproul@cstone.net> 12/05/00 02:35pm >>>"Eric A. Sproul" wrote:> > JON GERDES wrote: > > > > If you run "df" or "du" do you get accurate answers ? Check out the "dfree command" parameter in smb.conf. You can specify your own script if necessary. See man 5 smb.conf for details. > > Jon, > Thanks for the advice. I will try a "dfree" script on tonight's run.Well it didn't work. Amanda still reports getting garbage from smbclient: calculating for amname '//nitrous/backups', dirname '//nitrous/backups' sendsize: getting size via smbclient for //nitrous/backups level 0 sendsize: running "/usr/bin/smbclient '\\nitrous\backups' XXXXX -d 0 -U backup -E -c 'archive 0;recurse;du'" added interface ip=xxx.xxx.xxx.13 bcast=xxx.xxx.xxx.255 nmask=255.255.255.0 34727 blocks of size 262144. 15960 blocks available Total number of bytes: -301180928 ..... (no size line match in above smbclient output) If the Unix machine is the client, where would the dfree script come into play? It looks to me as though dfree is for estimating filesystem sizes on a share that is being served out *from* the Unix host. So smbclient seems not to be utilizing it. This is my dfree script: #!/bin/sh df $1 | tail -1 | awk '{print $3" "$4}' And in the smb.conf file: dfree command="/usr/local/samba/bin/dfree /mnt/nitrous" As mentioned before, even with the dfree script, du and df still disagree on the total bytes. I got rid of one of the two 3 GB files (only one file is now present), and now du reports 3,900,182 KB while df reports 4,804,352 KB. And ls reports 3,993,786,368 bytes. I'm lost. I just want to get this sucker backed up! :) Anyone else know what I can do? Thanks, Eric -- Eric Sproul, Systems Administrator Cornerstone Networks Inc. (http://www.cstone.net) ------------------------------------------------- If James Bond was an Amish spy, he would drink buttermilk. Shaken not churned.