- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- fsadm and SAM
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
Discussions
Discussions
Forums
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
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
тАО04-29-2003 01:43 AM
тАО04-29-2003 01:43 AM
fsadm and SAM
i have a file system "/u05"
on vxfs. I wanted to convert it to handle large files so
i did a umount /u05 and fsadm -F vxfs -o largefiles /dev/vg05/lvol1
i get this error "vxfs fsadm: /dev/xpvg10/lvol1 is not the root inode of a vxfs file sytem"
then i tried using SAM to convert /u05 to largefiles..
SAM-> disks n filesystems -> filesystems -> action -> modify - allow large files and it worked! i was wondering what specific command SAM used to make the conversion possible.
thanks in advance
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО04-29-2003 01:49 AM
тАО04-29-2003 01:49 AM
Re: fsadm and SAM
You don't have to umount the file system.
You should just do:
fsadm -Fvxfs -o largefiles /u05
good luck
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО04-29-2003 01:51 AM
тАО04-29-2003 01:51 AM
Re: fsadm and SAM
the error and the command mention a different vg. was this a typo?
Donald
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО04-29-2003 01:53 AM
тАО04-29-2003 01:53 AM
Re: fsadm and SAM
To see what sam did, check /var/sam/log/samlog
Hope you'll find it,
Tom
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО04-29-2003 01:55 AM
тАО04-29-2003 01:55 AM
Re: fsadm and SAM
I think I once got the same error and tried specifying the raw device insted: in your case it would have been /dev/vg05/rlvol1,
but you can check what sam did by looking in:/var/sam/log/samlog
However, when you have converted a filesystem to "largefiles" then check that your mount options for the filesystem are ok in /etc/fstab; it should say "largefiles" instead of "nolargefiles" for the file system in question, else it cannot be mounted again, e.g. when you boot.
regards,
John K.
inst
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО04-29-2003 01:59 AM
тАО04-29-2003 01:59 AM
Re: fsadm and SAM
Please change that to largefiles
Thanks
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО05-01-2003 06:34 PM
тАО05-01-2003 06:34 PM
Re: fsadm and SAM
check inode use rate
# glance -t
or
# bdf -i
if you use more than 100% inode, change kernel parameter :inode
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-14-2003 07:23 AM
тАО07-14-2003 07:23 AM
Re: fsadm and SAM
fsadm -Fvxfs -o largefiles /dev/vg05/rlvol1
I know, fsadm should really tell you that the device is a block device instead of some criptic "root inode" error.
To verify your change, use the command:
fsadm -Fvxfs /dev/vg05/rlvol1
you should see "largefiles".
Remember to change your /etc/fstab and include "largefiles" on the line for this filesystem.
Jeff
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-14-2003 08:08 AM
тАО07-14-2003 08:08 AM
Re: fsadm and SAM
example, if fsadm is used to set the largefiles flag, but nolargefiles
is specified as a mount option in /etc/fstab, the files system is not
mountable.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-15-2003 01:36 AM
тАО07-15-2003 01:36 AM
Re: fsadm and SAM
You sure about the Volume Group beacuse you mention vg05
By default root logical volume lvol1 lies in /dev/vg00
pls check this then try the fsadm command
can you put the bdf output pls