at least one volume could not be unmounted

#At least one volume could not be unmounted update#

Second, try mounting with options -o recovery or -o ro or -o recovery,ro (using the new kernel). If you have your kernel on a btrfs filesystem, then you will probably have to find a recovery disk with a recent kernel on it.

#At least one volume could not be unmounted update#

Mount/unmount problems I can't mount my filesystem, and I get a kernel oops!įirst, update your kernel to the latest one available and try mounting again. Please attach files (like logs or dumps) directly to the bug and don't use pastebin-like services. If you include kernel log backtraces in bug reports sent to the mailing list, please disable word wrapping in your mail user agent to keep the kernel log in a readable format. Please use btrfs-progs somewhere in the bug subject if you're reporting a bug for the userspace tools. For quick questions you may want to join the IRC #btrfs channel on libera.chat (and stay around for some time in case you do not get the answer right away). Please report bugs on Bugzilla on (requires registration) setting the component to Btrfs, and report bugs and issues to the mailing list ( you are not required to subscribe). General topics How do I report bugs and issues? 3.5 I get 'No space left on device' errors, but df says I've got lots of space.3.4 I get the message 'failed to open /dev/btrfs-control skipping device registration' from 'btrfs dev scan'.3.2 Compression doesn't work / poor compression ratios.

3.1 Defragmenting a directory doesn't work.2.4 My filesystem won't mount and none of the above helped.2.3 Only one disk of a multi-volume filesystem will mount.2.2 Filesystem can't be mounted by label.2.1 I can't mount my filesystem, and I get a kernel oops!.