diff options
| author | Thomas Schwinge <tschwinge@gnu.org> | 2011-07-25 11:27:24 +0200 |
|---|---|---|
| committer | Thomas Schwinge <tschwinge@gnu.org> | 2011-07-25 11:27:24 +0200 |
| commit | b687f782572b127e8ae32f0df40250fb19ccd22b (patch) | |
| tree | ccce6af6cd4809f0f6fa694ff7789c52d1bb9c2e /open_issues/rm_fr.mdwn | |
| parent | 6fb6c2a396bb1b851a4ec8a6f5e605a15c218d10 (diff) | |
IRC.
Diffstat (limited to 'open_issues/rm_fr.mdwn')
| -rw-r--r-- | open_issues/rm_fr.mdwn | 12 |
1 files changed, 12 insertions, 0 deletions
diff --git a/open_issues/rm_fr.mdwn b/open_issues/rm_fr.mdwn index 89a803ab..aab52d97 100644 --- a/open_issues/rm_fr.mdwn +++ b/open_issues/rm_fr.mdwn @@ -25,3 +25,15 @@ really waits for all I/Os, which basically means strictly serializing file removals: remove one file, wait for the disk to have done it (~10ms), remove the next one, etc. I guess this is for safety reasons against crashes, but isn't the sync option there for such kind of + + +# IRC, freenode, #hurd, 2011-07-23 + + <antrik> youpi: hm... async deletion does have one downside: I just removed + something to make space, and retried the other command immediately + afterwards, and it still said "no space left on device"... a few seconds + later (after the next regular sync I suppose?) it worked + <youpi> well, that's sorta expected, yes + <youpi> we get the same on Linux + <youpi> Mmm, on second thought, I'm not sure how that can happen + <youpi> the asynchronous thing is for disk writes, not cache writes |