- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Re: After extending 100% FS in SAM, changes did no...
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Forums
Discussions
Discussions
Discussions
Forums
Discussions
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-18-2003 09:28 PM
03-18-2003 09:28 PM
After extending 100% FS in SAM, changes did not reflect
I extended a 20GB FS (named u04) to 22 GB using SAM. It is already at 100% util. (0 space left) when I extended it.
If I look at the space using bdf, space is still the same (20GB) while on SAM it says 22GB. Any ideas why the space does not reflect
I cannot umount the FS as it is being used by Oracle. By the way the FS contains Oracle DBF's.
Thanks,
Tope
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-18-2003 09:39 PM
03-18-2003 09:39 PM
Re: After extending 100% FS in SAM, changes did not reflect
You need to unmount the file system while extending.
If you have OnLine JFS installed, then you can do this without unmounting.
from your post it looks like you don't have JFS installed, so you need to unmount file system before extending it.
one more thing is you must use
#extendfs /dev/vgxx/rlvolx
after extending using lvextend
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-18-2003 09:43 PM
03-18-2003 09:43 PM
Re: After extending 100% FS in SAM, changes did not reflect
you can see if you have online JFS by lookinhg for it in the output of 'swlist'
# swlist -l fileset | grep -i online
At a guess I would say that you don't online JFS and SAM has only extended the logical volume size, not the filesystem itself.
Here is a brief summation on how it is done on the command line if online JFS is installed.
# lvextend -L 22528 /dev/myvg/mylvol
# fsadm -F vxfs -b 23068672 /u04
If the fsadm fails then you don't have it installed. This piece of software requires a license.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-18-2003 10:00 PM
03-18-2003 10:00 PM
Re: After extending 100% FS in SAM, changes did not reflect
I have tried extending another FS (/u05) from 20 to 22 GB and it was successful. It has about 30 MB of space left when I extended it.
I think the problem is caused by 0 space left on device when I extended it. Any other ideas?
Thanks,
Tope
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-18-2003 10:12 PM
03-18-2003 10:12 PM
Re: After extending 100% FS in SAM, changes did not reflect
your command
swlist -l fileset|grep -i vxfs
lists base veritas file system which comes by default along with OS.
If you have less space lvextend will thro the error saying "insufficient blocks".
your problem is either you don't have online JFS or you haven't used exendfs after lvextend