Apple products and storage drive manufacturers report drive capacity differently


 
Thread Tools Search this Thread
Operating Systems OS X (Apple) OS X Support RSS Apple products and storage drive manufacturers report drive capacity differently
# 1  
Old 11-24-2008
Apple products and storage drive manufacturers report drive capacity differently

The storage device drive capacity stated in the product specification may be lower than what is reported by Apple products.

More from Apple OS X Support ...
Login or Register to Ask a Question

Previous Thread | Next Thread

8 More Discussions You Might Find Interesting

1. AIX

Performance metrics between Dual Storage IOA versus other drive configurations

Greetings! We ordered a bunch of P7s as part of a hardware upgrade and I was made aware of the Dual Storage IOA configuration. This is something we hadn't fully considered and I was wondering if anyone had done any performance tests using this setup. All our IBM rep told us was "it's slower" and... (1 Reply)
Discussion started by: Mike Brendan
1 Replies

2. UNIX for Dummies Questions & Answers

Need help to move .csv file from UNIX path to windows shared drive or c:\ drive

Hi Guys, Can any one help me on this. I need help to move .csv/.xls file from unix path to windows shared drive or c:\ drive? Regards, LKR (1 Reply)
Discussion started by: lakshmanraok117
1 Replies

3. Filesystems, Disks and Memory

Different partitions of a drive behaving differently in Windows

I have a memory card of my Nokia N73 attached to laptop. There are a few partitions. Why all partitions behave differently? As clear from the attachments, for some partition, delete option is disabled. See 'Disk 1' which is my memory card. Here, patition 'G' (CHECK), i created in windows. The... (6 Replies)
Discussion started by: ravisingh
6 Replies

4. Solaris

Generic drive in a Sun Storage Array?

With a sun storage array j4200 with a failed drive. It's got 11 other drive right now running seagate's ST314655SSUN146G I'm about to replace that one drive with seagate's ST3146356SS drive. Do anyone see this as a problem to use non-Sun drives in Sun storage array or mixing the two... (9 Replies)
Discussion started by: JT-KGY
9 Replies

5. Hardware

How to Clone a Drive with 512 byte Sectors to a Drive with 4096 bytes/sector (AF)?

I have a 320 GB drive which dual boots Windows and Debian: Disk /dev/sda: 320.1 GB, 320072933376 bytes 255 heads, 63 sectors/track, 38913 cylinders, total 625142448 sectors Units = sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal):... (0 Replies)
Discussion started by: phillipsoasis
0 Replies

6. SCO

mounting USB floppy drive /Flash drive in OSR 6.0

Can anybody help me out to mount USB flash /floppy drive in sco openserver 6.0 . (5 Replies)
Discussion started by: sureshdrajan
5 Replies

7. UNIX for Dummies Questions & Answers

Map Drive From Windows To Apache Shared Drive?

Anyone know how I can map a windows drive to an apache shared drive? In my httpd.conf file, I have: Alias /merc_rpts/ "/u/merc_rpts/" <Directory "/u/merc_rpts"> Options Indexes </Directory> I'm able to bring up a browser and see the contents of this folder. In... (0 Replies)
Discussion started by: gseyforth
0 Replies

8. UNIX for Dummies Questions & Answers

How to transfer files from UNIX to my own Hard drive storage?

I will leave the University I am working, but I need to backup and transfer my research data from UNIX system in our department to my own 750G Hard Drive Storage. But I am not familiar with UNIX. How to do this? Thank you. (5 Replies)
Discussion started by: fishwater00
5 Replies
Login or Register to Ask a Question
FSYNC(2)						      BSD System Calls Manual							  FSYNC(2)

NAME
fsync -- synchronize a file's in-core state with that on disk SYNOPSIS
#include <unistd.h> int fsync(int fildes); DESCRIPTION
fsync() causes all modified data and attributes of fildes to be moved to a permanent storage device. This normally results in all in-core modified copies of buffers for the associated file to be written to a disk. Note that while fsync() will flush all data from the host to the drive (i.e. the "permanent storage device"), the drive itself may not physi- cally write the data to the platters for quite some time and it may be written in an out-of-order sequence. Specifically, if the drive loses power or the OS crashes, the application may find that only some or none of their data was written. The disk drive may also re-order the data so that later writes may be present, while earlier writes are not. This is not a theoretical edge case. This scenario is easily reproduced with real world workloads and drive power failures. For applications that require tighter guarantees about the integrity of their data, Mac OS X provides the F_FULLFSYNC fcntl. The F_FULLFSYNC fcntl asks the drive to flush all buffered data to permanent storage. Applications, such as databases, that require a strict ordering of writes should use F_FULLFSYNC to ensure that their data is written in the order they expect. Please see fcntl(2) for more detail. RETURN VALUES
The fsync() function returns the value 0 if successful; otherwise the value -1 is returned and the global variable errno is set to indicate the error. ERRORS
The fsync() system call will fail if: [EBADF] fildes is not a valid descriptor. [EINTR] Its execution is interrupted by a signal. [EINVAL] fildes refers to a file type (e.g., a socket) that does not support this operation. [EIO] An I/O error occurred while reading from or writing to the file system. If a queued I/O operation fails, fsync() may fail with any of the errors defined for read(2) or write(2). SEE ALSO
fcntl(2), read(2), sync(2), write(2), sync(8), update(8) HISTORY
The fsync() function call appeared in 4.2BSD. 4.2 Berkeley Distribution June 4, 1993 4.2 Berkeley Distribution