At Wed, 03 Jul 2013 13:05:28 -0400, Jeff Mahoney wrote:
On 7/3/13 12:57 PM, Cristian Rodríguez wrote:
El 03/07/13 12:23, Jeff Mahoney escribió:
So, I'd like to hear your stories. What's worked for you? What hasn't worked? What would you consider the pain points with using btrfs?
I had some problems in the past, but since 3.9 or so I have not seen them again, if I recall correctly, hell broke lose when my small SSD disk was full, there was no way to mount it, or do anything with it, issuing btrfs-zero-log to the device save the day.
I suggest running tests on ENOSPC conditions ;-)
Yep, that's tops on the list but even those have become less frequent.
I hit this problem when I moved the whole FS on my workstation to btrfs, and unfortunately in my case, I had to reinstall the whole system from the scratch, and lose many data. This was the worst case I met ever since Reiserfs over 10 years ago, so I gave up btrfs since then. A sudden -ENOSPC is unavoidable as a nature of COW, especially when snapshots are taken automatically. But, the behavior like this (refusing any actions including mount) is a literally disaster, which must not happen. If mount may be refused, at least a proper fsck must be provided instead of a random tool. Takashi -- To unsubscribe, e-mail: firstname.lastname@example.org To contact the owner, e-mail: email@example.com