Re: When I attempt to save a workbook I get a disk is full error

In article <33103DC9-4477-456D-83AE-B2A200DE227E@xxxxxxxxxxxxx>, =?Utf-8?B?SmltIEFiZWw=?= <JimAbel@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote:
I have discovered some more information with this issue. I believe that the
disk is full error is false the drive has 50 GB free. When doing some trial
and error I found that sometimes I could get the changes to save and other
times I could not. I keep expanding the workbook until I consistamtly got
the error to occur@3MB in size. What I noticed was that the time it took got
significantly longer for it to save to the network location. I am now
thinking that there may be a timeout issue or that the network drops the save
operation. I will further investigate this avenue and see if I can find
something along those lines.

Does sound promising. Note that a network drive usually shows all it's space
as free even if there are many users and your allocated share of it is a lot
less. Can you check your disk quota allocation on that drive ? Users would
usually have a lot less than 50 GB allocated to them.

Good luck. :)

"Bruce Sinclair" wrote:

In article <714162D1-1A20-4702-877C-3E64D43502B8@xxxxxxxxxxxxx>,
=?Utf-8?B?SmltIEFiZWw=?= <JimAbel@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote:
Thanks Bruce, I am unclear as to where I look for this reference. Can you
add some more detail as to where I can get to this article?

Article ? Sorry, don't know what you mean. I do know I've had disk full
errors (particularly on a network drive) when it wasn't and the temporary
file was the problem. It's worse (obviously) for seriously large files. :)
I admit I'm not certain beyond doubt that xl does this now or with all
versions, but it is worth a look. And the dung out/ ask for more space fix
ought to work anyway. :)

"Bruce Sinclair" wrote:

In article <076FA966-0F43-423E-B3C1-5A77AD729081@xxxxxxxxxxxxx>,
=?Utf-8?B?SmltIEFiZWw=?= <JimAbel@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote:
I have a copy of Excel 2003 installed on a server. It is in a share were
4 people on out team can access throuh a mapped drive. When any of us
the workbook make some changes and attempt to save it we get a messavebox

that says the disk is full.

This in not true.
If we save the workbook to our desttop, make the edits save it and copy
back to the server they are saved for the next person to see without a

This adds a good deal of time to the changes over the month and we would
like to know ifanyone can tell us why we cannot edit the file directly on
server. It contains a data source to a database that populates the

with some data, if that matters.

Any ideas of why we have this behavior and what we could do so that we
simply open the file in place make the changes and then save it , would
greatly appreciated.

Are you really close to your disk limit (ie if you saved 2 files the same
size as the one you are talking about, would you get the message on the
second save but not the first ?). The first thing XL does when opening is
create a temp file in the directory where the original is. (copy 1).
When you try to save it, I think it creates a new version, then deletes
temp file. (copy 2). That it works fine on the desktops is an indicator.
Suggest you have a dung out in the shared directory or ask for more disk
space. :)


Relevant Pages

  • Re: Block size confusion.
    ... The physical disk will have "blocks" - i.e. all physical reads and ... the laws of physics. ... For file systems with a few big files, ... allocation here. ...
  • Re: [Lit.] Buffer overruns
    ... part of the issue with page backing store allocation policy is whether ... once a disk location is allocated on ... you can still overcommit a no-dup policy ... ... unixes during the 90s that had "lazy" swap but a dup policty (once ...
  • Re: ldev lists in classes - DISC
    ... the MPE/iX file space allocation policies but I do remember using a trick on ... You would create a number of disk entries for one disk and few ... MPE/iX R&D Architect ... > If the user wanted to artificially load LDev 2 more heavily, ...
  • Re: [PATCH] Revert "writeback: limit write_cache_pages integrity scanning to current EOF"
    ... entire allocation unit is zeroed. ... allocated blocks past EOF that have to be zeroed when extending the ... blocks of the allocation unit from being written back to disk. ... between the old EOF and the new EOF on each extending write. ...
  • Linux VFS architecture questions
    ... fragmenting the allocation bitmap, catalog file, etc, such that each 1/8 or so of the disk contains its own allocation bitmap describing its contents, its own set of files or directories, etc. ... The allocator would largely try to keep individual btree fragments cohesive, such that one of the 1/8th divisions of the disk would only have pertinent data for itself. ... I'm trying to write up a "Linux Disk-Based Filesystem Developers Guide" based on what I learn, but it's remarkably sparse so far. ...