Bug 307971
| Summary: | GFS: kernel panic when filesystem withdrawn after storage controller reset | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 5 | Reporter: | Corey Marthaler <cmarthal> |
| Component: | gfs-kmod | Assignee: | Robert Peterson <rpeterso> |
| Status: | CLOSED WORKSFORME | QA Contact: | Cluster QE <mspqa-list> |
| Severity: | low | Docs Contact: | |
| Priority: | low | ||
| Version: | 5.0 | CC: | bmr |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2007-12-19 20:28:51 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
Corey Marthaler
2007-09-26 20:29:38 UTC
Do you remember the bugzilla number of the RHEL4 bug where this was previously fixed? No, I've been looking for it but can't find it, I wonder if it was in the old sistina bz system, because it was a long time ago when it was filed, but not that long ago when it was fixed. This does appear to be just the flock case (which I just found out may already have a bug for this issue), as I attempted this scenario with just a dd writing to the gfs and the withdraw worked without the panic. I tried for a long time to recreate this problem on both gfs and gfs2 by mounting the file system, taking flocks, then doing "gfs_tool withdraw /mnt/gfs2" for gfs1, or "echo "1" > /sys/fs/gfs2/sdb1/withdraw") for gfs2. I tried a couple ways of taking out flocks: (1) xiogen -t 10k -T 10k -o -m random -F 50k:file | xdoio -n 6 -K (2) genesis -S RANDSEED -i RUN_TIME -n 100 -d 100 -p 10 -L flock -s 665600 (3) locktests (a tool I got for a bugzilla a while back). I tried a local disk (/dev/sdb1) and a SAN through LVM2 from multiple nodes, but it didn't recreate. The withdraw happened as expected, but there was no subsequent panic. I'm looking for a good way to recreate this. I haven't actually written my own flock test program but that's probably the next step. I suppose I could also try pulling the FC cable from my box rather than doing a controlled withdraw from the command line. I was unable to reproduce this issue, will reopen if seen again. It does seem odd though, that this stack is reported in other bz's 253347/253948, hmmm... |