Hi!

Andrea Gelmini <andrea.gelm...@gmail.com> schrieb:

>   and thanks a lot for your work.
>   I have an USB drive with BTRFS, on which I write with different
> kernel release.
>   Anyway, today I made a copy of one big file, and than powered off
> the computer with a clean shutdown (Ubuntu 13.10 - 32bit).
>   Now it's impossible to me to mount it (even with kernel 3.12).

Some init systems are not clever enough to cleanly unmount filesystems under 
some circumstances, you usually see a log message similar to this then:

"Unable to unmount filesystem. Shutting down anyway. Good luck"

I don't remember the exact phrasing. What it essantially means is that a 
sync was issued, the init systems waits another few seconds, then shuts 
down.

For your USB connected btrfs these "few seconds" could probably not be 
enough. Btrfs tends to do a lot of background work from time to time which 
makes it lag on unmount for a few minutes sometimes especially for USB 
drives. The underlying problem could also be mounting through the device 
mapper. I'm not sure how it plays into the problem but it may introduce some 
sort of write behavior that btrfs is not aware of. I'm pretty sure I've read 
something about device mapper and write barriers not working correctly which 
are needed for btrfs being able to rely on transactions working correctly.

Either find an init system which handles this in a more sane way or simply 
unmount manually before shutting the system down and wait for the unmount to 
complete and return to command line (so do it from command line, not GUI). 
Maybe try to avoid the device mapper.

BTW, this is only guessing. And I'm sorry it doesn't help for the particular 
situation you are in currently.

Did you try to mount in recovery mode? This may, however, mount an older 
version of your superblock which does not refer to your latest additions of 
files on the disk but it may be newer than what you got in your backup.

HTH
Kai

--
To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Reply via email to