> Trying to figure out what this means (other than it couldn't write the > file because it thought it was out of space): > > 12:32:41 (166920.001) Could only write 82944 of 262144 bytes to file > /database/olaprdo/temp04.dbf at file offset 3 gigabytes + 1914412032 > bytes > 12:32:41 (166920.001) Couldn't write to file > /database/olaprdo/temp04.dbf: No space left on device > > The original file was actually 5242888192 bytes. Looking at > the target > filesystem given its current space available I can see that this file > wouldn't have fit. I'm just trying to figure out where it determined > the numbers seen in the first line of the message as they > don't seem to > relate directly either to the filesystem size or the original > file size.
Not sure which numbers you are concerned with, but you're using a 256KB block size, and write() returned an error after 82944 bytes of that block were written. That's 162 disk-drive, 512-byte blocks. If they're computing GB correctly (not like the dumb new ISO standard!), 3GB = 2^30 * 3 = 3221225472, and if it got through 1914412032 more, it was up to 5135637504 before it ran out. Just tack another 107250688 bytes onto that disk and you're good to go. :-) _______________________________________________ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu