Thanks to: Ken Zachmann <ken@ella.slis.indiana.edu> Stan.Pietkiewicz@statcan.ca It turns out that growing did not fail due to large-file support. It failed because of fsadm. Fsadm was unable to grow because the file-systems were at 100% utilization. KEN: ################ fsadm often fails when growing filesystems that are full or highly fragmented because it doesn't have enough free space to do its magic. You can do one of two things: 1) move a file (it doesn't have to be very big, a few megs will suffice) to a different filesystem until after you grow the full filesystem, or 2) grow it a little bit (add only a hundred megs to the filesystem even if you added many gigs to the volume size) then try growing it to the full size of the expanded volume (e.g. if the volume was 50GB and you grew it to 60GB but the filesystem resize failed, grow the filesystem by 100MB using fsadm, THEN try growing it to the full 60GB). ken STAN: ################### I've seen this sort of problem in a couple of instances...... If the filesystem is 100%, VxFS will not be able to grow the filesystem. In each case so far, I've had to make some room first; a megabyte or so should do it. Stan _________________________________________________________________ Get your FREE download of MSN Explorer at http://explorer.msn.comReceived on Thu May 17 16:27:38 2001
This archive was generated by hypermail 2.1.8 : Wed Mar 23 2016 - 16:24:55 EDT