CentOSThis forum is for the discussion of CentOS Linux. Note: This forum does not have any official participation.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Ive noticed the past several days the dump command has been hanging and not producing any output.
I tried to run from the command line, but it's not doing anything and requires a "kill -9" to abort from another console.
# /sbin/dump -0uz9 -f /tmp/root.151012.L0.dump /
Output file is created, but 0 length, even after several hours. This has been running fine for almost a year until this weekend...
Yes, it does look like this device might be an issue.
dmsetup shows that to be used as a RAW device, and I tried to access the /dev/raw device and it's also hanging.
Ill have to see what's wrong with the device on the SAN, but as a side-note, why would it hang on access to the raw device when it's not dumping the raw device in the command itself?
I requested it to dump a filesystem, which has nothing to do with the raw device.
any access to that device will hang because the driver is out. You may try to access the filesystem on that device, partition table or whatever ("high" level access - not only to the raw device) and finally all of them will hang. I have no idea about your system at all, but probably something was "in use" on that device.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.