- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - OpenVMS
- >
- Dfu error message - what is it really saying
Operating System - OpenVMS
1753867
Members
7179
Online
108809
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
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
тАО01-12-2010 05:27 AM
тАО01-12-2010 05:27 AM
Dfu error message - what is it really saying
Running dfu 2.7-A on OpenVMS 8.3 and we got the following message during a defrag:
SYSTEM-W-DEVICEFULL, device full; allocation failure
DFU-E-NOTMOVED, Error moving disk:[dir]file.ext
Does this mean that dfu in working on this file actually caused the disk to fill up or does it mean that dfu in attempting to defrag the file, found that there was not a large enough contiguous file space? Or does it mean something else?
The main thing I am trying to determine is, will dfu actually fill the disk and possibly cause impact to other processes writing to the disk. By the way, yes I know there is a newer version. I am asking this question because I am researching something that happened with the specifications above.
Thanks for any help in advance.
SYSTEM-W-DEVICEFULL, device full; allocation failure
DFU-E-NOTMOVED, Error moving disk:[dir]file.ext
Does this mean that dfu in working on this file actually caused the disk to fill up or does it mean that dfu in attempting to defrag the file, found that there was not a large enough contiguous file space? Or does it mean something else?
The main thing I am trying to determine is, will dfu actually fill the disk and possibly cause impact to other processes writing to the disk. By the way, yes I know there is a newer version. I am asking this question because I am researching something that happened with the specifications above.
Thanks for any help in advance.
2 REPLIES 2
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО01-12-2010 06:40 AM
тАО01-12-2010 06:40 AM
Re: Dfu error message - what is it really saying
I found the error in the manual. I missed it the first time through.
DEVICEFULL: Device has not enough contiguous free space to move the entire file
DEVICEFULL: Device has not enough contiguous free space to move the entire file
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО01-12-2010 12:20 PM
тАО01-12-2010 12:20 PM
Re: Dfu error message - what is it really saying
Mike,
For future reference... use HELP/MESSAGE and you won't need to dig out the manual. See
$ HELP/MESSAGE DEVICEFULL
>will dfu actually fill the disk and
>possibly cause impact to other processes
>writing to the disk
In theory, no. DFU does its best to stay out of the way, and back when there are potential conflicts. I suppose there are some very unlikely race conditions, for example, imagine there is a single free contiguous block exactly the right size for a DFU consolidation. DFU grabs it just before some other application attempts to allocate space. DFU does it's consolidation, then releases the old fragmented blocks. In the mean time the victim application has failed with DEVICEFULL.
I'm not sure if DFU sets an allocaion threshold slightly below 100% of the disk space to prevent this type of scenario (I know there are definitely some limits on how much free space must be present for DFU to proceed). It could also be argued that if the above situation did occur, the application and storage were so close to the edge that the failure would possibly have occurred even without DFU.
Bottom line. Storage is cheap. It's a false economy to operate with inadequate headroom.
For future reference... use HELP/MESSAGE and you won't need to dig out the manual. See
$ HELP/MESSAGE DEVICEFULL
>will dfu actually fill the disk and
>possibly cause impact to other processes
>writing to the disk
In theory, no. DFU does its best to stay out of the way, and back when there are potential conflicts. I suppose there are some very unlikely race conditions, for example, imagine there is a single free contiguous block exactly the right size for a DFU consolidation. DFU grabs it just before some other application attempts to allocate space. DFU does it's consolidation, then releases the old fragmented blocks. In the mean time the victim application has failed with DEVICEFULL.
I'm not sure if DFU sets an allocaion threshold slightly below 100% of the disk space to prevent this type of scenario (I know there are definitely some limits on how much free space must be present for DFU to proceed). It could also be argued that if the above situation did occur, the application and storage were so close to the edge that the failure would possibly have occurred even without DFU.
Bottom line. Storage is cheap. It's a false economy to operate with inadequate headroom.
A crucible of informative mistakes
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