Networks

Ask something
Discussion Locked

Netware 3.12: File size is > Volume size

0 helpful
7 replies

by gordonhaas

Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

Under Netware 3.12 have a file that is 1.8 GB. This size is reported by both DIR and NDIR. When checking the Volume (only one volume - SYS:) size with the CHKVOL utility it states the Volume space used is 1 GB. Doing a DIR/W/S produces a used space of 2.8 GB, which is the entire Volume size!! Did an NCOPY of the file to a local C: drive to verify size on non Netware volume and it is indeed 1.8GB after the copy on the target drive. Found a TID at Novell.com about a 4 GB problem producing a similar "reporting size" conflict but can't seem to find a TID identifying this particular "flavor". Has anyone out their encounted this beast.

Thanks in advance
Gordon Haas

7 replies

by p. dickason, cne, mcse, cca

Gordon,
Might you have compression enabled on that volume? Databases for example have alot of empty space and can compress down really small. When you do a NDIR, it will tell you the normal file size and not the compressed size. Let me know.
Pete

by ashar

I suppose, this is NOT "reporting size" problem. Netware version 3.12 and above supports so called "Sparse files". This type of files often used by database applications, there data stored by offset from begining of the file, and, therefore, may have "holes" between fragments of data. If this "holes" are long enough (greater, than block size on the Netware volume), Netware server allocates space only for blocks, filled with information, and when you read data from "holes", server returns hex00 sequences without allocating space for the file. So, the size of one file can exeed the size of a volume.
By the way, as I know, data compression, mensiond in previous answer, was introduced in version 4.

by thunderchief

I have encountered similar size reporting problems in NW 3.12. Always related to large database files. After applying the latest patches from Novell the problem has not recurred. However, it is recommended that you keep your database files in their own volume, for one thing it makes tracking these problems down easier.

John

This discussion is closed to new replies.