Join GitHub today
GitHub is home to over 50 million developers working together to host and review code, manage projects, and build software together.
Sign upBtrfs rm issue #2961
Btrfs rm issue #2961
Comments
|
@mzdaniel You run BTRFS, do you have these issues ? |
|
@unclejack I wonder if it'd be worthwhile to have the daemon check the directory on startup and throw out a warning if it's not on ext4 until we can get these issues worked out or worked around? |
|
@tianon I think we could have Docker just check what FS its storage is on when using AUFS. If the used FS isn't one we know to to be fully compatible with AUFS, we can just display that warning. |
|
+1, SGTM |
|
There's a native btrfs driver now. That one should be used instead of attempting to use AUFS on top of btrfs. I'll close this issue now since we're not going to support AUFS on top of btrfs for now. Please feel free to comment. |
This issue was split from #2953 because I described two different problems in there.
When I try to delete a directory inside a container with rm -rf I get the error "Directory not empty"
rm: fts_read failed: Stale NFS file handle
It failed
I tried docker verison 0.6.7 and 0.7.