| To: | Eric Sandeen <sandeen@xxxxxxxxxxx> |
|---|---|
| Subject: | Re: LWN article: ext4 and data loss |
| From: | Greg Banks <gnb@xxxxxxx> |
| Date: | Fri, 13 Mar 2009 03:33:49 +1100 |
| Cc: | Martin Steigerwald <Martin@xxxxxxxxxxxx>, xfs@xxxxxxxxxxx |
| In-reply-to: | <49B92423.4020708@xxxxxxxxxxx> |
| Organization: | File Serving Technologies ; Silicon Graphics Inc. |
| References: | <200903121239.35442@xxxxxx> <49B9097C.1070003@xxxxxxxxxxx> (sfid-20090312_151043_496061_D19DDB11) <200903121514.12732.Martin@xxxxxxxxxxxx> <49B92423.4020708@xxxxxxxxxxx> |
| User-agent: | Thunderbird 1.5.0.12 (X11/20060911) |
Eric Sandeen wrote: > > It's simple. Want your data safe on disk? fsync. There's not a lot > more to it than that. (and if fsync hurts perf too much, re-think how > you are storing your data) > > Filesystems can hack around some heuristics to try to make unsafe apps > safer, but in the end, it's the app's job to make sure a buffered write > hits permanent storage when it matters. > Stewart Smith has a highly entertaining presentation on this very topic. http://www.linux.org.au/conf/2007/talk/278.html -- Greg Banks, P.Engineer, SGI Australian Software Group. the brightly coloured sporks of revolution. I don't speak for SGI. |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: LWN article: ext4 and data loss, Greg Banks |
|---|---|
| Next by Date: | Oops at xfs_bmbt_get_startoff in SLES 10 2.6.16, Kevin Jamieson |
| Previous by Thread: | Re: LWN article: ext4 and data loss, Eric Sandeen |
| Next by Thread: | Re: LWN article: ext4 and data loss, Eric Sandeen |
| Indexes: | [Date] [Thread] [Top] [All Lists] |