SCOUG-HELP Mailing List Archives
Return to [ 28 |
July |
2002 ]
>> Next Message >>
Content Type: text/plain
=====================================================
If you are responding to someone asking for help who
may not be a member of this list, be sure to use the
REPLY TO ALL feature of your email program.
=====================================================
Sandy Shapiro wrote:
>
> I found that 2 GB was the largest file I could create.
Hi Sandy,
I ran into the same problem a while back. It's a
file system limitation -- HPFS has a maximum file
size of 2 GB. (JFS doesn't have this restriction.)
- Peter
Here's the chart:
OS/2 File System Comparison Chart
The chart on the following pages compares the characteristics of four file systems: JFS, 386 HPFS,
HPFS, and FAT.
Note that when 386 HPFS is installed, it replaces HPFS.
File System Comparison: JFS, 386 HPFS, HPFS, and FAT
Characteristic Journaled File 386 High High Performance FAT File System
System (JFS) Performance File File System (HPFS)
System (386 HPFS)
Maximum volume size 2TB (terabytes) 64GB (gigabytes) 64GB (gigabytes) 2GB (gigabytes)
Maximum file size 2TB (terabytes) 2GB (gigabytes) 2GB (gigabytes) 2GB (gigabytes)
Maximum file name 254 characters 254 characters 254 characters 11 (8.3 format)
length (bytes) (bytes) (bytes) characters
Allows spaces and Yes Yes Yes No; however, a
periods in file period is required
names between file name
and extension
Standard file and Within file system Within file system Within file system Within file system
directory attributes
(bit flags)
Extended attributes Within file system Within file system Within file system In a separate file
(64KB text or binary
with keywords)
Maximum path length 260 characters 260 characters 260 characters 64 characters
(bytes) (bytes) (bytes) (bytes)
Bootable file systemNo Yes Yes Yes
Logical volume type LVM only LVM or LVM or LVM or
compatibility (mustcompatibility compatibility
be compatibility
for Fault
Tolerance)
Allows dynamic Yes No No No
volume expansion
File system scales Yes No No No
up when using SMP
Allows for fault No Yes No No
tolerance
Allows for local No Yes No No
security
Requires a separate No Yes No No
proof of license
during installation
Average wasted space1/2 block size (256 1/2 sector (256 1/2 sector (256 1/2 cluster (1KB to
per file to 2048 bytes) bytes) bytes) 16KB),
approximately
0.001% of volume
Allocation Near each file in Near each file in Near each file in Centralized near
information for its INODE its FNODE its FNODE front of volume
files
Free disk-space Centralized in file Located near free Located near free Centralized near
information structure space in bit maps space in bit maps front of volume
represented by
B+tree
Directory structure Sorted B+tree Sorted B-tree Sorted B-tree Unsorted linear
list; must be
searched
exhaustively
Directory location Close to files it Located near seek Located near seek Root directory at
contains center of volume center of volume front of volume;
others scattered
Read-ahead 32MB Sensitive to data Cache reads in 8KB Optional
type blocks
Cache replacement Segmented least Sensitive to data Modified least Simple least
strategy recently used (LRU) type recently used (LRU)recently used (LRU)
algorithm algorithm algorithm
Write-behind (lazy Optional; can be Optional; can be Optional; can be Optional; can be
write) handled on a handled on a handled on a handled on a
per-file basis per-file basis per-file basis per-file basis
Caching program None; lazy write CACHE386.EXE CACHE.EXE (in the DISKCACHE (in the
parameters can be (values specified CONFIG.SYS file) CONFIG.SYS file)
set on the for the IFS and RUN
IFS=JFS.IFS line in statements in the
the CONFIG.SYS file)CONFIG.SYS file)
and HPFS386.INI
Maximum cache size Physical memory Physical memory 2MB 14MB
available available
Cache threshold No cache threshold Sensitive to data Variable, up to Variable, up to
type 64KB 64KB; 3.5KB default
LAN Server access Within file system Within file system In separate file In separate file
control lists (NET.ACC) (NET.ACC)
=====================================================
To unsubscribe from this list, send an email message
to "steward@scoug.com". In the body of the message,
put the command "unsubscribe scoug-help".
For problems, contact the list owner at
"rollin@scoug.com".
=====================================================
>> Next Message >>
Return to [ 28 |
July |
2002 ]
The Southern California OS/2 User Group
P.O. Box 26904
Santa Ana, CA 92799-6904, USA
Copyright 2001 the Southern California OS/2 User Group. ALL RIGHTS
RESERVED.
SCOUG, Warp Expo West, and Warpfest are trademarks of the Southern California OS/2 User Group.
OS/2, Workplace Shell, and IBM are registered trademarks of International
Business Machines Corporation.
All other trademarks remain the property of their respective owners.
| 
