- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- bdf lies about how many inodes are free
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
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-04-2006 06:35 AM
тАО04-04-2006 06:35 AM
This is not a timing error. When the filesystem is in this state "touch" will fail to create new files.
I think this bug existed in 11.00 and possibly in 10.20 too. These are very large filesystems as witnessed by the "fstyp" output. We never run either of the fsadm "-d" or "-e" functions.
Particulars:
Running "/usr/sbin/mkfs -F vxfs -m /dev/vgfbr2/rlvol17" reports:
mkfs -F vxfs -o ninode=unlimited,bsize=1024,version=4,inosize=256,logsize=1024,nolargefiles /dev/vgfbr2/rlvol17 131072000
Running "fstyp -v /dev/vgfbr2/rlvol17" reports:
vxfs
version: 4
f_bsize: 8192
f_frsize: 1024
f_blocks: 131072000
f_bfree: 4655454
f_bavail: 4364745
f_files: 9547348
f_ffree: 1163860
f_favail: 1163860
f_fsid: 1074200593
f_basetype: vxfs
f_namemax: 254
f_magic: a501fcf5
f_featurebits: 0
f_flag: 0
f_fsindex: 7
f_size: 131072000
Running "fsadm -F vxfs -D /mnt" reports that there are:
dirs searched 1842422
total blocks 161121
immed dirs 1763792
immeds to add 31
dirs to reduce 1128
blocks to reduce 1157
Running "fsadm -F vxfs -E /mnt" reports that there are:
Total Files 4355682
Average File Blks 28
Average Extents 1
Total Free Blks 4654666
blocks used for indirects: 176
% Free blocks in extents smaller than 64 blks: 5.26
% Free blocks in extents smaller than 8 blks: 0.53
% blks allocated to extents 64 blks or larger: 88.34
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО04-04-2006 06:39 AM
тАО04-04-2006 06:39 AM
Re: bdf lies about how many inodes are free
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО04-04-2006 06:42 AM
тАО04-04-2006 06:42 AM
Re: bdf lies about how many inodes are free
Pete
Pete
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО04-04-2006 06:45 AM
тАО04-04-2006 06:45 AM
Re: bdf lies about how many inodes are free
Pete
Pete
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО04-04-2006 07:09 AM
тАО04-04-2006 07:09 AM
Re: bdf lies about how many inodes are free
http://docs.hp.com/en/939/KCParms/KCparam.Ninode.html
says << ninode defines the maximum number of open inodes that can be in memory. >>
This parameter cannot possibly be the issue. First, ninode controls the size of a table which is a RAM cache so that every iget() operation does not require a disk read. When the limit described by ninode is reached the oldest entries in the inode cache in RAM are expired making room for more.
Next, only one of over 90 filesystems on this box has run out of inodes. There is nothing that associates ninode with a single filesystem.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО04-04-2006 07:11 AM
тАО04-04-2006 07:11 AM
Solution- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО04-04-2006 07:17 AM
тАО04-04-2006 07:17 AM
Re: bdf lies about how many inodes are free
Good question but difficult to answer in that the filesystems on this box are holding live, production data and we currently have to move data between filesystems and make symlinks
If the applications expect /mnt/product/dir1/dir2/file
We have a "secret" indirection layer
/mnt/1/product/dir1/dir2/file
and symlinks like /mnt/product/dir1 -> /mnt/1/product/dir1
so we can shuffle directories around between filesystem on live data by mounting a new filesystem
/mnt/2
and copying /mnt/1/product/dir1 to /mnt2/product/dir1
and then changing the symlink so the update is atomic (indivisible in time.)
/mnt/product/dir1 -> /mnt/2/product/dir1
Then going back and reclaming /mnt/1/product/dir1 via rm -r
New incoming data happens at any time so the inode count is constantly changing. I neglected to save the "bdf -i" data when the limit was hit but right now it looks like this due to clean up:
Filesystem kbytes used avail %used iused ifree %iuse Mounted on
/dev/vgfbr2/lvol17 131072000 126309067 4484901 97% 8305907 1190733 87% /mnt
Using GNU df:
gdf -i .
Filesystem Inodes IUsed IFree IUse% Mounted on
/dev/vgfbr2/lvol17 9496660 8305931 1190729 87% /repository/rep24
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО04-04-2006 07:22 AM
тАО04-04-2006 07:22 AM
Re: bdf lies about how many inodes are free
Oh, this might be it. I'll get back to you after I see about running fsadm to turn on large files.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО04-04-2006 07:26 AM
тАО04-04-2006 07:26 AM
Re: bdf lies about how many inodes are free
Sounds like a global limit in the kernel may be hit. The an inode limit for the system is being breached.
ninode 476 - ((NPROC+16+MAXUSERS)+32+(2*NPTY))
vnode_cd_hash_locks 128 - 128
vnode_hash_locks 128 - 128
vx_ninode 0 - 0
vx_ninode is probably not set to zero like on this system, which would allow it to go to any number it likes. The problem with leaving it like the above system is there is a huge performance cost.
A. Clay's analysis of filestructure is also a likely cause, except the individual filesystems do not show being out of inodes. I can't explain that discrepency.
btw, computer programs are incapable of lying. They merely produce inaccurate results. Have you looked for patches for this issue?
SEP
Owner of ISN Corporation
http://isnamerica.com
http://hpuxconsulting.com
Sponsor: http://hpux.ws
Twitter: http://twitter.com/hpuxlinux
Founder http://newdatacloud.com
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО04-04-2006 08:44 AM
тАО04-04-2006 08:44 AM
Re: bdf lies about how many inodes are free
This appears to be due to hitting the 2GB limit on the size of the structures used to hold inodes on disk.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО04-04-2006 08:47 AM
тАО04-04-2006 08:47 AM
Re: bdf lies about how many inodes are free
Indeed, there is a paper describing just how poorly 'ninode' is understood:
http://docs.hp.com/en/5580/Misconfigured_Resources.pdf
Regards!
...JRF...
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО04-04-2006 08:47 AM
тАО04-04-2006 08:47 AM
Re: bdf lies about how many inodes are free
fsadm -F vxfs -o largefiles /mnt
since in 32-bit mode you can hit the 2 GB limit of the size of the data structures used to hold inodes so even dynamic inode allocation will fail for want of table address space not data space.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО04-04-2006 02:12 PM
тАО04-04-2006 02:12 PM
Re: bdf lies about how many inodes are free
Bill Hassell, sysadmin