🚀 go-pugleaf

> We just recently had a 36 gig disk array added to our Novell server. A
> 10 gig volume (the balance to be assigned as needed) was allocated for
> the Mac users. Even though the space shows up as 10 gig on a PC that
> is hooked up the to server the Macs only see 2 gig. I tried to max out
> the space just to make sure it's really only 2 gig.
> 
> Funny thing is the current disk array that prior to installing the new
> 36 gig drive though it SHOWS 2 gig in total (in window header)
> actually is 6 gig and I was able to calculate all the folders and
> confirmed this. Most of the Macs are running system 7.5.1. Strange is
> it not?
> 
> 
> Is there someway to get the rest of the space to show up on the Macs.
> Any suggestions would be greatly appreciated.


From the Mac Storage FAQ:


3.07  What's the maximum size of a Macintosh volume?
----------------------------------------------------

> Pre-System 7.5 -- 2 gigabytes 
> System 7.5     -- 4 gigabytes
> System 7.5.2   -- 2048 gigabytes (2 terabytes)

Currently, System 7.5.2 only works with the Power Macintosh 9500. System
7.5 Update 2.0 -- when released -- will presumably include support for 2
terabyte volumes. 


I don't know how this relates to newtwork volumes, though. 


|Les Jones  |  FAQs for AOL, ClarisWorks, Mac Storage, and ZTerm  |

| ftp://users.aol.com/macfaq   |  I'd give anything for a new car.|
| http://users.aol.com/macfaq  |  Except money. -- Jesse Martin   |

In article <44d5nk$ou0@newsbf02.news.aol.com> macfaq@aol.com "MacFAQ" writes:

> > We just recently had a 36 gig disk array added to our Novell server. A
> > 10 gig volume (the balance to be assigned as needed) was allocated for
> > the Mac users. Even though the space shows up as 10 gig on a PC that
[snip]

Along with the previously mentioned volume space limits for the various
system versions, there seem to be additional limitations in AFP
(Appletalk Filing Protocol) for network volumes.

In my experience problems start to occur as a network volume
*approaches* 2Gb, such as disk full errors and free space being reported
as negative numbers (presumably some internal counter running over its
limit and turning negative).

The only workaround seems to be to partition the volume into smaller
pieces, say around the 1.7Gb range.

-- 
Mark "Kipper" Price               |  No .cig  - I'm a non-smoker!
Research & Development Manager,   |  
Minc Limited, London, UK          |  kippy@minc.demon.co.uk           

In article <812486312snz@minc.demon.co.uk>,
Mark  Kipper  Price  <kippy@minc.demon.co.uk> wrote:
>
>Along with the previously mentioned volume space limits for the various
>system versions, there seem to be additional limitations in AFP
>(Appletalk Filing Protocol) for network volumes.
>
>In my experience problems start to occur as a network volume
>*approaches* 2Gb, such as disk full errors and free space being reported
>as negative numbers (presumably some internal counter running over its
>limit and turning negative).
>
>The only workaround seems to be to partition the volume into smaller
>pieces, say around the 1.7Gb range.

Does anyone else get the feeling that anything apple does to fix the 
problems with local and network file systems won't come soon enough.

I am getting sick of waiting for apple to fix all the anachronisms in the 
current version of the MacOS.
--
__________________________________________________________________________
Erik A. Speckman         Seattle, Washington       Good Brain Doesn't Suck
especkma@reed.edu                                     especkma@halcyon.com
     "The kids of today should defend themselves against the 70's"