| To: | xfs-masters@xxxxxxxxxxx |
|---|---|
| Subject: | [xfs-masters] [Bug 6380] XFS corruption with Linux 2.6.16 |
| From: | bugme-daemon@xxxxxxxxxxxxxxxxxxx |
| Date: | Thu, 13 Apr 2006 09:06:27 -0700 |
| Reply-to: | xfs-masters@xxxxxxxxxxx |
| Sender: | xfs-masters-bounce@xxxxxxxxxxx |
http://bugzilla.kernel.org/show_bug.cgi?id=6380 ------- Additional Comments From Martin@xxxxxxxxxxxx 2006-04-13 09:06 ------- One additional thought: Can XFS detect common cases where write operation is dangerous (ATM only write cache on with barrier off comes to my mind) and do a readonly mount in that case issuing an error message explaining why it does so? IMHO a filesystem should follow that better safe than sorry strategy where possible when it comes to the risk of data corruption. And at least here it shouldn't have any serious performance impact. ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee. |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | [xfs-masters] Re: notifier chain problem? (was Re: 2.6.17-rc1 did break XFS), Jes Sorensen |
|---|---|
| Next by Date: | [xfs-masters] Re: 2.6.17-rc1 did break XFS, Alan Stern |
| Previous by Thread: | [xfs-masters] [Bug 6380] XFS corruption with Linux 2.6.16, bugme-daemon |
| Next by Thread: | [xfs-masters] [Bug 624] New: DM_EVENT_REMOVE does not include object mode, bugzilla-daemon |
| Indexes: | [Date] [Thread] [Top] [All Lists] |