Bug 215237
Summary: | lvcreate --snapshot crashes machine | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 4 | Reporter: | Kirchner <w.kirchner> |
Component: | lvm2 | Assignee: | Milan Broz <mbroz> |
Status: | CLOSED INSUFFICIENT_DATA | QA Contact: | Corey Marthaler <cmarthal> |
Severity: | high | Docs Contact: | |
Priority: | medium | ||
Version: | 4.4 | CC: | agk, dwysocha, jbrassow, mbroz, m.hanisch, prockai, pvrabec |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | i386 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2007-01-29 17:20:55 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Kirchner
2006-11-12 18:50:06 UTC
Please can you provide more information about this crash ? - anything related in syslog - is it SMP system ? How much memory is there ? - run script with debugging info - add 'activation = 1' in the log section of lvm.conf and run lvm commands with -vvvv to log debug messages Please attach output of (before and after crash - of course if it is possible) dmsetup info -c dmsetup table dmsetup status and if possible full process and memory info after crash (to syslog) echo t > /proc/sysrq-trigger echo m > /proc/sysrq-trigger (or enable sysrq key and use it from console) (You can try to create separate volume group for root volume and separate for data volume + snapshots to avoid some locking issues. Also significant is amount of free physical memory - not swap.) Since there are insufficient details provided in this report I am closing this bug. Please if you see this issue again, reopen the bug and provide requested information, thank you. |