Bug 177951
| Summary: | kernel 2.6.15-1.185*_FC5 eats my filesystem | ||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Nicolas Mailhot <nicolas.mailhot> | ||||||||||||||||||||||||||
| Component: | kernel | Assignee: | Jeff Garzik <jgarzik> | ||||||||||||||||||||||||||
| Status: | CLOSED UPSTREAM | QA Contact: | Brian Brock <bbrock> | ||||||||||||||||||||||||||
| Severity: | high | Docs Contact: | |||||||||||||||||||||||||||
| Priority: | medium | ||||||||||||||||||||||||||||
| Version: | rawhide | CC: | davej, dcantrell, dwmw2, k.georgiou, peterm, sundaram, wtogami | ||||||||||||||||||||||||||
| 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: | 2006-02-03 13:18:56 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: | |||||||||||||||||||||||||||||
| Bug Depends On: | |||||||||||||||||||||||||||||
| Bug Blocks: | 150222, 172490 | ||||||||||||||||||||||||||||
| Attachments: |
|
||||||||||||||||||||||||||||
|
Description
Nicolas Mailhot
2006-01-16 19:26:27 UTC
Created attachment 123251 [details]
lspci
Created attachment 123252 [details]
/var/log/dmesg with working kernel
Created attachment 123253 [details]
mdadm for /dev/md0
Created attachment 123254 [details]
mdadm for /dev/md1
Created attachment 123255 [details]
lvm info
Created attachment 123256 [details]
lsmod on working system
Created attachment 123343 [details]
dmesg for one problem kernel (kernel-2.6.15-1.1859_FC5)
I hope this helps - this just cost me 2h of cleanup after the attempted boot
(single mode) corrupted the filesystem again
this really looks like a hardware problem. Either a bad cable, or worse, a dying drive. Those ata warnings are a really big sign.. "Unrecovered read error - auto reallocate failed" Means it couldn't read a sector, and when it tried to reallocate it from the spare pool, it couldn't, which usually means its already reallocated a bunch of sectors. Looks like RMA time. It may look like a dying drive but : 1. smart reports 0 error 2. the system is solid with 2.6.15 kernel, even after several days of I/O 3. the drives are new (ok weak point) 4. and anyway what's the probability for *two* new drives going bad at *exactly* the same moment (being SATA BTW It may look like a dying drive but : 1. smart reports 0 error 2. the system is solid when rebooted with 2.6.15 kernel, even after several days of I/O 3. the drives are new (ok weak point) 4. and anyway what's the probability for *two* new drives going bad at *exactly* the same moment (being SATA BTW they don't share cabling) Created attachment 123604 [details]
smart info for sda
Created attachment 123605 [details]
smart info for sdb
Just let me know if you need more logs / test results 2.6.15-1.1872_FC5 patched to disable FUA (as suggested by Tejun Heo there : http://marc.theaimsgroup.com/?l=linux-ide&m=113825474609128) boots fine I've been unable to connect to marc.theaimsgroup.com for weeks, from multiple locations around the world. Can you attach that patch to the bugzilla please ? Strange, it works fine there. You can find the whole thread on any other linux-ide archive (Title is : regarding bug #5914 - fs corruption on SATA) I'll attach the patch but it's very preliminary and useful mainly to check if FUA is causing problems on a system (it short-circuits it). People are talking about drive-specific FUA blacklisting now (but the fuller patch is not cooked yet) Created attachment 123808 [details]
Simple patch to disable fua
Created attachment 123940 [details]
Fua blacklisting
The following (tested) patch implements fua drive blacklisting (specifically,
my drive model). Was posted in the aforementioned thread
Created attachment 123941 [details]
dmesg for kernel patched with patch #123940
Closing as the blacklisting patch was merged in latest git snapshot upstream |