- Community Home
- >
- Servers and Operating Systems
- >
- Legacy
- >
- HPE 9000 and HPE e3000 Servers
- >
- Re: Page Deallocation Table (PDT)
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
тАО08-05-2004 12:14 AM
тАО08-05-2004 12:14 AM
Page Deallocation Table (PDT)
The Page Deallocation Table (PDT) is 100% full.
PDT Entries Used: 50
PDT Entries Free: 0
PDT Total Size: 50
An excessive number of memory pages have been deallocated due to
excessive correctable single bit errors being detected. Although the
errors are being corrected, this condition indicates a potential
problem.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО08-05-2004 12:23 AM
тАО08-05-2004 12:23 AM
Re: Page Deallocation Table (PDT)
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО08-05-2004 12:42 AM
тАО08-05-2004 12:42 AM
Re: Page Deallocation Table (PDT)
Can I work in this way? Until I find another module?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО08-05-2004 01:28 AM
тАО08-05-2004 01:28 AM
Re: Page Deallocation Table (PDT)
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО08-05-2004 03:31 AM
тАО08-05-2004 03:31 AM
Re: Page Deallocation Table (PDT)
1) Reboot the system
2) Interrupt the autoboot
3) go to configuration menu
I believe you have the option to clear PDT entries from here. I cannot recollect the exact command though.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО08-05-2004 07:54 AM
тАО08-05-2004 07:54 AM
Re: Page Deallocation Table (PDT)
Bill Hassell, sysadmin
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО08-05-2004 10:42 PM
тАО08-05-2004 10:42 PM
Re: Page Deallocation Table (PDT)
the PDT entries are genertated by the online diagnostics if single bit errors happen. If an excessive amount of errors happen on one dimm, then it points to a hardware problem on this Dimm. But: we should keep in mind that these are only single bit errors. Single bit errors are corrected without delay and the only impact on the performance is that CPU time is used for logging the error via the dm_memory monitor and the memlogd process. The same diagnostic processes are responsible for writing PDT entries. This is only a preventive action to decrease the chance of a double bit error.
Although the chance of a double bit error is higher than before, it is still very low, because this would mean that two bits flip in one byte at the same time which is not very probable in a Dimm > 1 MB.
Let's say we have two independend single bit errors in 1 MB. The chance that after the first single bit error, the next error happens on the same byte is ~ 1000000:1 and you need a lot of single bit errors to produce such an error.
Unfortunately it may also be that the errors are not independent and in this case it may indeed be that the server will crash in the future with a double bit error (and if a double bit error occurs during the selftests, and the PDT is full, then the Dimm will be deallocated).
If you want to save your money and take a risk then ignore the errors. Maybe your system will run for the next 100 years without a crash ;-)
If a double bit errors occur, then you must replace the dimm (depends on server type if one or two dimms have to be replaced).
good luck
Stefan
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО08-06-2004 08:03 PM
тАО08-06-2004 08:03 PM
Re: Page Deallocation Table (PDT)
Most recommended now is to replace the bad memeory module.
TT