Inodes are dynamically allocated in VxFS, so that's not likely to be the cause (unless you have a multiple billion inodes or a very, very old disk layout). Enhancements were a couple versions ago to reserve space internally within the file system so users wouldn't have to manually reserve free space. See: http://seer.entsupport.symantec.com/docs/249933.htm But you said you're running on version 5. So it sounds like you've hit one of the 'rare cases' What is the exact size of the file system? I seem to recall the rare cases involved being a multiple of some number. Regards, Scott
________________________________ From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Rajiv Gunja Sent: Monday, March 17, 2008 11:10 AM To: Sengor Cc: Asim Zuberi; Doug Hughes; veritas-vx@mailman.eng.auburn.edu Subject: Re: [Veritas-vx] vxfs filesystem full - can not expand. -- That is very odd. How are you doing on i-nodes? Too many / any free left? -- RM fails, how about mv (move) there should be a way to free up i-nodes and or space. -GGR On Sun, Mar 16, 2008 at 11:31 PM, Sengor <[EMAIL PROTECTED]> wrote: On 3/17/08, Asim Zuberi <[EMAIL PROTECTED]> wrote: > Did you consider doing "fsck -F vxfs" on the filesystem? Nope, since we need the fs to remain online. -- _________________________________/ sengork.blogspot.com /¯¯¯¯
_______________________________________________ Veritas-vx maillist - Veritas-vx@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-vx
