HPE GreenLake Administration
- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - Linux
- >
- cmresmond/cmcheckdisk problem
Operating System - Linux
1825793
Members
2302
Online
109687
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
Forums
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
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
10-29-2003 07:49 PM
10-29-2003 07:49 PM
cmresmond/cmcheckdisk problem
Hi,
we have the following setup: MC Service/Guard for Linux v.A 11.14.02 on 2 RedHat 7.3 nodes with kernel 2.4.22 and devfs.
The cmcheckdisk program, spawned by cmresmond at every x seconds aborts with a core dump.
Running cmcheckdisk alone, it seems that the environment affects it: some times unsetting some env variables fixes the problem; the strange thing is that the name of the variables doesn't matter, only the number of characters.
We believe that it's because the device names in /proc/partitions are long (e.g. 34 chars) and maybe some internal buffer overflows.
Has anyone seen this behaviour?
we have the following setup: MC Service/Guard for Linux v.A 11.14.02 on 2 RedHat 7.3 nodes with kernel 2.4.22 and devfs.
The cmcheckdisk program, spawned by cmresmond at every x seconds aborts with a core dump.
Running cmcheckdisk alone, it seems that the environment affects it: some times unsetting some env variables fixes the problem; the strange thing is that the name of the variables doesn't matter, only the number of characters.
We believe that it's because the device names in /proc/partitions are long (e.g. 34 chars) and maybe some internal buffer overflows.
Has anyone seen this behaviour?
3 REPLIES 3
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-30-2003 01:11 AM
10-30-2003 01:11 AM
Re: cmresmond/cmcheckdisk problem
As no one seems to be answering this one I will have a go !
One way I use to find out more about such problem is perhaps, a little twisted, but her goes !
I would try to invoke the faulty command using something like the following ex:
#strace -o test.dat df
this show you all system calls for command df and place result in test.dat, you can then read/analyse test.dat and try/see if you can more informations out of this.
I also sometimes use lsof command to further help me find out more info to continue solution search ...
In your case could try this before and after changing variable and see/check where that leads...
Just Hoping this will toggle/trigger some advance and get you on the way.
J-P
One way I use to find out more about such problem is perhaps, a little twisted, but her goes !
I would try to invoke the faulty command using something like the following ex:
#strace -o test.dat df
this show you all system calls for command df and place result in test.dat, you can then read/analyse test.dat and try/see if you can more informations out of this.
I also sometimes use lsof command to further help me find out more info to continue solution search ...
In your case could try this before and after changing variable and see/check where that leads...
Just Hoping this will toggle/trigger some advance and get you on the way.
J-P
Smile I will feel the difference
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-30-2003 01:20 AM
10-30-2003 01:20 AM
Re: cmresmond/cmcheckdisk problem
Hello,
We already did that - indeed, strace+lsof are the first debugging tools. But the problem is that it crashes somewhere in userspace, and gdb shows (on the core) that it SEGFAULT-ed somewhere in glibc/vprintf, which led me to the ideea that it is somehow related to (for example):
char devname[16];
sprintf(devname, "/dev/%s", whatever);
In our case, device names are longer than in non-devfs case, which possibly triggers this. Before switching to devfs, it was ok.
We already did that - indeed, strace+lsof are the first debugging tools. But the problem is that it crashes somewhere in userspace, and gdb shows (on the core) that it SEGFAULT-ed somewhere in glibc/vprintf, which led me to the ideea that it is somehow related to (for example):
char devname[16];
sprintf(devname, "/dev/%s", whatever);
In our case, device names are longer than in non-devfs case, which possibly triggers this. Before switching to devfs, it was ok.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-30-2003 01:34 AM
10-30-2003 01:34 AM
Re: cmresmond/cmcheckdisk problem
I suppose you have already done this, but did you try this with more a higher trace level
devfsd -t
I have had a look at man devfsd and that also talks of variable in bash env
Just trying to help
J-P
devfsd -t
I have had a look at man devfsd and that also talks of variable in bash env
Just trying to help
J-P
Smile I will feel the difference
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.
Company
Support
Events and news
Customer resources
© Copyright 2025 Hewlett Packard Enterprise Development LP