| To: | Jan Engelhardt <jengelh@xxxxxxxxxxxxxxx> |
|---|---|
| Subject: | Re: XFS write speed drop |
| From: | Helge Hafting <helge.hafting@xxxxxxxxxxxxx> |
| Date: | Fri, 26 May 2006 09:20:27 +0200 |
| Cc: | Nathan Scott <nathans@xxxxxxx>, linux-xfs@xxxxxxxxxxx, Linux Kernel Mailing List <linux-kernel@xxxxxxxxxxxxxxx> |
| In-reply-to: | <Pine.LNX.4.61.0605231517330.25086@yvahk01.tjqt.qr> |
| References: | <Pine.LNX.4.61.0605190047430.23455@yvahk01.tjqt.qr> <20060522105326.A212600@wobbly.melbourne.sgi.com> <Pine.LNX.4.61.0605221308290.11108@yvahk01.tjqt.qr> <20060523084309.A239136@wobbly.melbourne.sgi.com> <Pine.LNX.4.61.0605231517330.25086@yvahk01.tjqt.qr> |
| Sender: | xfs-bounce@xxxxxxxxxxx |
| User-agent: | Thunderbird 1.5.0.2 (X11/20060516) |
Jan Engelhardt wrote:
Well as mentioned, -o nobarrier solved it, and that's it. I do not actually need barriers (or an UPS, to poke on another thread), because power failures are rather rare in Germany. Then there are mistakes like someone stepping on the power cord, pulling out the wrong one, drilling holes in the wall, there are kernel crashes, there is lightning, there is the possibility that some component inside the box just breaks. Helge Hafting |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | PARTIAL TAKE 952967 - BUG() in generic_delete_inode(), David Chinner |
|---|---|
| Next by Date: | Re: XFS write speed drop, Jan Engelhardt |
| Previous by Thread: | Re: XFS write speed drop, Jeremy Higdon |
| Next by Thread: | Re: XFS write speed drop, Jan Engelhardt |
| Indexes: | [Date] [Thread] [Top] [All Lists] |