- Community Home
- >
- Servers and Operating Systems
- >
- HPE ProLiant
- >
- ProLiant Servers (ML,DL,SL)
- >
- file descriptor xx left open - problem with LVM on...
ProLiant Servers (ML,DL,SL)
1748164
Members
3623
Online
108758
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
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
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
04-07-2008 04:12 AM
04-07-2008 04:12 AM
file descriptor xx left open - problem with LVM on ProLiant ML 350
Hello,
i'm getting the mentioned error in SuSE Linux Enterprise Server 10 SP1, ProLiant ML 350 G4p,
using LVM.
If i type in a xterm (under KDE) e.g. vgscan, vgdisplay, pvscan i get
the message: "file descriptor xx left open", with a one or two digit
number for xx.
Afterwards i see the desired infromations. The LV's are accessible,
reading and writing is possible. When i leave X and start a tty with
STRG+ALT+F2, and then type e.g. vgscan, vgdisplay, i don't get these
mesages !
Following questions:
1. What does these messages mean ? Are they severe ? I searched
already on the net, and found a lot of people experiencing the same
problem, but no one has a solution/explanation.
2. Why do i get these messages in a xterm, but not in a tty. In both
should run the same bash, or ?
3. How can i get more informations about these file descriptors ? E.g.
which process is attached, or which file is it in real ?
Thanks in advance for any help.
Bernd
i'm getting the mentioned error in SuSE Linux Enterprise Server 10 SP1, ProLiant ML 350 G4p,
using LVM.
If i type in a xterm (under KDE) e.g. vgscan, vgdisplay, pvscan i get
the message: "file descriptor xx left open", with a one or two digit
number for xx.
Afterwards i see the desired infromations. The LV's are accessible,
reading and writing is possible. When i leave X and start a tty with
STRG+ALT+F2, and then type e.g. vgscan, vgdisplay, i don't get these
mesages !
Following questions:
1. What does these messages mean ? Are they severe ? I searched
already on the net, and found a lot of people experiencing the same
problem, but no one has a solution/explanation.
2. Why do i get these messages in a xterm, but not in a tty. In both
should run the same bash, or ?
3. How can i get more informations about these file descriptors ? E.g.
which process is attached, or which file is it in real ?
Thanks in advance for any help.
Bernd
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