- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- file system full (1 block extent)
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
06-24-2004 11:26 PM
06-24-2004 11:26 PM
I am trying to copy a file (size 800MG) within it own folder, on a volume that has 2 GB free,
however each time I run the copy command I get the following error message -
root@cracker:/bcv1/p2plog02/export # cp p2pdub75p.log p2pdub75p.log_old
vxfs: mesg 001: vx_nospace - /dev/bcv_vgp2logs/lvol2 file system full (1 block extent)
cp: bad copy to p2pdub75p.log_old: write: No space left on device
any ideas welcome ???
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-24-2004 11:33 PM
06-24-2004 11:33 PM
Re: file system full (1 block extent)
Check for any process that has opened this filesystem . It may be the case that a small file is open in memory and has been modified recently to a large size.
check the space with "du" and compare it with df o/p
Kaps
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-24-2004 11:42 PM
06-24-2004 11:42 PM
Re: file system full (1 block extent)
here is the output from du and df
root@cracker:/bcv1/p2plog02 # du -ks
du: bad status < ./export/oracle_pipe >
2038474 .
root@cracker:/bcv1/p2plog02 # df -k /bcv1/p2plog02
/bcv1/p2plog02 (/dev/bcv_vgp2logs/lvol2) : 4272188 total allocated Kb
2150460 free allocated Kb
2121728 used allocated Kb
49 % allocation used
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-24-2004 11:59 PM
06-24-2004 11:59 PM
Re: file system full (1 block extent)
do you have lsof installed??
get it from
http://hpux.connect.org.uk/hppd/hpux/Sysadmin/lsof-4.71/
if you have lsof already, please confirm with the lsof utility
with best wishes
Naveej
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-25-2004 12:05 AM
06-25-2004 12:05 AM
Re: file system full (1 block extent)
I have seen this problem once when the source filesystem was largefile enabled but the target filesystem was not.
You could try to check that.
manish
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-25-2004 12:09 AM
06-25-2004 12:09 AM
Re: file system full (1 block extent)
Regds
Kaps
):-Hi naveej ;)
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-25-2004 01:32 AM
06-25-2004 01:32 AM
Re: file system full (1 block extent)
what am to look for ?
the output is too big to put into the forum,
thanks,
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-25-2004 03:33 AM
06-25-2004 03:33 AM
Re: file system full (1 block extent)
On a nightly batch job on a separate server a pipe is created to gzip the output of export from an oracle db. The name pipe was put in there as space was filling up doing it in a linear fashion.
This volume then gets ghost imaged to the other server and once there does not have any inode, thus cannot do any thing to the file. Other symtoms are cannot cp or vi any files on that volume,
Must wait until next week to run tests.
Any suggestions still welcome.
----------- copy from script ----------------
mkfifo oracle_pipe
/usr/contrib/bin/gzip -c < oracle_pipe > p2pdub75p.dmp.gz &
$ORACLE_HOME/bin/exp parfile=/p2plog02/export/p2pdub75pexp.par
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-25-2004 05:24 AM
06-25-2004 05:24 AM
Re: file system full (1 block extent)
The quick and dirty soltion to fix your problem would be to reboot your system.
Best of luck.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-25-2004 05:32 AM
06-25-2004 05:32 AM
Re: file system full (1 block extent)
Kaps
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-25-2004 05:37 AM
06-25-2004 05:37 AM
SolutionMake sure the filesystem is mounted. Maybe its in root and not where you think it is. bdf
There has to be a factor being missed here. Even if you were gzipping the file and there were two copies during compression then you should have 400 MB to spare.
So, some process has a file handle open on the filesystem that needs to be closed.
fuser -cu /filesysetm
fuser -cuk /filesystem
It will kill all processes so you may want to take the lsof and check approach.
Or boot the box and perform the file copy after.
Also, since this is your first question, please take the time to assign points to the answers that helped you.
Regards,
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
06-30-2004 02:09 AM
06-30-2004 02:09 AM
Re: file system full (1 block extent)
I am still none the wiser !!!
used lsof but found no open files
used fuser -cu /bcv1/p2plog02
both filesystems are configured for largefiles
The named pipe was a red herring, did not have any effect on subsequent days after deleting the pipe
cannot think of anything else ?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-30-2004 02:35 AM
06-30-2004 02:35 AM
Re: file system full (1 block extent)
please post output of
# du -sk /bcv1/p2plog02
# bdf
Best regards,
Ettore
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-30-2004 03:00 AM
06-30-2004 03:00 AM
Re: file system full (1 block extent)
as requested -
root@cracker:/ # du -sk /bcv1/p2plog02
2052829 /bcv1/p2plog02
output from bdf -
/dev/bcv_vgp2logs/lvol2 4415488 2121728 2150461 50% /bcv1/p2plog02
-nigel
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-30-2004 08:19 PM
06-30-2004 08:19 PM
Re: file system full (1 block extent)
How ? I dont know
Using fuser I found a process that had /bcv1/p2plog02 as its current dir and had a file open. The process was a 'sh' and had been hanging around for months.
We killed the process yesterday and there was no effect, but this morning after the ghost copy to this server it all worked OK !
has anybody any idea what went on here ?
thanks to all for your help,
-nigel.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-30-2004 09:01 PM
06-30-2004 09:01 PM
Re: file system full (1 block extent)
Message: 001
NOTICE: msgcnt x: vxfs: mesg 001: vx_nospace - mount_point file system
full (n block extent)
Explanation
The file system is out of space. Often, there is plenty of space and
one runaway process used up all the remaining free space. In other
cases, the available free space becomes fragmented and unusable for
some files.
Action
Monitor the free space in the file system and prevent it from becoming
full. If a runaway process has used up all the space, stop that
process, find the files created by the process, and remove them. If the
file system is out of space, remove files, defragment, or expand the
file system. To remove files, use the find command to locate the files
that are to be removed. To get the most space with the least amount of
work, remove large files or file trees that are no longer needed. To
defragment or expand the file system, use fsadm (see the fsadm(1M)
manual page).
Regards,
Robert-Jan
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-30-2004 10:35 PM
06-30-2004 10:35 PM
Re: file system full (1 block extent)
it is an odd situation!
If you assign points then other people in future could notice who helped you better.
Thanks for your collaboration!
No points for me please...
Best regards,
Ettore