Hi Jorgen,
   
  Errno 16 means "Mount device busy".  There are three primary causes for this
error:

    1. The file system is too busy to be resized.

       Although resizing a file system requires that the file system be
mounted, one must "freeze" the file system to actually perform the resize. 
Freezing will temporarily prevent new accesses to the file system, but it is 
necessary to wait for pending I/O's to complete. If it is not possible to 
freeze the file system quickly, stating
that the file system is too busy is given up.

    2. The file system has a snapshot file system mounted on it.

       If a snapshot file system was mounted on the file system being
resized, the resize will fail. File systems that have
snapshots mounted on them cannot be resized.

    3. The file system may have corruption and needs to be fsck'd.

        A file system that has experienced structural damage and is marked
for full fsck cannot be resized.

RESOLUTION:

Make sure that the file system does not have any snapshot file system
mounted on it. Attempt the resize when the file      system has less of a
load on it.
If it continues to fail with "errno 16" then unmount the file system,
perform "fsck -o full", remount, and try again.
=


Jørgen Henriksen <[EMAIL PROTECTED]> wrote:
        st1\:*{behavior:url(#default#ieooui) }                 
  Hi,
   
  Just tried to resize a volume in Storage Foundation 4.1, and ended up with 
the following error:
   
  UX:vxfs fsadm: ERROR: V-3-20340: attempt to resize 
/dev/vx/rdsk/dummydg/dummyvol01 failed with errno 16 VxVM vxresize ERROR 
V-5-1-7514 Problem running fsadm command for volume dummyvol01, in diskgroup 
dummydg 
   
  When I tried to fsck the volume, it just aborted. This is an Oracle Rac 
configuration, and I used the “fsclustadm showprimary” and “fsclustadm 
setprimary” together with “vxdctl –c mode” to assure the right host for the 
operation. The vxresize command was issued from VEA, and it made the volume 
unusable, and took down the entire production cluster. The issue was resolved 
by resizing the volume manually with vxassist, and then fsck on the volume. 
Everything is now back to normal, but why did this happen ? Anyone ?
   
  Best regards Jørgen Henriksen
  Ementor AS
  Norway
   

_______________________________________________
Veritas-ha maillist - [email protected]
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-ha



Thanks & Regards,
Munish Dhawan
       
---------------------------------
Got a little couch potato? 
Check out fun summer activities for kids.
_______________________________________________
Veritas-ha maillist  -  [email protected]
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-ha

Reply via email to