- Community Home
- >
- Servers and Operating Systems
- >
- Legacy
- >
- HPE 9000 and HPE e3000 Servers
- >
- filesystem larger than the device
HPE 9000 and HPE e3000 Servers
1752252
Members
5039
Online
108785
Solutions
Forums
Categories
Company
Local Language
юдл
back
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
юдл
back
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
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Go to solution
Topic Options
- 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
тАО12-18-2004 01:13 PM
тАО12-18-2004 01:13 PM
Hi all,
I have a problem mounting filesystem. When checking it by fsck, got the following message:
root@czhs0079: fsck -F vxfs -o full -n /dev/vx/dsk/dg01/vol2
file system is larger than device
vxfs fsck: cannot initialize aggregate
from the VxVM point of view the volume seems to be ok:
root@czhs0079: vxprint -g dg01 -htq vol2
v vol2 - ENABLED ACTIVE 614400 SELECT - fsgen
pl vol2-01 vol2 ENABLED ACTIVE 614400 CONCAT - RW
sd dg01disk01-02 vol2-01 dg01disk01 614400 614400 0 c4t0d1 ENA
the disk itself seems to have no problems (no I/O errors in syslog, ioscan shows it CLAIMED). Does it necessarily mean, that the filesystem is corrupted? What can I check more?
I have a problem mounting filesystem. When checking it by fsck, got the following message:
root@czhs0079: fsck -F vxfs -o full -n /dev/vx/dsk/dg01/vol2
file system is larger than device
vxfs fsck: cannot initialize aggregate
from the VxVM point of view the volume seems to be ok:
root@czhs0079: vxprint -g dg01 -htq vol2
v vol2 - ENABLED ACTIVE 614400 SELECT - fsgen
pl vol2-01 vol2 ENABLED ACTIVE 614400 CONCAT - RW
sd dg01disk01-02 vol2-01 dg01disk01 614400 614400 0 c4t0d1 ENA
the disk itself seems to have no problems (no I/O errors in syslog, ioscan shows it CLAIMED). Does it necessarily mean, that the filesystem is corrupted? What can I check more?
Solved! Go to Solution.
3 REPLIES 3
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО12-18-2004 07:54 PM
тАО12-18-2004 07:54 PM
Solution
Hi Jan,
Exact Error Message
file system is larger than device
Details:
Check the size of the file system, using fstyp -v, calculating the number of 512 byte sectors determined by the size (in file system blocks) and bsize (bytes / file system block). Compare this to the size of the device (vxprint -ht for volume, or prtvtoc/format for disk).
The device should be smaller than the file system. The solution is to grow the device (partition or volume) and then the device, and then mount.
This should only have been caused if someone changed the device size so that the file system is bigger than the device. This error message would not have been apparent previous to VERITAS File System 3.2.5. In 3.2.5 and above, the now checks to ensure that the device is at least as large as the file system.
Related Documents:
180766: WARNING: msgcnt x: vxfs: mesg 021: vx_fs_init - mount_point file system validation failure
http://support.veritas.com/docs/180766
http://seer.support.veritas.com
Hope this helps,
Robert-Jan
Exact Error Message
file system is larger than device
Details:
Check the size of the file system, using fstyp -v, calculating the number of 512 byte sectors determined by the size (in file system blocks) and bsize (bytes / file system block). Compare this to the size of the device (vxprint -ht for volume, or prtvtoc/format for disk).
The device should be smaller than the file system. The solution is to grow the device (partition or volume) and then
This should only have been caused if someone changed the device size so that the file system is bigger than the device. This error message would not have been apparent previous to VERITAS File System 3.2.5. In 3.2.5 and above, the
Related Documents:
180766: WARNING: msgcnt x: vxfs: mesg 021: vx_fs_init - mount_point file system validation failure
http://support.veritas.com/docs/180766
http://seer.support.veritas.com
Hope this helps,
Robert-Jan
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО12-19-2004 11:20 AM
тАО12-19-2004 11:20 AM
Re: filesystem larger than the device
If the root user ran the lvreduce command on the logical volume, you will get this message. lvreduce knows nothing about filesystems so it just reduces the lvol (the filesystem's disk). If this has happened, you can use lvextend to put the lvol size back to the original size.
Bill Hassell, sysadmin
Bill Hassell, sysadmin
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО12-19-2004 12:23 PM
тАО12-19-2004 12:23 PM
Re: filesystem larger than the device
Thank you guys for your replies, according to the fstyp the filesystem was 1G in size, volume has only 600M. I'll try to recover the data. Apparently, the volume could not have been resized by vxresize, this one takes care even for the filesystem, right? As far as I know, the vxassist shrinkby/shrinkto doesn't care about the filesystem..
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
News and Events
Support
© Copyright 2024 Hewlett Packard Enterprise Development LP